Explain Usage
asgeirtj/system_prompts_leaks
Explain where this session's tokens went, with one simple chart in plain language.
A skill your agent uses when explaining or planning around the ICLR review process, including OpenReview public review, AC/SAC roles, reviewer questions, discussion, revisions, final…
MITAuto-check passed
Install Iclr Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iclr-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iclr-review-process --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-review-process .claude/skills/iclr-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICLR-Skills/skills/iclr-review-process into .claude/skills/iclr-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iclr-review-process", 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-review-processType 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-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iclr-review-process --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-review-process .agents/skills/iclr-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICLR-Skills/skills/iclr-review-process into .agents/skills/iclr-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iclr-review-process", 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-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iclr-review-process --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-review-process .cursor/skills/iclr-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICLR-Skills/skills/iclr-review-process into .cursor/skills/iclr-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iclr-review-process", 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-review-process--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-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iclr-review-process --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-review-process .gemini/skills/iclr-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICLR-Skills/skills/iclr-review-process into .gemini/skills/iclr-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iclr-review-process", 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-review-processInstalls 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-review-process -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-review-process .github/skills/iclr-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICLR-Skills/skills/iclr-review-process into .github/skills/iclr-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iclr-review-process", 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-review-process -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-review-process --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-review-process .opencode/skills/iclr-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICLR-Skills/skills/iclr-review-process into .opencode/skills/iclr-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iclr-review-process", 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-review-process- GitHub stars
- 1.2k
- Token cost
- ~940 tokens
- SKILL.md length
- 414 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when explaining or planning around the ICLR review process, including OpenReview public review, AC/SAC roles, reviewer questions, discussion, revisions, final…
- Planning around the ICLR review process
- SKILL.md covers Process model, Author strategy, How public reviews change… and Worked vignette, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Including OpenReview public review
What it does
Iclr Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when explaining or planning around the ICLR review process, including OpenReview public review, AC/SAC roles, reviewer questions, discussion, revisions, final recommendations, and ethics escalation. Use when deciding whether to reply publicly or privately, how a permanently visible review thread shapes strategy, when to upload an allowed revision, or when to escalate a defective review to the AC for the current cycle.
Its SKILL.md is about 940 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
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 around the ICLR review process
- Including OpenReview public review
- Reviewer questions
- Final recommendations
Example prompts
- “/iclr-review-process”
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 Review Process loads about 940 tokens when it runs. Until then it costs about 111 tokens; SKILL.md has 414 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). 414 words, ~940 tokens.
Download SKILL.mdSave it as
.claude/skills/iclr-review-process/SKILL.md (or your agent's skills folder).- name
- iclr-review-process
- description
- Use when explaining or planning around the ICLR review process, including OpenReview public review, AC/SAC roles, reviewer questions, discussion, revisions, final recommendations, and ethics escalation. Use when deciding whether to reply publicly or privately, how a permanently visible review thread shapes strategy, when to upload an allowed revision, or when to escalate a defective review to the AC for the current cycle.
ICLR Review Process
Use this to plan strategy around ICLR's OpenReview process. Reopen the current Reviewer Guide and Author Guide before advising on timelines, visibility, or revision permissions.
Process model
- Submissions are reviewed double-blind on OpenReview.
- Reviews evaluate contribution, correctness, empirical/theoretical support, clarity, and value to the ICLR community.
- Authors can respond in discussion; current-cycle rules determine whether and how revised PDFs or supplementary files may be uploaded.
- Reviewers may update their recommendations after discussion; ACs synthesize reviews, comments, and paper fit for the final decision.
- Some comments are public, while others can be restricted by audience. Visibility affects tone, specificity, and what should be escalated privately.
- Ethics or conduct concerns can move outside ordinary score negotiation.
Author strategy
- Treat the AC as the decision reader. Help them see which objections are resolved and which remain.
- Do not chase every score. Resolve the few issues that change acceptability.
- Use revisions only when they clarify, correct, or support existing claims.
- Keep public comments short, factual, and civil; do not accuse reviewers publicly.
- Use official confidential paths for abusive reviews, severe review defects, conflicts, or suspected integrity issues.
How public reviews change strategy
ICLR pioneered fully open review: submissions, reviews, scores, author responses, and final decisions remain on OpenReview permanently, and community members may post comments. This visibility changes the calculus at every stage.
| Visibility property | Strategic consequence | Failure mode it punishes |
|---|---|---|
| Reviews are public forever | Reply as if future citers will read it | Defensive or rude rebuttals |
| Scores are visible | Address the objection behind the score, not the digit | Score-haggling that clutters the thread |
| Community can comment | A "this is just X" post can appear | Weak novelty framing left unguarded |
| Decisions are archived | The meta-review must match your final PDF | Quietly changing claims after acceptance |
Show full SKILL.md (120 more words)Show less
Worked vignette
A submission on an alignment objective gets two borderline reviews and one negative. Instead of arguing all three, the authors identify the one concern the AC will weigh: whether the objective generalizes beyond the tuned prompt set. They post a public reply with a held-out-prompt table and upload an allowed revision. One reviewer's updated, still-public review raises the score, and the AC's meta-review cites the resolved concern.
Reviewer-pushback patterns
- "Reviewer is hostile in public." Stay factual; flag genuine abuse confidentially to the AC.
- "Revision not allowed yet." Check the current cycle's upload window before promising a new PDF.
- "Score did not move." A fixed score can still accept if the AC sees the core objection resolved.
Output format
[Stage] pre-review / reviews released / discussion / final recommendation / decision
[Decision reader] reviewer / AC / SAC / PC
[Best action] reply / revise / provide evidence / escalate / wait
[Visibility] public / restricted / confidential
[Rationale] <why this action fits ICLR process>© 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-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Iclr Review Process 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 Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~940 | Automated safety check: Pass | MIT | |
| Explain Usageasgeirtj/system_prompts_leaks | 69k | — | ~345 | Automated safety check: Pass | CC0-1.0 | |
| Logic Explainsickn33/agentic-awesome-skills | 47k | 1 repos | ~894 | Automated safety check: Pass | MIT | |
| Faceless Explainer Videoheygen-com/hyperframes | 60k | 3 repos | ~7.7k | Automated safety check: Notes | Apache-2.0 | |
| PR Explainermastra-ai/mastra | 29k | — | ~1.4k | Automated safety check: Pass | Custom licence | |
| Understand ExplainEgonex-AI/Understand-Anything | 86k | — | ~1.3k | Automated safety check: Pass | MIT |
Similar skills
Logic Explain
sickn33/agentic-awesome-skills
Explain what a specific piece of code actually does for a given input by producing a step-by-step execution trace (interprocedural, with name resolution and type transitions).
Faceless Explainer Video
heygen-com/hyperframes
Turns an article, notes or a topic brief into an explainer video whose visuals are invented per scene, built frame by frame in HyperFrames with no footage.
PR Explainer
mastra-ai/mastra
A skill your agent uses when creating an approachable, self-contained HTML review aid for a pull request; explaining what changed, why it matters, how it works, and how it fits into the broader…
Understand Explain
Egonex-AI/Understand-Anything
Gives an in-depth explanation of one file, function or module by reading the project's knowledge graph and checking that the graph is still fresh.
Explain Like Socrates
sickn33/agentic-awesome-skills
Explains concepts using Socratic-style dialogue. An agent skill from sickn33/agentic-awesome-skills.
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…
Questions about Iclr Review Process
What does Iclr Review Process do?
A skill your agent uses when explaining or planning around the ICLR review process, including OpenReview public review, AC/SAC roles, reviewer questions, discussion, revisions, final…. Iclr Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when explaining or planning around the ICLR review process, including OpenReview public review, AC/SAC roles, reviewer questions, discussion, revisions, final recommendations, and ethics escalation.
When should I use Iclr Review Process?
Iclr Review Process fits situations like: planning around the ICLR review process; including OpenReview public review; reviewer questions; final recommendations.
How do I install Iclr Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iclr-review-process -a claude-code`. Or copy the skill folder (ICLR-Skills/skills/iclr-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/iclr-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Iclr Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iclr-review-process -a codex`. Or copy the skill folder (ICLR-Skills/skills/iclr-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/iclr-review-process in your project. Codex loads it when a task matches its description.
Can I use Iclr Review Process 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-review-process -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-review-process, .gemini/skills/iclr-review-process, .github/skills/iclr-review-process and .opencode/skills/iclr-review-process in your project.
What does Iclr Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Iclr Review Process is instructions for the agent only.
Does Iclr Review Process 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 Review Process 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 Review Process use?
Iclr Review Process 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 Review Process use?
About 940 tokens (SKILL.md is roughly 3.8k 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 Review Process?
Skills that share tags, products or a category with Iclr Review Process: Explain Usage (asgeirtj/system_prompts_leaks, 69k stars), Logic Explain (sickn33/agentic-awesome-skills, 47k stars), Faceless Explainer Video (heygen-com/hyperframes, 60k stars) and PR Explainer (mastra-ai/mastra, 29k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Iclr Review Process?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 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.