paper-polish

Revise compiled research manuscripts through two bounded issue-driven passes and one final factual check.

Updated Aug 18, 2026
One-click install
npx skills add https://github.com/Nitrogen216/awesome-dsh-mods --skill paper-polish-nitrogen216
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: paper-polish
Source: https://github.com/Nitrogen216/awesome-dsh-mods/tree/main/modes/dsh-autoresearch/skills/paper-polish
Command: npx skills add https://github.com/Nitrogen216/awesome-dsh-mods --skill paper-polish-nitrogen216

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a research paper is compiled, authors often fall into open-ended revision loops or accept unsupported reviewer suggestions. This Skill bounds manuscript revision to at most two issue-driven passes plus one consolidated factual check, keeping edits evidence-backed and preventing scope creep. ## Core Features & Use Cases - Two Bounded Revision Passes: Pass 1 audits argument and evidence (claim-evidence alignment, contribution statement, section order); Pass 2 audits presentation (terminology, captions, page budget, figure readability). - Severity-Tagged Issue Tracking: Every actionable issue is recorded with severity (critical, major, minor), location, evidence, and a minimal fix, with recompilation after material edits. - Final Factual Check: Writes paper/FINAL_CHECK.md mapping headline claims to evidence, verifying reported numbers against raw artifacts, and validating citations, figures, and venue rules. - Use Case: After compiling a venue-neutral research paper, run this Skill to tighten claim wording, fix caption and layout issues, and produce a final factual audit without adding new experiments or altering the promoted research pipeline. ## Quick Start Use the paper-polish skill to revise the compiled manuscript through bounded evidence-backed passes and produce the final factual check.

Frequently Asked Questions about paper-polish

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I revise a research paper without endless rewriting loops?▼

Bound revision to at most two issue-driven passes: one for argument and evidence, one for presentation. Stop early when no new material issue remains, and record repeated concerns once instead of rewriting to satisfy wording preferences.

How to verify claims and numbers in a compiled research manuscript?▼

Run a single consolidated factual check that maps every headline claim to its evidence, compares each reported number against its raw artifact, and verifies every citation exists and supports the attached statement. The result is written to paper/FINAL_CHECK.md.

Can this skill add new experiments or citations during revision?▼

No. It never adds new experiments, method components, theorems, results, or citations merely because a reviewer asks. Such requests are recorded in paper/OPEN_EVIDENCE_GAPS.md and returned to the user instead.

When should paper polishing be run in a research workflow?▼

Run it after the paper has been compiled, not during drafting or experimentation. It operates on the current manuscript source and PDF, and never alters the promoted research method or pipeline state.

What are the limitations of bounded manuscript revision?▼

It applies minor fixes only when local and low risk, and rejects changes unsupported by existing sources. It cannot resolve missing evidence gaps itself; unresolved gaps are documented and returned to the user for decision.