ClaudeCodeMod

All shelves / Skills

nature-statistics

yuan1z0825/nature-skills · 10.6k installs · 47.5K stars

Skill

Marked External Downloads · Indirect Prompt Injection

Install

In your shell
npx -y skills add yuan1z0825/nature-skills --skill nature-statistics --agent claude-code

Run in a terminal. Claude loads the skill when a task calls for it. Check the repo's README before you run it.

Open the repo

Files

SKILL.md

Nature Statistics Reporting Skill

Use this skill to make manuscript statistics transparent, reproducible, and appropriately bounded. It is a reporting and review skill, not a substitute for a statistician reanalysing raw data unless the user supplies the data and explicitly asks for computation.

Default stance

  • Prioritize design transparency over decorative statistical language.
  • Separate three questions: what was measured, what unit was analysed, and what inference was claimed.
  • Treat the independent experimental unit as the default n; do not silently treat cells, fields of view, repeated readings, spectra, model runs, or technical replicates as independent biological or experimental samples.
  • Prefer effect sizes, uncertainty intervals, sample sizes, and exact test definitions over significance-only phrasing.
  • State missing information as AUTHOR_INPUT_NEEDED instead of inventing sample sizes, tests, software, corrections, exclusion rules, randomization, or blinding.
  • If a journal-specific instruction, study-type guideline, or field standard conflicts with this skill, follow the more specific source and mark the source used.

Accepted inputs

The skill may receive:

  • a Statistical analysis / Methods subsection
  • Results paragraphs containing test statistics or p values
  • figure panels, legends, captions, or source-data notes
  • reviewer comments about statistics
  • author notes in Chinese or English
  • tables of reported comparisons
  • raw or summary data, only when the user wants a concrete reanalysis or figure-statistics check

If the input is partial, run a bounded audit and state which parts cannot be assessed.

Workflow

  1. Classify the task. Decide whether the user wants audit, rewrite, draft, reviewer-response support, figure-statistics alignment, or data-backed reanalysis.
  2. Extract the design. Identify groups, treatments, time points, endpoints, blocking factors, repeated measures, randomization, blinding, exclusions, and missing-data handling.
  3. Define n and replication. Separate independent experimental units, biological replicates, technical replicates, repeated measures, cells/fields/subsamples, simulations, and pooled observations.
  4. Map claims to analyses. For each result claim, record the comparison/model, test family, assumptions, correction strategy, effect estimate, uncertainty, and exact p-value policy.
  5. Check common failure modes. Use references/common-failure-modes.md when the text involves nested data, many comparisons, cell-level measurements, interaction claims, correlations, regression, outliers, small samples, or significance-only reasoning.
  6. Check reporting completeness. Use references/statistical-reporting.md to verify that Methods and Results give enough information for readers and reviewers to understand the analysis. If the target is the flagship journal Nature, also use references/nature-article-requirements.md for its exact tail, n, repeat, P-value, test-statistic and degrees-of-freedom requirements. If the target is Nature Machine Intelligence, also use ../nature-shared/journal-formats/nature-machine-intelligence.md for its legend-statistics, source-data, reporting-summary and stage-specific checks.
  7. Align figure statistics. Use references/figure-statistics.md when figure legends, panel labels, stars, error bars, box plots, violin plots, source data, or supplementary figure notes are involved.
  8. Draft or revise. Produce conservative, ready-to-paste text. Keep claims within the supplied design and evidence. Do not upgrade statistical association into mechanism or causality.
  9. Run final QA. Use references/reviewer-checklist.md before final delivery for severity labels, unresolved author questions, and reviewer-facing risk.

Output format

Unless the user asks for another format, return:

Statistics review scope
- Input reviewed:
- Boundary / missing materials:
- Study design readout:
- Independent unit and replication readout:

Major statistical issues
- [P0/P1/P2] Issue:
  Evidence from supplied text:
  Why it matters:
  Fix:

Ready-to-paste revision
[Rewritten Statistical analysis / Results / figure legend text]

AUTHOR_INPUT_NEEDED
- [short factual questions only]

Reviewer-risk note
- What a statistical reviewer may still challenge:

For a clean drafting request with enough information, skip the long issue list and return:

Draft Statistical analysis
[ready-to-paste text]

Reporting notes
- n definition:
- tests/models:
- multiple comparisons:
- software/version:
- unresolved fields:

Red lines

  • Do not invent p values, sample sizes, degrees of freedom, confidence intervals, software versions, correction methods, preregistration, exclusion rules, or power calculations.
  • Do not recommend a statistical test as final when the unit of analysis or design is unclear.
  • Do not accept n = number of cells/images/measurements as independent replication without checking the experimental hierarchy.
  • Do not use “significant” as a synonym for important, large, causal, or biologically meaningful.
  • Do not hide non-significant or weak results by rewriting them into stronger claims.
  • Do not give medical, regulatory, or clinical-trial statistical advice beyond reporting checks unless the user provides the relevant protocol and asks for bounded manuscript wording.

Related files

File Open when
references/source-basis.md You need the source hierarchy or want to justify why the skill emphasizes transparency, reproducibility, and design reporting
references/nature-article-requirements.md The target is the flagship journal Nature or the user requests its exact statistical submission checklist
../nature-shared/journal-formats/nature-machine-intelligence.md The target is Nature Machine Intelligence or NMI-specific legend, source-data, reporting or stage requirements affect the audit
references/statistical-reporting.md You are drafting or auditing Statistical analysis, Methods, Results, or Supplementary Methods text
references/common-failure-modes.md You see nested measurements, many comparisons, interaction claims, correlation/regression, outliers, tiny samples, or overstrong p-value language
references/figure-statistics.md You are checking figure legends, panel statistics, error bars, stars, box/violin plots, source-data notes, or graphical reporting
references/reviewer-checklist.md You are finalizing an audit or preparing a reviewer-facing risk summary
../nature-shared/core/consistency-sweep.md The same statistic appears in more than one place, or interval terminology is in question: one metric at two precisions across table and text, SD/Std abbreviation drift, confidence interval used where prediction interval is meant, or overlapping error bars described as outperformance

Source hierarchy

Use sources in this order:

  1. User-supplied manuscript, data, protocol, statistical analysis plan, reviewer comments, and journal instructions.
  2. Nature Portfolio reporting standards and reporting-summary requirements.
  3. Nature Methods / Nature Portfolio statistics guidance summarized in references/source-basis.md.
  4. Study-type reporting guidelines where relevant, for example CONSORT, STROBE, PRISMA, ARRIVE, or field-specific community standards.
  5. Conservative statistical reporting practice.

If the supplied material is insufficient for a defensible statistical recommendation, ask for the missing design facts or provide a bounded wording option rather than guessing.

Facts

Kind
Skill
Repo
yuan1z0825/nature-skills
Group
Uncategorized
Installs
10.6k
Stars
47.5K

More on this shelf

  1. 1find-skillsvercel-labs/skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.3.8M
  2. 2grill-memattpocock/skillsA relentless interview to sharpen a plan or design.1.3M
  3. 3grill-with-docsmattpocock/skillsA relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.1.1M
  4. 4agent-browservercel-labs/agent-browserBrowser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.1.1M
  5. 5improve-codebase-architecturemattpocock/skillsScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.1.1M
  6. 6tddmattpocock/skillsTest-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.1.1M