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/fragments/section/discussion.md
View on GitHub# Section: Discussion (writing)
Load `../../../../nature-shared/core/discussion-argument-language.md` for the
complete Discussion function chain, modality ladder, limitation logic, and
sentence-function audit.
## Default structure
`central advance -> what the evidence means -> relation to prior work -> constraints / limitations -> future use or open questions`
## Drafting rules
- Discussion **synthesizes across established Results claims**; it does not
repeat the evidence figure by figure.
- Address rival explanations before generalizing. Reviewers look for this.
- Hedging strength must match evidence strength. Do not promote a "consistent with" finding to "demonstrates" wording.
- Limitations come from inside the paper, not from generic disclaimers. Name the specific condition or dataset where the result stops holding.
## Sentence syntax
Discussion sentences interpret:
- `may reflect`
- `suggests that`
- `could indicate`
- `is likely due to`
- `may facilitate`
## Common failure modes when drafting
- Re-summarizing Results instead of interpreting them.
- Skipping rival explanations.
- Omitting boundaries — when does the interpretation stop holding?
- Future-work statements that read as marketing, not as honest open questions.
- Treating the reverse funnel as a fixed paragraph template or expanding beyond
what the evidence supports.
- Using `must`, `cannot`, `demonstrates`, or causal verbs without naming the
design feature that licenses that strength.
- Listing limitations without saying which claim, scope, or interpretation each
one changes.
## Short rule to memorize
- Results = the evidence chain that establishes and advances claims
- Discussion = what those claims mean together, how they relate to the field,
and when the synthesis may fail
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 |