iclr-review-process
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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iclr-review-process --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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,
- Process model
- Author strategy
- How public reviews change strategy
- Worked vignette
- Reviewer-pushback patterns
- Output format
What does the iclr-review-process skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iclr-review-process --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.