
Paper Revision
Turn messy peer-review comments into a prioritized revision plan and targeted edits for ML papers and agent-driven research pipelines.
Overview
Paper Revision is an agent skill most often used in Ship (also Validate and Build) that classifies reviewer comments and drives structured manuscript and experiment revisions for research agents.
Install
npx skills add https://github.com/lingzhi227/agent-research-skills --skill paper-revisionWhat is this skill?
- Four-type concern classifier (Major / Minor / Question / Suggestion) with P0–P3 priority
- Per-concern revision planning template with affected sections and required actions
- Full pipeline re-run pattern when major revisions need new experiments or analysis
- Before/after score comparison and verification that each concern is addressed
- Targeted edit prompts for clarity, methodology, and citation fixes
- 4 concern types with P0–P3 priority tiers
- 4-step full pipeline re-run when major revision needs new experiments
Adoption & trust: 767 installs on skills.sh; 114 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You received a dense reviewer report and no clear order of operations for which comments need new experiments versus a wording fix.
Who is it for?
Indie researchers or solo builders using AI-Scientist-style agents who need a repeatable peer-review response workflow with optional experiment reruns.
Skip if: Casual blog editing, non-academic copy, or teams with an already-approved camera-ready PDF and no open review cycle.
When should I use this skill?
When responding to peer or internal review on a research paper or when an agent pipeline must refine a report after scored feedback.
What do I get? / Deliverables
You get a prioritized revision plan per concern, executed edits or phased reruns, and a checklist that each Major/Minor item was addressed before resubmission.
- Per-concern revision plan with type, sections, and steps
- Updated paper sections or full rewritten draft after pipeline rerun
- Concern-addressed verification checklist
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Peer-response and rebuttal work sits in Ship under review: you are improving work before acceptance, not discovering the idea or shipping product code. Review subphase matches systematic handling of reviewer concerns, severity triage, and structured revision—not ad-hoc paragraph tweaks.
Where it fits
Scope which reviewer demands require new ablations versus wording before you commit GPU time.
Re-run experiment and analysis phases after injecting reviewer notes while preserving prev_code and prev_results.
Execute targeted section edits for Minor and Question comments with explicit affected-section mapping.
How it compares
Use instead of unstructured “fix the reviews” chat when you need concern typing and pipeline-aware reruns.
Common Questions / FAQ
Who is paper-revision for?
Solo builders and small research teams running agent-assisted paper workflows who must respond to formal peer review or internal review rounds.
When should I use paper-revision?
Use it in Ship when revising after review; in Validate when tightening claims before submission; and in Build when rerunning experiment or analysis phases after Major revision requests.
Is paper-revision safe to install?
Review the Security Audits panel on this Prism skill page and the source repo before piping reviewer text or code into automated rerun pipelines.
SKILL.md
READMESKILL.md - Paper Revision
# Paper Revision Prompts Extracted from AI-Scientist (perform_improvement) and AgentLaboratory (report_refinement). ## Concern Classification ``` For each reviewer comment, classify as: | Type | Description | Priority | |------|-------------|----------| | Major Revision | Fundamental flaw, missing experiment, wrong methodology | P0 | | Minor Revision | Clarity issues, missing details, presentation | P1 | | Question | Reviewer seeks clarification | P2 | | Suggestion | Nice-to-have improvement | P3 | ``` ## Revision Planning Template ``` For each concern: Concern: [Extracted reviewer concern] Type: [Major/Minor/Question/Suggestion] Affected Section(s): [Section name(s)] Required Action: [Clarification/Experiment/Analysis/Structural/Citation] Plan: - Step 1: ... - Step 2: ... New Content Needed: [Yes/No - describe if yes] ``` ## Revision Execution (AgentLaboratory) ### Full Pipeline Re-run When a major revision requires new experiments: ``` 1. Save current state: prev_code = current_code prev_results = current_results prev_paper = current_paper 2. Inject reviewer feedback as notes: notes += "Reviewer requested: {concern}" 3. Re-run affected phases: - If new experiment needed: re-run experiment phase - If new analysis needed: re-run analysis phase - Always re-run writing phase for affected sections 4. Compare new vs previous: - Score improvement: new_score - prev_score - Verify concern addressed ``` ## Targeted Edit Prompts ### For Clarification Concerns ``` The reviewer found this passage unclear: "{original_text}" Their comment: "{reviewer_comment}" Rewrite the passage to address the reviewer's concern. Keep the same meaning but improve clarity. Mark revised text with \textcolor{blue}{...}. ``` ### For Missing Experiment Concerns ``` The reviewer requests: "{reviewer_comment}" Current experimental setup: {current_setup} Available resources: {resources} Design a new experiment to address this concern: 1. What to test 2. Expected outcome 3. How to present results (table/figure) ``` ### For Citation Concerns ``` The reviewer suggests citing: "{suggested_area}" Search for relevant papers and add citations. Integrate citations naturally into the text. Do not just add a parenthetical — explain the connection. ``` ## Change Marking ```latex % Use blue text for all revisions \usepackage{xcolor} \newcommand{\revision}[1]{\textcolor{blue}{#1}} % Example usage: \revision{We additionally evaluate on the CIFAR-100 dataset to address the reviewer's concern about generalization.} ``` ## Revision Verification Checklist ``` After all revisions: [ ] Every reviewer concern has been addressed [ ] All revised text is marked in blue [ ] New results are from actual experiments (not fabricated) [ ] Page count still fits venue requirements [ ] No new LaTeX errors introduced [ ] All new citations are in .bib file [ ] Self-review score improved or maintained [ ] Revision summary cross-references every concern ``` ## Revision Summary Template ``` # Revision Summary ## Changes Overview - N sections modified - M new experiments added - K new figures/tables added ## Detailed Changes ### Reviewer 1, Concern 1 (Major) **Concern**: [what they said] **Action**: [what we did] **Location**: Section X, paragraph Y **New content**: [brief description] ### Reviewer 1, Concern 2 (Minor) ... ## Score Comparison | Metric | Before | After | |--------|--------|-------| | Overall | 5 | 7 | | Clarity | 6 | 8 | | ... | ... | ... | ``` --- 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 director