icra-review-process
Use when explaining or strategizing around ICRA's review pipeline — the RAS Conference Editorial Board of Editors and Associate Editors, reviewer recruitment through PaperPlaza, the absence of an author rebuttal in the classic ICRA flow, the January accept/reject decision, and how this differs from RA-L's revise-capable journal review.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icra-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.
# ICRA Review Process ICRA review is run not by ad-hoc program committees but by a standing RAS **Conference Editorial Board (CEB)** structure operating inside PaperPlaza. The mechanics differ enough from both journals and ML conferences that authors mis-model them — most consequentially around the rebuttal that never comes. ## The pipeline ```text Sep 15 PaperPlaza deadline │ ▼ Editor (area lead) assigns paper to an Associate Editor (AE) │ by keyword match from your chosen PaperPlaza topics ▼ Oct-Dec AE recruits 2-3 reviewers; reviews written on the standard │ RAS form (contribution, technical soundness, clarity, │ experimental validation, video comments) ▼ Dec-Jan AE writes a summary report reconciling the reviews and │ recommends; Editors + program committee calibrate across areas ▼ Jan 31 accept or reject — no conditional accepts, no shepherding, │ and in the classic ICRA flow NO author rebuttal phase ▼ Mar camera-ready with voluntary reviewer-driven revisions ``` Two structural notes. First, keyword choice at submission is not paperwork — it routes the manuscript to an Editor's area and thereby to the reviewer pool most or least sympathetic to it. Second, reviewer identity pra
- The pipeline
- No rebuttal: consequences, not complaints
- What the review form rewards
- Where author leverage actually exists
- Calibrating expectations
- Contrast with RA-L review
- Reading a decision packet
- Output format
What does the icra-review-process skill do?
Use when explaining or strategizing around ICRA's review pipeline — the RAS Conference Editorial Board of Editors and Associate Editors, reviewer recruitment through PaperPlaza, the absence of an author rebuttal in the classic ICRA flow, the January accept/reject decision, and how this differs from RA-L's revise-capable journal review.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icra-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.