Rebuttal Writing Skill for Claude
Write point-by-point rebuttals to reviewer comments. Extract concerns from reviews, generate evidence-based responses, and format as a structured rebuttal document. Use after receiving peer review feedback.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/lingzhi227/agent-research-skills --skill rebuttal-writingThe instruction itself
10 sections, as written by the authorRebuttal Writing
Generate structured, evidence-based rebuttals to peer review comments.
Input
$0— Reviewer comments (text file, or pasted directly)- Optional: current paper draft for reference
References
- Rebuttal prompts and format templates:
~/.claude/skills/rebuttal-writing/references/rebuttal-prompts.md
Workflow
Step 1: Parse Review Comments
For each reviewer:
- Extract individual concerns/questions/weaknesses
- Categorize each: major concern, minor concern, question, suggestion
- Identify the core issue behind each concern
Step 2: Generate Responses
For each concern:
- Acknowledge the reviewer's point
- Respond with evidence — cite specific sections, equations, experiments, or results from the paper
- Describe what was done (not what will be done) — "We have added...", "Our experiments show..."
- If additional experiments are needed, describe the new results concretely
Step 3: Format Rebuttal
Use the standard rebuttal format:
# Response to Reviewers
We thank all reviewers for their constructive feedback. We address each concern below.
## Reviewer #1
**Concern #1:** [extracted concern]
**Author Response:** [detailed response with evidence]
**Concern #2:** [extracted concern]
**Author Response:** [detailed response with evidence]
## Reviewer #2
...
Step 4: Summary of Changes
Add a brief summary at the top listing all major changes made to the paper:
- New experiments added
- Sections revised
- Clarifications made
Rules
- Reply with what was done, not what will be done — "We have conducted additional experiments" not "We will conduct..."
- Be specific — Reference exact sections, table numbers, equation numbers
- Be respectful — Thank reviewers, acknowledge valid concerns
- Address every concern — Do not skip any reviewer point
- Provide evidence — Every response should include concrete data, citations, or reasoning
- Keep responses concise — Detailed enough to address the concern, but not padded
- Highlight changes — When referring to modified text, use blue text or clearly mark revisions
Related Skills
- Upstream: self-review, paper-revision
- Downstream: paper-compilation
- See also: data-analysis
Other skills for the same job
different authors, same section of the catalogue
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementing any feature or bugfix, before writing implementation code
Use when you have a spec or requirements for a multi-step task, before touching code
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
| Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
Official Opentrons Protocol API for OT-2 and Flex robots. Use when writing protocols specifically for Opentrons hardware with full access to Protocol API v2 features. Best for production Opentrons protocols, official API compatibility. For multi-vendor automation or broader equipment control use pylabrobot.
How to use it
Take lingzhi227/rebuttal-writing from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.