iros-author-response
Use when responding to IROS reviews given the traditional no-rebuttal model — pre-answering objections in the paper and video before submission, addressing the meta-review through camera-ready edits, writing RA-L response letters for the journal pathway, and drafting reject-to-ICRA/CoRL/RA-L resubmission memos under double-anonymous rules.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iros-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.
# IROS Author Response Use this after IROS reviews arrive — and, crucially, *before* submission too, because IROS traditionally offers **no rebuttal**. The reviews come with the decision, so the "response" is spread across three real channels: pre-answering in the paper, editing the camera-ready, and, if rejected or on the journal route, a response letter or resubmission memo. Confirm the current cycle's policy before assuming a rebuttal window does or does not exist. ## Channel 1: pre-answer before you submit The most effective IROS author response is written before anyone reviews the paper. Anticipate the standard objections and disarm them in the body and the video: - "Did it really work?" → shown, uncut trials plus a labeled failure in the video. - "Is it reliable or cherry-picked?" → trial counts, resets, and a failure taxonomy in the body. - "Does sim imply real?" → a stated sim-to-real gap, not an implied zero. - "Is the baseline fair?" → same-platform baseline with comparable tuning. ## Channel 2: the camera-ready revision When the decision is accept (often with requested changes), the meta-review is your instruction set. Integrate its asks without inflating the contributio
- Channel 1: pre-answer before you submit
- Channel 2: the camera-ready revision
- Channel 3: RA-L response letters and resubmission memos
- Micro-example: turning a rejection into a plan
- Output format
What does the iros-author-response skill do?
Use when responding to IROS reviews given the traditional no-rebuttal model — pre-answering objections in the paper and video before submission, addressing the meta-review through camera-ready edits, writing RA-L response letters for the journal pathway, and drafting reject-to-ICRA/CoRL/RA-L resubmission memos under double-anonymous rules.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iros-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.