Agent skill · Documentation

io-rebuttal

Use when writing the response to an International Organization (IO) revise-and-resubmit. IO R&Rs come from expert IR referees whose anonymous reviews the editors return with a decision letter, and the editor adjudicates. The response must convert each reviewer on the IR theory and design without alienating the editor, keep the manuscript double-blind, and keep results and proofs re-runnable for IO's pre-final-acceptance verification. Structures the response; it does not fabricate new results.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill io-rebuttal --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: International-Organization-Skills/skills/io-rebuttal/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

# R&R Rebuttal (io-rebuttal) An IO **R&R is a strong signal** — first-round accepts are rare at the field's leading IR journal. The editors return **anonymous expert reviews** with a decision letter and **adjudicate**, so the response must move *every* reviewer toward yes on the **IR theory and design** while keeping the editor confident the revision is convergent — and keep the package verifiable for the post-conditional-acceptance check. ## When to trigger - An R&R decision arrived and you are planning the revision + response memo - Reviewers disagree (e.g., a rationalist and a constructivist referee pull in opposite directions) - A reviewer requests analyses or model changes that would alter the paper's claims - Writing the cover note to the editor summarizing the revision ## Strategy 1. **Read the editor's letter as the rubric.** The editor signals which points are decisive — solve those first; the editor adjudicates disagreements among referees. 2. **One point-by-point response, every comment addressed.** Quote each comment, then respond. Never skip one — silence reads as non-compliance. 3. **Concede or rebut explicitly, with evidence.** For each: did what was asked (say where

What's inside
Steps it walks through
  1. When to trigger
  2. Strategy
  3. Response-memo format
  4. Referee-objection playbook (the recurring IO pushbacks and their fixes)
  5. Worked rebuttal vignette (illustrative)
  6. Anti-patterns
  7. Output format
  8. Supplementary resources
More from Awesome-Journal-Skills
All skills →
About this skill
What does the io-rebuttal skill do?

Use when writing the response to an International Organization (IO) revise-and-resubmit. IO R&Rs come from expert IR referees whose anonymous reviews the editors return with a decision letter, and the editor adjudicates. The response must convert each reviewer on the IR theory and design without alienating the editor, keep the manuscript double-blind, and keep results and proofs re-runnable for IO's pre-final-acceptance verification. Structures the response; it does not fabricate new results.

How do I install it?

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