Install
$ agentstack add skill-aravindan20-claude-research-paper-os-paper-revision ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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](../self-review/)
- Downstream: [paper-compilation](../paper-compilation/)
- See also: [rebuttal-writing](../rebuttal-writing/), [paper-writing-section](../paper-writing-section/)
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: ARAVINDAN20
- Source: ARAVINDAN20/Claude-Research-Paper-OS
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.