Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Browser & automation

paper-workflow

Entry point for any manuscript request that does not name a specific skill. Load this FIRST whenever the ask is general, then run the chain it prescribes. Covers optimize my paper, improve the manuscript, polish this draft, make this better, clean it up, help with my paper, review my writing, get this ready to submit, work on the paper, and the Chinese equivalents 优化论文, 改论文, 润色论文, 帮我看看论文, 论文写作, 学术写作, 把论文弄好, 论文修改, 投稿前检查. Also decides which skill applies and how to sequence manuscript work from project setup through submission and rebuttal, including the separate path for a Review, survey, or Perspective. A general manuscript request is never served well by one skill alone; this file decides which chain to run.

Boom5426 · AI review on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add Boom5426/Nature-Paper-Skills --skill paper-workflow

About this skill


name: paper-workflow description: >- Entry point for any manuscript request that does not name a specific skill. Load this FIRST whenever the ask is general, then run the chain it prescribes. Covers optimize my paper, improve the manuscript, polish this draft, make this better, clean it up, help with my paper, review my writing, get this ready to submit, work on the paper, and the Chinese equivalents 优化论文, 改论文, 润色论文, 帮我看看论文, 论文写作, 学术写作, 把论文弄好, 论文修改, 投稿前检查. Also decides which skill applies and how to sequence manuscript work from project setup through submission and rebuttal, including the separate path for a Review, survey, or Perspective. A general manuscript request is never served well by one skill alone; this file decides which chain to run.

Paper Workflow: Dispatcher

This is the entry point, not a menu. A request such as 优化一下论文 or improve my manuscript names a goal, not a layer. Manuscript work happens at distinct layers, and editing the wrong layer first wastes the edit: a paragraph whose scientific role is wrong should never be polished, and a sentence whose claim is unstable should never be re-punctuated.

Do not answer a general manuscript request by loading a single specialist skill. Classify the request, then run the whole chain for that class.

Default assumption: unless a conference venue is named, the manuscript follows the journal-oriented Nature-style path.

Step 1: Classify by what was actually handed over

InputClassChain
One sentence or one paragraphpassagewrite-scientific-manuscript then scientific-prose-style
One section to draft or rewrite in prosesectionscientific-writing, write-scientific-manuscript, then scientific-prose-style
A Results section that is scientifically settled but reads figure-by-figureresults-flowresults-section-revision then scientific-prose-style
A whole draft, or no unit namedmanuscriptmanuscript-optimizer, scientific-writing, write-scientific-manuscript, anti-defensive-writing, then scientific-prose-style
Reads hedged, over-caveated, apologetic, or timid; too many disclaimers; a paragraph opens with a limitationpostureanti-defensive-writing, then scientific-prose-style. If the claim hierarchy is not yet settled, run manuscript-optimizer first: an unnecessary disclaimer and a real scope condition look identical while the claim is still moving
A Review, survey, or Perspectivereview-articlereview-article-architecture first, then the Review path below
A long draft carried across many sessionslong-draftdraft-marker-discipline then review-article-architecture drift audit
Near submission or resubmissionpreflightsubmission-audit, citation-verifier, claim-source-verification, stats-reporting-audit, data-availability
Reviewer comments existresponsepaper-reviewer to inventory every ask, rebuttal-response to draft and calibrate, then paper-reviewer again to grade the draft. paper-reviewer is not in the default recommended set; install it with --set all
A manuscript to referee, or a request to predict what reviewers will attackrefereepaper-reviewer, installed with --set all
Figures are the bottleneckfigurefigure-planner, then nature-figure to render, then figure-style to check. The last two are the figure stack, installed with --figure
No draft yet, project new or messybootstrappaper-bootstrap then nature-portfolio-playbook

When two classes with different chains both fit, ask one question. That is the one case worth a clarifying question; guessing wastes more time than asking.

Step 2: Announce the chain, then run it in order

State the chain in one line before starting, so the author can redirect early:

Running the manuscript chain: structure (manuscript-optimizer), prose (scientific-writing), passage logic (write-scientific-manuscript), then sentence pass (scientific-prose-style).

Load each skill in sequence and apply it. Do not skip a link because the previous one already improved the text. Each layer catches a different defect class, and a later layer cannot see the defect an earlier one owns.

Step 3: Stop rules

Stop the chain and report why when:

  • an upstream layer finds a problem that invalidates downstream work, such as a claim the evidence does not support. Fix or surface it before polishing;
  • the request was narrow. 帮我把这句话改短 is a passage job, not a licence to restructure the paper;
  • a later layer would undo a decision the author explicitly approved.

Never run preflight on a draft still in manuscript class. Auditing unstable text produces findings that evaporate on the next revision.

Never run scientific-prose-style on a drifted Review before the drift audit. Polishing a drifted draft makes the drift harder to see, not easier.

The layers

Every skill sits at one layer. This is why the chains are ordered.

  1. Structure: is there a defensible claim hierarchy and evidence chain? manuscript-optimizer for research articles, review-article-architecture for Reviews.
  2. Prose: is the section drafted in full paragraphs that carry the argument? scientific-writing, with results-section-revision for late-stage Results architecture.
  3. Passage logic: is this paragraph followable? Buried topic sentences, missing bridges, ambiguous referents, noun chains, incomplete comparisons, coined terminology. write-scientific-manuscript.
  4. Rhetorical posture: does the text advance its claim, or negotiate with an imagined critic? Unnecessary disclaimers, caveats in high-impact positions, paragraphs that open with a limitation, repeated statements of what the text does not claim. anti-defensive-writing. It runs after the claim hierarchy is settled, because before that an unnecessary disclaimer and
Read the complete source ↗