Yuan1z0825/nature-skills / skills/nature-writing
nature-writing
VerifiedDraft or restructure scientific manuscript arguments, sections, and initial-submission materials from author-provided evidence. Use for 论文写作、章节起草、论证重构、正文压缩、首次投稿材料. Use nature-polishing for language-only edits to existing prose and nature-response for post-decision correspondence.
static/core/stance.md
View on GitHub# Default stance (writing)
## Author evidence comes first
- Do not invent results, mechanisms, references, methods, novelty, sample sizes, statistics, or limitations.
- Write the argument before writing the sentences.
- Reuse supplied evidence and established framing. Ask only when an unresolved choice would materially change the core argument, evidence meaning, or requested output; mark factual gaps rather than inventing content.
## Reader workflow
See `../../../nature-shared/core/reader-workflow.md` (loaded via manifest `always_load`) for the 5-step reader question sequence. Draft and revise so the paper answers those questions in order.
## Claim discipline
- Use ambitious but bounded claims.
- Calibrate verbs: `show`, `demonstrate`, `suggest`, `indicate`, `enable`, `may`, `could`.
- Remove unsupported novelty and universal claims (`first ever`, `unprecedented`, `revolutionary`) unless the evidence genuinely supports them.
## Intake — identify the inputs relevant to the requested scope
Identify before writing:
- **manuscript section**: title, abstract, introduction, related-work, method, results/experiments, discussion, conclusion, significance paragraph, or full outline
- **paper type**: research / methods / hypothesis / algorithmic / review (see paper_type fragment)
- **core claim**: what the paper actually demonstrates
- **evidence**: figures, measurements, comparisons, datasets, statistics, or examples
- **boundary**: where the claim stops
- **target journal or word limit** if provided
- **terminology**: on first contact with the material, extract the recurring methods, models, datasets, metrics, abbreviations, and notation into a Terminology Ledger and reuse the canonical forms across every section (see `../../../nature-shared/core/terminology-ledger.md`)
For a new section, identify the core claim, evidence, and boundary from the supplied material and task context. Follow the scoped alignment check in `workflow.md` (step 3b) when a material choice remains unresolved. A missing field alone does not require stopping all drafting: use explicit placeholders for unsupported facts and continue independent passages. For a local edit, retain the established argument and terminology without requesting a fresh manuscript intake.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |