Skip to content

Yuan1z0825/nature-skills / skills/nature-writing

nature-writing

Verified

Draft 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.

FileKindSize
README.mdmarkdown4.3 KB
README_EN.mdmarkdown4.9 KB
SKILL.mdskill md8.1 KB
agents/openai.yamlconfig253 B
manifest.yamlconfig8.5 KB
references/abstract.mdmarkdown4.0 KB
references/article-architecture.mdmarkdown3.4 KB
references/chinese-author-workflow.mdmarkdown1.8 KB
references/conclusion.mdmarkdown1.2 KB
references/examples/abstract-examples.mdmarkdown875 B
references/examples/abstract/template-a.mdmarkdown950 B
references/examples/abstract/template-b.mdmarkdown3.2 KB
references/examples/abstract/template-c.mdmarkdown1.7 KB
references/examples/index.mdmarkdown2.3 KB
references/examples/introduction-examples.mdmarkdown1.5 KB
references/examples/introduction/novel-task-challenge-decomposition.mdmarkdown1.5 KB
references/examples/introduction/pipeline-not-recommended-abstract-only.mdmarkdown2.9 KB
references/examples/introduction/pipeline-version-1-one-contribution-multi-advantages.mdmarkdown2.0 KB
references/examples/introduction/pipeline-version-2-two-contributions.mdmarkdown2.0 KB
references/examples/introduction/pipeline-version-3-new-module-on-existing-pipeline.mdmarkdown1.5 KB
references/examples/introduction/pipeline-version-4-observation-driven.mdmarkdown1.4 KB
references/examples/introduction/technical-challenge-version-1-existing-task.mdmarkdown2.6 KB
references/examples/introduction/technical-challenge-version-2-existing-task-insight-backed-by-traditional.mdmarkdown3.8 KB
references/examples/introduction/technical-challenge-version-3-novel-task.mdmarkdown1.6 KB
references/examples/introduction/version-1-task-then-application.mdmarkdown727 B
references/examples/introduction/version-2-application-first.mdmarkdown405 B
references/examples/introduction/version-3-general-to-specific-setting.mdmarkdown847 B
references/examples/introduction/version-4-open-with-challenge.mdmarkdown1.7 KB
references/examples/method-examples.mdmarkdown1.0 KB
references/examples/method/example-of-the-three-elements.mdmarkdown7.3 KB
references/examples/method/method-writing-common-issues-note.mdmarkdown355 B
references/examples/method/module-design-instant-ngp.mdmarkdown4.5 KB
references/examples/method/module-motivation-patterns.mdmarkdown410 B
references/examples/method/module-triad-neural-body.mdmarkdown763 B
references/examples/method/neural-body-annotated-figure-text.mdmarkdown2.8 KB
references/examples/method/overview-template.mdmarkdown2.0 KB
references/examples/method/pre-writing-questions.mdmarkdown479 B
references/examples/method/section-skeleton.mdmarkdown110 B
references/experiments.mdmarkdown4.7 KB
references/introduction.mdmarkdown15.3 KB
references/method.mdmarkdown6.9 KB
references/nat-comms-2025-corpus.mdmarkdown7.3 KB
references/nature-summary-paragraph.mdmarkdown10.3 KB
references/paper-review.mdmarkdown5.3 KB
references/paragraph-flow.mdmarkdown1.7 KB
references/related-work.mdmarkdown1.3 KB
references/submission-package.mdmarkdown7.9 KB
static/core/output-format.mdmarkdown1.8 KB
static/core/stance.mdmarkdown2.2 KB
static/core/workflow.mdmarkdown5.1 KB
static/fragments/journal/generic.mdmarkdown1.1 KB
static/fragments/journal/nat-comms.mdmarkdown3.1 KB
static/fragments/journal/nat-mach-intell.mdmarkdown5.9 KB
static/fragments/journal/nature-family.mdmarkdown1.2 KB
static/fragments/journal/nature.mdmarkdown2.7 KB
static/fragments/language/en.mdmarkdown1.0 KB
static/fragments/language/zh-to-en.mdmarkdown1.6 KB
static/fragments/paper_type/algorithmic.mdmarkdown1.2 KB
static/fragments/paper_type/hypothesis.mdmarkdown1.0 KB
static/fragments/paper_type/methods.mdmarkdown1.2 KB
static/fragments/paper_type/research.mdmarkdown1.3 KB
static/fragments/paper_type/review.mdmarkdown1.2 KB
static/fragments/section/abstract.mdmarkdown1.7 KB
static/fragments/section/conclusion.mdmarkdown929 B
static/fragments/section/discussion.mdmarkdown1.8 KB
static/fragments/section/experiments.mdmarkdown3.0 KB
static/fragments/section/intro.mdmarkdown2.6 KB
static/fragments/section/method.mdmarkdown1.5 KB
static/fragments/section/related-work.mdmarkdown1.2 KB
static/fragments/section/title.mdmarkdown999 B
static/fragments/task/manuscript.mdmarkdown288 B
static/fragments/task/submission-package.mdmarkdown2.5 KB
templates/submission/declarations-and-reviewers.texother2.6 KB
templates/submission/highlights-and-summary.texother1.1 KB
templates/submission/initial-cover-letter.texother1.6 KB
templates/submission/title-page.texother1.9 KB
tests/scoped-drafting.mdmarkdown1.9 KB

static/fragments/section/experiments.md

View on GitHub
# Section: Experiments / Results (writing)

## Default evidence ladder

`establish the phenomenon -> stress-test it -> rule out alternatives -> broaden it -> interpret it -> bound it`

Each subsection has a claim-first opening, then data support.

Depending on the paper, instantiate this as a discovery loop, a core-capability
plus validation envelope, or a capability ladder. Load
`../../../../nature-shared/core/nature-results-discussion.md` for the three
archetypes and the same-level-repetition test.

## Drafting rules

- Load `../../../../nature-shared/core/main-text-discipline.md` before deciding
  which analyses enter the main text. Classify results by their function in the
  paper and build the shortest sufficient evidence chain.
- Stay mainly in past tense.
- Report what was observed, under what conditions, with what quantitative support.
- Use statistics correctly and sparingly. Every test needs a stated hypothesis.
- Keep core discovery and necessary support in the main text. Route robustness,
  non-central heterogeneity, provenance detail, alternative inference, and edge
  cases to SI unless they change the central interpretation.
- **Each major claim needs adequate evidence across the manuscript and SI.** Do
  not force every comparison, ablation, or stress test into the main text; if
  adequate evidence is absent from the full record, mark it for follow-up rather
  than drafting around it.
- Normally report the descriptive quantity and primary inferential statistic in
  the main text. Put secondary inference and diagnostics in SI unless required
  or conclusion-changing.

## Results syntax (vs Discussion)

Results sentences usually report:

- `was detected` / `increased` / `showed` / `enabled` / `achieved`

Close each coherent evidence unit with the bounded inference it supports.
Calibrated interpretation (`suggests`, `indicates`, `likely because`) may remain
in Results when it directly answers the current experiment and the supporting
evidence is visible there. Move literature synthesis, broad implications, and
extended mechanistic reconciliation to Discussion.

## Common failure modes when drafting

- Mixing observation with an interpretation that is not supported by the
  current experiment, or allowing local interpretation to expand into a broad
  Discussion.
- Citing supplementary data when the result should be in the main text.
- Appending robustness or reviewer-defense prose until the central evidence chain
  disappears.
- Repeating the same effects, intervals, and P values in Results and captions.
- Vague comparisons (`higher than control`) without effect size, sample size, or test.
- Per-paragraph claims without per-paragraph evidence.
- Reusing an earlier baseline or control as the centre of a later subsection
  and restating the same claim, instead of making the new perturbation,
  falsification, stronger comparator, or boundary the decisive evidence.

## Deeper reference

For ML/conference-style experiment sections — baselines, ablations, metrics, tables, figures — open `references/experiments.md`.
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
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: 194kUpdated Claude CodeCodexVerifiedInstall