mcpbeat

Paper Revision

lingzhi227/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.

2k tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
256
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/lingzhi227/agent-research-skills --skill paper-revision

The instruction itself

11 sections, as written by the author

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:

  • Extract the specific concern
  • Classify: major revision, minor revision, question, suggestion
  • Map to affected paper section(s)
  • 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:

  • Read the current section
  • Apply targeted edits (preserve surrounding structure)
  • If new experiments needed: use experiment-code skill
  • If new figures/tables needed: use figure-generation / table-generation skills
  • 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
  • Downstream: paper-compilation
  • See also: rebuttal-writing, paper-writing-section

How to use it

Copy the folder

Take lingzhi227/paper-revision from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

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.