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/abstract.md
View on GitHub# Section: Abstract (writing)
The abstract is the manuscript's shortest evidence chain, not a compressed
Introduction. Draft it last, when Results and Discussion are stable.
## Default Nature pattern
`precise problem / gap -> answer-enabling design -> main discovery -> decisive support / boundary -> implication`
## Paragraph movement (recommended)
1. State the problem and exact unresolved question with minimal background.
2. Explain only the design logic needed to see how the question is answered.
3. State one main discovery.
4. Add one or two decisive supporting findings or boundaries.
5. End with the bounded conceptual, technical, or field-level implication.
## Pattern variants for technical / method-heavy papers
For ML, CV, materials, or method-heavy manuscripts, choose one variant from `references/abstract.md`:
- `challenge -> contribution`
- `challenge -> insight -> contribution`
- `multiple contributions`
Open `references/abstract.md` for templates and examples.
## Diagnostics before submitting the draft
- Beginning with `Here, we` may signal missing context.
- Ending with a broad promise may need scope control.
- A result may feel ungrounded when neither a decisive comparison nor the logic
of the supporting test is visible. A number is optional unless it defines the
central claim.
## Drafting discipline
- Keep it compact. Cut sentences that re-summarize background the title already implies.
- Include a quantitative result only when it defines, supports, or materially
bounds the central claim. Do not invent numbers or fill the abstract with an
experiment inventory.
- Keep one main claim and no more than one or two supporting claims.
- End with what the work enables, not generic importance.
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 |