Research Finance
borghei/Claude-Skills
Research budgeting and funding operations — study budget construction, cost per participant and per insight, burn against milestones, and portfolio prioritisation by decision value.
A skill your agent uses when planning an ICLR project timeline from topic selection through OpenReview submission, discussion, revision, decision, camera-ready, poster, video, and public artifact…
Install Iclr Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iclr-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iclr-workflow --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/ICLR-Skills/skills/iclr-workflow .claude/skills/iclr-workflow && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "iclr-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICLR-Skills/skills/iclr-workflow into .claude/skills/iclr-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iclr-workflow", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICLR-Skills/skills/iclr-workflowType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iclr-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iclr-workflow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/ICLR-Skills/skills/iclr-workflow .agents/skills/iclr-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "iclr-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICLR-Skills/skills/iclr-workflow into .agents/skills/iclr-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iclr-workflow", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iclr-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iclr-workflow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/ICLR-Skills/skills/iclr-workflow .cursor/skills/iclr-workflow && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "iclr-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICLR-Skills/skills/iclr-workflow into .cursor/skills/iclr-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iclr-workflow", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path ICLR-Skills/skills/iclr-workflow--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iclr-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iclr-workflow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/ICLR-Skills/skills/iclr-workflow .gemini/skills/iclr-workflow && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "iclr-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICLR-Skills/skills/iclr-workflow into .gemini/skills/iclr-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iclr-workflow", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iclr-workflowInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iclr-workflow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/ICLR-Skills/skills/iclr-workflow .github/skills/iclr-workflow && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "iclr-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICLR-Skills/skills/iclr-workflow into .github/skills/iclr-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iclr-workflow", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iclr-workflow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iclr-workflow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/ICLR-Skills/skills/iclr-workflow .opencode/skills/iclr-workflow && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "iclr-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICLR-Skills/skills/iclr-workflow into .opencode/skills/iclr-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iclr-workflow", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
iclr-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 527 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when planning an ICLR project timeline from topic selection through OpenReview submission, discussion, revision, decision, camera-ready, poster, video, and public artifact…
- Planning an ICLR project timeline from topic selection through OpenReview submission
- SKILL.md covers Milestones, Operating rules, Phase ownership and risk and Worked vignette, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Public artifact release
What it does
Iclr Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an ICLR project timeline from topic selection through OpenReview submission, discussion, revision, decision, camera-ready, poster, video, and public artifact release. Use when sequencing milestones against the current cycle's OpenReview deadlines, budgeting time for the long public discussion phase, or assigning owners for anonymity audits and reviewer-verifiable evidence paths.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Business, Finance & HR, covering Project management and Budgeting and forecasting. The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Planning an ICLR project timeline from topic selection through OpenReview submission
- Public artifact release
- Sequencing milestones against the current cycles OpenReview deadlines
- Budgeting time for the long public discussion phase
Example prompts
- “/iclr-workflow”
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Iclr Workflow loads about 1.1k tokens when it runs. Until then it costs about 103 tokens; SKILL.md has 527 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 527 words, ~1,132 tokens.
Download SKILL.mdSave it as
.claude/skills/iclr-workflow/SKILL.md (or your agent's skills folder).- name
- iclr-workflow
- description
- Use when planning an ICLR project timeline from topic selection through OpenReview submission, discussion, revision, decision, camera-ready, poster, video, and public artifact release. Use when sequencing milestones against the current cycle's OpenReview deadlines, budgeting time for the long public discussion phase, or assigning owners for anonymity audits and reviewer-verifiable evidence paths.
ICLR Workflow
Use this as the project-management skill for an ICLR submission. Always replace dates with the current cycle's official deadlines and work backwards from OpenReview cutoffs.
ICLR is a conference, not a journal: it has no standing editor-in-chief and no article-processing charge. The rotating leadership is the per-edition General Chair, Senior Program Chair, and Program Chairs, and the cost model is registration fees, not APCs — proceedings are open-access on OpenReview. The ICLR 2027 committee is not recorded in this pack: the 2027 committees page 404s at the source map's access date, so no official page names it (the 2026 committee was General Chair Carl Vondrick, Senior PC Bharath Hariharan, and PCs Raffel, Pinto, Yang and Faust, and those appointments rotate). Program chairs are reachable at program-chairs@iclr.cc. Re-check the current CFP and committees page rather than carrying a name forward.
Milestones
- Fit decision: confirm the paper has a learning-representation contribution and a credible ICLR audience.
- Evidence lock: freeze the main claim, core baselines, ablations, and reproducibility path.
- Abstract deadline: submit a real abstract and verify author list, conflicts, subject areas, and OpenReview profiles.
- Paper deadline: upload anonymized PDF, supplement, code/data package, disclosures, and required fields.
- Review release: triage reviewer concerns and assign owners for evidence, wording, and revision.
- Discussion: respond, upload allowed revisions, maintain a concise changelog, and escalate only through official channels.
- Decision: archive reviews, meta-review, author discussion, and final submitted version.
- Acceptance: complete camera-ready, poster, slides, video, project page, public artifacts, and registration.
Operating rules
- Maintain one source-of-truth checklist for OpenReview fields and file names.
- Run an anonymity audit after every PDF, supplement, code, or demo change.
- Keep a "reviewer can verify this in five minutes" path for each major claim.
- Do not add new experiments during discussion unless they clarify an already submitted claim and current rules allow the revision.
Show full SKILL.md (224 more words)Show less
Phase ownership and risk
ICLR's timeline differs from venues with a short rebuttal: the public discussion phase is long, and revisions you upload remain visible. Plan for an extended, public exchange, not a one-shot rebuttal.
| Phase | Owner focus | ICLR-specific risk |
|---|---|---|
| Abstract deadline | Profiles, conflicts, real abstract | Placeholder abstract or incomplete profile |
| Paper deadline | Anonymized PDF, supplement, disclosures | Identity leak in code or links |
| Review release | Triage, assign evidence owners | Reacting to every score instead of the AC's concern |
| Discussion | Replies, allowed revisions, changelog | Promising runs the cycle's rules disallow |
| Camera-ready | De-anonymize, fulfill promises | Final PDF drifts from the meta-review |
Worked vignette
A two-person team plans backward from the OpenReview paper deadline for an interpretability paper. They lock the main claim and core ablation early, reserve the final days for an anonymity audit of the PDF and code ZIP, and pre-assign discussion roles: one owns evidence replies, one owns wording and the changelog. When reviews land they already have a "verify in five minutes" probe script, so the public thread stays concrete.
Reviewer-pushback patterns to schedule around
- "We need a new experiment fast." Pre-build a probe or ablation harness so small results are cheap.
- "Anonymity slipped after an edit." Re-run the audit after every PDF, supplement, or code change.
- "Deadline confusion." Treat the current cycle's OpenReview dates as the single source of truth.
Output format
[Current stage] idea / experiments / writing / submission / discussion / accepted
[Next deadline] <official date and source, or unknown>
[Critical path] <three tasks that determine readiness>
[Anonymity checkpoint] pass / needs audit
[Owner map] <task -> person or role>© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in ICLR-Skills/skills/iclr-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Iclr Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Iclr Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Research Financeborghei/Claude-Skills | 886 | — | ~3.4k | Automated safety check: Pass | MIT | |
| Fda Catalyst Vaccinesagentii-ai/agentii-investment-intelligence | 207 | — | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| Longbridge Researchhelsome/folio | 270 | 3 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Bet SizingJoelLewis/finance_skills | 205 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Ceos Calendarbradfeld/ceos | 156 | — | ~2k | Automated safety check: Pass | MIT |
Similar skills
Fda Catalyst Vaccines
agentii-ai/agentii-investment-intelligence
Vaccine catalyst analysis across the two-gate path: CBER BLA review and the ACIP recommendation gate that turns FDA approval into commercial availability.
Longbridge Research
helsome/folio
Institution ratings, consensus price targets, EPS/revenue forecasts, finance calendar, shareholder data, fund holders, insider trades (SEC Form 4), short interest, industry rankings, peer group…
Bet Sizing
JoelLewis/finance_skills
Determine how much capital to allocate to individual positions within a portfolio.
Ceos Calendar
bradfeld/ceos
A skill your agent uses when managing the rolling market calendar - conferences, launches, fundraising milestones, partner events, and team constraints
Cre Asset Management
ahacker-1/cre-agent-skills
CRE Asset Management analysis suite — 9 specialist skills for post-acquisition multifamily operations including annual budgeting, monthly variance analysis, rent collection, renewal decisions…
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Related
Questions about Iclr Workflow
What does Iclr Workflow do?
A skill your agent uses when planning an ICLR project timeline from topic selection through OpenReview submission, discussion, revision, decision, camera-ready, poster, video, and public artifact…. Iclr Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an ICLR project timeline from topic selection through OpenReview submission, discussion, revision, decision, camera-ready, poster, video, and public artifact release.
When should I use Iclr Workflow?
Iclr Workflow fits situations like: planning an ICLR project timeline from topic selection through OpenReview submission; public artifact release; sequencing milestones against the current cycles OpenReview deadlines; budgeting time for the long public discussion phase.
How do I install Iclr Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iclr-workflow -a claude-code`. Or copy the skill folder (ICLR-Skills/skills/iclr-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/iclr-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Iclr Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iclr-workflow -a codex`. Or copy the skill folder (ICLR-Skills/skills/iclr-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/iclr-workflow in your project. Codex loads it when a task matches its description.
Can I use Iclr Workflow in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iclr-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/iclr-workflow, .gemini/skills/iclr-workflow, .github/skills/iclr-workflow and .opencode/skills/iclr-workflow in your project.
What does Iclr Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Iclr Workflow is instructions for the agent only.
Does Iclr Workflow access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Iclr Workflow safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Iclr Workflow use?
Iclr Workflow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Iclr Workflow use?
About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Iclr Workflow?
Skills that share tags, products or a category with Iclr Workflow: Research Finance (borghei/Claude-Skills, 886 stars), Fda Catalyst Vaccines (agentii-ai/agentii-investment-intelligence, 207 stars), Longbridge Research (helsome/folio, 270 stars) and Bet Sizing (JoelLewis/finance_skills, 205 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Iclr Workflow?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.