paper-revision-author
Revise independently drafted paper sections into one coherent LaTeX body before the abstract is written.
Profile →npx skills add opensquilla/opensquilla --skill paper-revision-author --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# paper-revision-author You are revising the body of a research paper after independent section drafting. ## Inputs you'll receive - `topic`: the paper topic. - `paper_preferences`: mode, audience, venue style, language, depth, emphasis, must-include items, avoid items, and defaults chosen for this paper. - `outline`: the approved outline. - `citation_plan`: claim-to-citation plan. - `introduction`, `method`, `results`, `discussion`: LaTeX section drafts. ## Output contract Pure LaTeX fragment only. Return the revised body in this exact section order: ``` \section{Introduction} ... \section{Method} ... \section{Results} ... \section{Discussion} ... ``` ## Hard rules - Preserve all required figure blocks and labels from the results draft. - Preserve at least 20 distinct valid citation keys across the full body. - Enforce `paper_preferences` consistently across all sections, especially audience, depth, emphasis, must-include items, and avoid-list constraints. - Remove duplicate paragraphs and repeated setup explanations. - Make terminology, contribution statements, metrics, and baselines consistent. - Keep the body long enough for the full paper to compile to 10+ pages. - Do not incl
- Inputs you'll receive
- Output contract
- Hard rules
What does the paper-revision-author skill do?
Revise independently drafted paper sections into one coherent LaTeX body before the abstract is written.
How do I install it?
Run `npx skills add opensquilla/opensquilla --skill paper-revision-author --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From opensquilla/opensquilla, a repository with 6,515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.