agentleFS
yuangao-tumyuangao-tum/rebuttal-skills/skills/write-rebuttal/SKILL.md

write-rebuttal

Skill5 starsChanged 4 months agoMITView on GitHub

Write conference/journal author-response rebuttals that clarify and convince, following Parikh–Batra–Lee's "How we write rebuttals" method (two-audience mindset, itemize→brain-dump→draft→revise, 18 tactics, the neutral-third-party test). Use when responding to peer reviews, writing an author response / rebuttal / reviewer reply for NeurIPS, ICLR, ICML, CVPR/ICCV/ECCV, AAAI, ACL/ARR/EMNLP, or any venue, planning rebuttal experiments, or when the user says "rebuttal", "author response", "respond to reviewers".

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. ShaishavMaisuria/research-paper-lifecycle-skills★ 59same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Tip 12: prefer designs that end in a statistic (effect size, CI, p-value, a baseline delta) — that is the currency of a rebuttal.

    line 71
  2. Distinctive:

    Never pre-write the outcome: If a response sentence already asserts a result ("the increase is significant") before the experiment is run, …

    line 75

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Write Rebuttal

Distilled from Devi Parikh, Dhruv Batra & Stefan Lee, How we write rebuttals (https://deviparikh.medium.com/how-we-write-rebuttals-dc84742fece1).

A rebuttal exists to clarify and convince — it is one stage in a deliberative scientific process, not a fight to win. Optimize it for the reader, not for venting.

The one idea that governs everything

Two audiences, and beginners forget the second one:

  1. Reviewers — read your paper, may have forgotten details. Goal: clarify doubts, correct misunderstandings, push back on mischaracterizations, incorporate feedback.
  2. Area Chair / meta-reviewer — likely has not read your paper closely and won't re-read it. Goal: show good-faith effort, give a fair summary, make it obvious each concern was addressed, flag bad-faith reviewing, and help them decide.

Most new researchers write only for (1). Writing for (2) is what moves decisions. Think of it like debate: you convince the judges (AC), not your opponents.

The acceptance test for every response — the "neutral third-party" test: Could someone who has not read your paper or the reviews tell, from your rebuttal alone, that the concern was addressed? If not, rewrite it (self-contained; Tip 8).

Process (do these in order)

  1. Itemize — put every reviewer comment/question/concern in a spreadsheet, one row each, columns per reviewer. Do this first, ASAP: it guarantees nothing is missed, surfaces shared concerns to consolidate, and identifies needed experiments early while there's still time to run them.
  2. Brain-dump — rough responses in the sheet, no style/length worry. Collaborative.
  3. Draft — turn the consensus into concise responses covering every point.
  4. Revise — reread the reviews, check completeness, prioritize the majors, fit the space limit. Run the neutral-third-party test on each response.

See references/rebuttal-skeleton.md for a ready structure (summary → common concerns → per-reviewer → note to AC), micro-templates, and two AC "dashboard" summary tables. assets/rebuttal-template.tex is the compilable LaTeX implementation — use it only where free-form PDF responses are accepted.

The 18 tactics (apply while drafting)

Full detail + examples in references/eighteen-tips.md. The load-bearing ones:

  • Start positive (1) — open with a short recap of the praise; don't let strengths be forgotten.
  • Order by strength, not by reviewer (2) — lead with the biggest concerns you have good answers for; trail minor/weaker points.
  • Quote → direct answer → detail (3) — quote the concern, answer Yes/No/one line in bold first, then elaborate.
  • Stats speak louder than words (12) — whenever you disagree with a reviewer, back it with a number, not an argument. Ask "can I establish this with data?"
  • Don't promise, do (13) — compute the number/analysis now and put it in the rebuttal; then say you'll fold it into the paper. Never leave "we will add X" as the whole answer.
  • Get credit for what's already there (9) — if they asked for something in the paper, cite the line/section and restate it.
  • Be transparent (15) — venue bars new experiments? no clean intuition? out of GPUs? result is null? Say so honestly and reframe — do not overclaim.
  • Answer the intent, not just the literal question (5), be self-contained (8), consolidate shared concerns (10), thank real effort (17), and remember the humans (18) — seek common ground unless a reviewer is bad-faith (16).

Applying it to rebuttal experiments

The guide shapes what you run, not just how you write:

  • Itemize first (Step 1) to derive the experiment list from concerns, then map each experiment to the exact sentence/slot it will fill.
  • Tip 2 + 13: prioritize experiments that will reliably yield a clean, defensible number inside the response window over high-variance gambles. A promised experiment that doesn't land is worse than a transparent limitation (Tip 15).
  • Tip 12: prefer designs that end in a statistic (effect size, CI, p-value, a baseline delta) — that is the currency of a rebuttal.
  • Tip 14 (be receptive): when a reviewer proposes a baseline/ablation, try it — "maybe it will work" — rather than arguing why it wouldn't.
  • Never pre-write the outcome. If a response sentence already asserts a result ("the increase is significant") before the experiment is run, that violates Tips 13 and 15 — fill it only with the computed value, or reframe to what the data supports.

Anti-patterns (auto-reject in review)

  • A response that fails the neutral-third-party test (needs the paper to make sense).
  • "We will add / we plan to" with no number in the rebuttal itself (violates 13).
  • Ordered reviewer-by-reviewer with the weakest answer first (violates 2).
  • Arguing a point you could have measured (violates 12).
  • Combative tone, litigating instead of clarifying (violates 4, 18).
  • Silent overclaim of a result the data doesn't yet support (violates 13, 15).
  • Ignoring the AC entirely — no decision-oriented summary (the core miss).

Optional check

python scripts/lint_rebuttal.py <rebuttal.tex|.md> flags promise-language ("we will add", "in the final version"), unfilled placeholders (\Rtodo, TODO, [\ldots]), outcomes asserted next to unfilled slots, a missing AC section, a missing opening thanks, and the absence of any statistics. Advisory only — judgment still yours.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.