paper-rebuttal
Guides writing effective rebuttals after receiving peer review feedback. Covers review diagnosis (score-driven color-coding), response strategy (champion identification, common-theme consolidation), tactical writing (18 rules), and counterintuitive rebuttal principles. Use when: user received reviewer scores/comments, needs to write a rebuttal or author response, wants to respond to specific criticism (e.g. 'limited novelty', 'missing baselines'), mentions 'rebuttal', 'reviewer comments', 'author response', or 'respond to reviewers'. Do NOT use for pre-submission self-review (use paper-review
npx skills add BioTender-max/awesome-bio-agent-skills --skill paper-rebuttal --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.
# Paper Rebuttal A systematic approach to writing rebuttals after receiving peer review feedback. The goal is not to defend every point — it's to move scores by addressing the concerns that actually drive them. ## When to Use This Skill - User received reviewer comments and needs to write a rebuttal - User asks how to respond to specific reviewer criticism - User wants to analyze reviews strategically before responding - User mentions "rebuttal", "reviewer comments", "review feedback", "respond to reviewers" > For pre-submission self-review and catching weaknesses before they become reviewer complaints, use the `paper-review` skill. ## Step 1: Diagnose Reviews Before writing a single word, answer: **"Why did this reviewer give this exact score?"** Not what they wrote — what drove the score. Most researchers skip this and address every comment equally. That is a mistake. ### Score Diagnosis For each reviewer, ask: "What would move this reviewer from their current score to acceptance?" | Score Range | Typical Situation | Your Strategy | |-------------|------------------|---------------| | 7+ | Already your champion | Arm them with ammunition for the discussion phase | | 5-6 | On the
- When to Use This Skill
- Step 1: Diagnose Reviews
- Score Diagnosis
- Color-Code Every Comment
- Identify the Invisible Question
- Step 2: Plan Response Strategy
- Categorize Every Concern
- Identify Common Themes
- Distinguish Actionable vs. Subjective
- The Champion Strategy
- Step 3: Write the Rebuttal
- Structure
- Per-Concern Format
- The Neutral Third-Party Test
What does the paper-rebuttal skill do?
Guides writing effective rebuttals after receiving peer review feedback. Covers review diagnosis (score-driven color-coding), response strategy (champion identification, common-theme consolidation), tactical writing (18 rules), and counterintuitive rebuttal principles. Use when: user received reviewer scores/comments, needs to write a rebuttal or author response, wants to respond to specific criticism (e.g. 'limited novelty', 'missing baselines'), mentions 'rebuttal', 'reviewer comments', 'author response', or 'respond to reviewers'. Do NOT use for pre-submission self-review (use paper-review
How do I install it?
Run `npx skills add BioTender-max/awesome-bio-agent-skills --skill paper-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 BioTender-max/awesome-bio-agent-skills, a repository with 135 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.