Agent Skills

rebuttal-writing

researchlingzhi2271.5K installs

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

npx skills add https://github.com/lingzhi227/agent-research-skills --skill rebuttal-writing
SKILL.md

Rebuttal 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:

  1. Extract individual concerns/questions/weaknesses
  2. Categorize each: major concern, minor concern, question, suggestion
  3. Identify the core issue behind each concern

Step 2: Generate Responses

For each concern:

  1. Acknowledge the reviewer's point
  2. Respond with evidence — cite specific sections, equations, experiments, or results from the paper
  3. Describe what was done (not what will be done) — "We have added...", "Our experiments show..."
  4. 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

Related skills

researchmattpocock575KInvestigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.paper-context-resolverlllllllama451KRigor Paper Context helper for README-first deep learning repo reproduction. Use only when the README and repository files leave a narrow reproduction-critical gap and the task is to resolve a specific paper detail such as dataset split, preprocessing, evaluation protocol, checkpoint mapping, or runtime assumption from primary paper sources while recording conflicts. Do not use for general paper summary, repo scanning, environment setup, command execution, title-only paper lookup, or replacing Renv-and-assets-bootstraplllllllama450KRigor Setup skill for README-first deep learning repo reproduction. Use when the task is specifically to prepare a conservative conda-first environment, checkpoint and dataset path assumptions, cache location hints, and setup notes before any run on a README-documented repository. Do not use for repo scanning, full orchestration, paper interpretation, final run reporting, or generic environment setup that is not tied to a specific reproduction target.ai-research-explorelllllllama311KRigor Explore compatible skill slug for meaningful and potentially novel deep learning research candidates. Use when the researcher has chosen the task family, dataset, benchmark, evaluation method, provided SOTA references, and wants candidate-only exploration on top of `current_research` with auditable repo understanding, idea gating, fair comparison, and governed experiments written to `explore_outputs/`. Do not use for README-first trusted reproduction, open-ended direction finding, narrow c

Search skills and MCP servers

Fuzzy search across 23,137 skills and servers