Agent skill · Documentation

icra-author-response

Use when responding to ICRA reviews in the channels that actually exist — turning decision-day reviewer comments into a disciplined camera-ready revision, writing the revise-and-resubmit response letter on the RA-L pathway, or converting an ICRA reject into a targeted IROS or RA-L resubmission — since classic ICRA offers no rebuttal.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icra-author-response --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Path: ICRA-Skills/skills/icra-author-response/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# ICRA Author Response At most conferences "author response" means a rebuttal window. Classic ICRA has none (verify the current cycle — see `icra-review-process`): reviews arrive together with the January decision. Author response at ICRA therefore happens in three real channels, each with its own craft: the **camera-ready revision** after acceptance, the **RA-L response letter** if the work travels the journal pathway, and the **resubmission memo** after a reject. Doing these well is a skill; pretending a rebuttal exists is a planning error. ## Channel 1: the camera-ready revision (accepted papers) Reviewer comments on an accepted ICRA paper are advisory — no one re-checks compliance — but ignoring them is shortsighted: reviewers are your first readers, their confusions predict everyone else's, and the same people may review the journal extension. Triage each comment: | Comment type | Action in camera-ready | Budget guard | |---|---|---| | Factual/math error caught | fix unconditionally | always fits | | Ambiguity that misled a reviewer | rewrite the passage | high priority | | Missing reference | add it | cheap | | "Add experiment X" | usually defer to journal version; add only i

What's inside
Steps it walks through
  1. Channel 1: the camera-ready revision (accepted papers)
  2. Channel 2: the RA-L response letter (journal pathway)
  3. Channel 3: the resubmission memo (rejected papers)
  4. Tone calibration (robotics reviewers, specifically)
  5. Discipline common to all three channels
  6. Ledger template
  7. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the icra-author-response skill do?

Use when responding to ICRA reviews in the channels that actually exist — turning decision-day reviewer comments into a disciplined camera-ready revision, writing the revise-and-resubmit response letter on the RA-L pathway, or converting an ICRA reject into a targeted IROS or RA-L resubmission — since classic ICRA offers no rebuttal.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icra-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.

Keep going