iclr-author-response
Use when drafting ICLR OpenReview author discussion replies, revision notes, public comments, restricted comments, and responses to reviewer or AC concerns during the discussion period. Use when reviews land and you must decide what to answer publicly versus privately, how to log a discussion-period revision, or how to move a borderline score before the AC writes the meta-review for the permanent record.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iclr-author-response --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 Author Response Use this after ICLR reviews arrive. ICLR discussion is not just a static rebuttal: authors can answer reviewers, clarify misunderstandings, make visible revisions when allowed, and help the AC evaluate whether concerns are resolved. ## Response strategy - Separate public comments from restricted comments to reviewers, ACs, or PCs according to the current OpenReview permissions. - Lead with decision-relevant points: correctness, novelty, empirical adequacy, clarity, reproducibility, ethics, and community value. - When uploading a revision during discussion, summarize the exact changes and give a compact diff map. Do not assume reviewers or ACs will re-read the full PDF. - Keep identity hidden. Do not reveal lab, institution, funding, private repository ownership, or author-controlled analytics. - Use private links only when the Author Guide permits them and only for the intended reviewers/ACs. - Escalate low-quality, abusive, or suspected LLM-generated reviews through the official confidential channel rather than arguing publicly. ## Reply pattern 1. State the reviewer concern in one sentence. 2. Provide the correction, evidence, or concession. 3. Point to the
- Response strategy
- Reply pattern
- Public-forever calibration
- Worked vignette
- Pushback patterns and fixes
- Output format
What does the iclr-author-response skill do?
Use when drafting ICLR OpenReview author discussion replies, revision notes, public comments, restricted comments, and responses to reviewer or AC concerns during the discussion period. Use when reviews land and you must decide what to answer publicly versus privately, how to log a discussion-period revision, or how to move a borderline score before the AC writes the meta-review for the permanent record.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iclr-author-response --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.