/paper-revision
Revise papers based on reviewer feedback. Map reviewer concerns to specific sections, apply targeted edits, run additional experiments if needed, and verify improvements. Use after receiving peer review with revision requests.
$ npx -y skills add lingzhi227/agent-research-skills --skill paper-revision --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/paper-revision
Context preview
The summary Claude sees to decide when to auto-load this skill.
Revise papers based on reviewer feedback. Map reviewer concerns to specific sections, apply targeted edits, run additional experiments if needed, and verify improvements. Use after receiving peer review with revision requests.
SKILL.md
paper-revision.SKILL.mdname: paper-revision
description: Revise papers based on reviewer feedback. Map reviewer concerns to specific sections, apply targeted edits, run additional experiments if needed, and verify improvements. Use after receiving peer review with revision requests.
argument-hint: [reviews-or-draft]
Paper Revision
Systematically revise papers based on reviewer feedback.
Input
- `$0` — Reviewer comments/feedback
- `$1` — Current paper draft (main.tex or paper directory)
References
- Revision workflow and prompts: `~/.claude/skills/paper-revision/references/revision-prompts.md`
Workflow
Step 1: Parse and Prioritize Concerns
For each reviewer comment: 1. Extract the specific concern 2. Classify: major revision, minor revision, question, suggestion 3. Map to affected paper section(s) 4. Prioritize: address major concerns first
Step 2: Plan Revisions
Create a revision plan:
Concern → Affected Section → Required Action → New Content/Experiment
Categories of actions:
- **Clarification**: Rewrite text for clarity
- **Additional experiment**: Run new experiment, add results
- **New analysis**: Add ablation, statistical test, or comparison
- **Structural change**: Move, merge, or split sections
- **Citation**: Add missing references
Step 3: Execute Revisions
For each planned revision: 1. Read the current section 2. Apply targeted edits (preserve surrounding structure) 3. If new experiments needed: use experiment-code skill 4. If new figures/tables needed: use figure-generation / table-generation skills 5. Mark changes (use `\textcolor{blue}{...}` for revised text)
Step 4: Verify Improvements
- Re-run self-review skill to check if scores improved
- Verify all reviewer concerns are addressed
- Check that revisions don't introduce new issues
- Ensure page count still fits venue requirements
Step 5: Write Revision Summary
Generate a diff summary:
- List all changes made with section references
- Note any new experiments, figures, or tables added
- Cross-reference each change to the reviewer concern it addresses
Rules
- Address EVERY reviewer concern — do not skip any
- Preserve paper structure unless structural change is explicitly needed
- New results must come from actual experiments, not hallucinated
- Mark all revised text clearly for the reviewers
- Keep a copy of the previous version before revising
- Compare new scores vs previous scores after revision
Related Skills
- Upstream: [self-review](../self-review/)
- Downstream: [paper-compilation](../paper-compilation/)
- See also: [rebuttal-writing](../rebuttal-writing/), [paper-writing-section](../paper-writing-section/)
Read more
name: paper-revision description: Revise papers based on reviewer feedback. Map reviewer concerns to specific sections, apply targeted edits, run additional experiments if needed, and verify improvements. Use after receiving peer review with revision requests. argument-hint: [reviews-or-draft]
Paper Revision
Systematically revise papers based on reviewer feedback.
Input
- `$0` — Reviewer comments/feedback
- `$1` — Current paper draft (main.tex or paper directory)
References
- Revision workflow and prompts: `~/.claude/skills/paper-revision/references/revision-prompts.md`
Workflow
Step 1: Parse and Prioritize Concerns
For each reviewer comment: 1. Extract the specific concern 2. Classify: major revision, minor revision, question, suggestion 3. Map to affected paper section(s) 4. Prioritize: address major concerns first
Step 2: Plan Revisions
Create a revision plan:
Concern → Affected Section → Required Action → New Content/Experiment
Categories of actions:
- **Clarification**: Rewrite text for clarity
- **Additional experiment**: Run new experiment, add results
- **New analysis**: Add ablation, statistical test, or comparison
- **Structural change**: Move, merge, or split sections
- **Citation**: Add missing references
Step 3: Execute Revisions
For each planned revision: 1. Read the current section 2. Apply targeted edits (preserve surrounding structure) 3. If new experiments needed: use experiment-code skill 4. If new figures/tables needed: use figure-generation / table-generation skills 5. Mark changes (use `\textcolor{blue}{...}` for revised text)
Step 4: Verify Improvements
- Re-run self-review skill to check if scores improved
- Verify all reviewer concerns are addressed
- Check that revisions don't introduce new issues
- Ensure page count still fits venue requirements
Step 5: Write Revision Summary
Generate a diff summary:
- List all changes made with section references
- Note any new experiments, figures, or tables added
- Cross-reference each change to the reviewer concern it addresses
Rules
- Address EVERY reviewer concern — do not skip any
- Preserve paper structure unless structural change is explicitly needed
- New results must come from actual experiments, not hallucinated
- Mark all revised text clearly for the reviewers
- Keep a copy of the previous version before revising
- Compare new scores vs previous scores after revision
Related Skills
- Upstream: [self-review](../self-review/)
- Downstream: [paper-compilation](../paper-compilation/)
- See also: [rebuttal-writing](../rebuttal-writing/), [paper-writing-section](../paper-writing-section/)
31 skills for Claude Code covering the full academic research paper lifecycle — from literature search to slide generation — plus GitHub repository analysis for research topics. Extracted from 17 GitHub repos studying LLM-agent-driven research automation.
Other skills on agent-research-skills.
- /algorithm-design
Design algorithms with LaTeX pseudocode and UML diagrams. Generate algorithmic environments, Mermaid class/sequence diagrams, and ensure consistency between pseudocode and implementation. Use when formalizing methods for a paper.
Open skill - /atomic-decomposition
Decompose research ideas into atomic, self-contained concepts with bidirectional math-code mapping. For each concept, extract the math formula from papers and find code implementations. Use for complex system papers requiring formal grounding.
Open skill - /backward-traceability
Make every number in the final PDF traceable to the exact code line that produced it. Uses \hypertarget/\hyperlink LaTeX commands and \num{formula} evaluated at compile time. Use for reproducibility and data integrity verification.
Open skill - /citation-management
Manage BibTeX citations for LaTeX papers. Harvest missing citations from a draft using Semantic Scholar, validate cite keys against .bib files, deduplicate entries, and format bibliography. Use when working with references, BibTeX, or citations.
Open skill - /code-debugging
Debug experiment code with structured error analysis. Categorize errors, apply targeted fixes with retry logic, and use reflection to prevent recurring issues. Use when experiment code fails or produces incorrect results.
Open skill - /data-analysis
Generate statistical analysis code with 4-round review. Select appropriate statistical tests, interpret results, and produce analysis reports with p-values, effect sizes, and confidence intervals. Use when analyzing experimental data for a paper.
Open skill

