Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Nature Methods

ASecurity

Use when targeting Nature Methods or deciding whether a methods/tools manuscript fits this venue. Encodes the journal's fit, framing, method-and-evidence bar, house style, official-submission re-check, and desk-reject heuristics.

1,052 stars
0 votes
0 copies
0 views
Added 6/5/2026
ai-agentsgogitperformancedocumentation

Works with

cli

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill nature-methods --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Nature Methods?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Nature Methods
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-nature-methods/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-nature-methods)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: nature-methods
description: Use when targeting Nature Methods or deciding whether a methods/tools manuscript fits this venue. Encodes the journal's fit, framing, method-and-evidence bar, house style, official-submission re-check, and desk-reject heuristics.
---

# Nature Methods (nature-methods)

## Journal positioning

Nature Methods is the Nature Portfolio's dedicated venue for new methods, approaches, and technologies in the life sciences and related disciplines, with the distinguishing requirement that a published method must be generalizable — applicable by other researchers to their own biological questions — and thoroughly benchmarked against alternatives. The journal's editorial culture is highly skeptical of incremental improvements; what wins is a genuinely new capability or a step-change in performance that enables previously impossible or impractical experiments. The readership is broadly all life scientists who need to understand and adopt new tools, making technical clarity and honest benchmarking as important as scientific novelty.

This skill is a **fit / venue-selection / re-framing** tool. It does not replace the journal's current official submission guidelines. Before submitting, re-check the live author instructions on the Nature Portfolio site or submission system.

## When to trigger

- The author names Nature Methods as the target venue.
- A new method, computational tool, or technology platform is being submitted and the author is choosing between Nature Methods, Nature Biotechnology, Genome Biology, or Bioinformatics.
- A biological study whose primary advance is a new analytical or experimental tool needs to assess whether the method's generalizability and benchmarking meet the bar.
- The author needs Nature Methods' specific desk-reject triggers and re-routing options.

## Scope & topic fit

- New experimental techniques in imaging, sequencing, proteomics, metabolomics, structural biology, or single-cell analysis — when the method enables previously impossible or substantially more efficient experiments.
- Computational and statistical methods for biology: new algorithms for sequence analysis, spatial transcriptomics, protein structure prediction, variant calling, or multi-omics integration — when rigorously benchmarked.
- Synthetic-biology and genome-engineering tools: new CRISPR variants, base editors, prime editors, or delivery systems — when generalizability and performance are demonstrated at method level.
- Microscopy and biophysical methods: super-resolution, live-cell imaging, cryo-EM workflows, single-molecule techniques — when the methodological advance is the contribution.
- Organoid, organ-on-chip, or model-system methods when the platform itself (not only its biological application) is the advance.
- Data analysis pipelines and benchmarking studies for widely used method classes — when the result changes best practices across the community.

## Method & evidence bar

- Generalizability is the primary test: the method must be demonstrated to work on multiple biological systems or datasets, not just the authors' system of development.
- Benchmarking against the current best alternatives is mandatory, using objective performance metrics; claims of superiority must be supported by head-to-head comparison on the same datasets or experimental conditions.
- Biological application is required: a method must demonstrate what new biology it enables or what question it answers; a pure engineering advance without biological demonstration does not qualify.
- Code or protocols for methods that generate data must be made fully available; software tools must be well-documented, installable, and actively maintainable.
- Usability matters: the editorial board values tools that other labs can actually adopt; inaccessible instruments or reagents requiring specialized infrastructure weaken the case.
- Reproducibility reporting: Nature reporting summary required; reagents and protocols should be described in sufficient detail for independent replication.

## Structure & house style

- Nature Portfolio format: unstructured abstract; main text followed by Methods section; Extended Data figures (up to current limit) for additional benchmarking; Supplementary Information for large datasets, code, and extended protocols.
- Nature reporting summary required; methods-specific checklists (e.g., ARRIVE for animal-based validation, human-subjects for clinical data) where applicable.
- The introduction must establish the biological problem the method solves and why existing approaches are insufficient; avoid leading with engineering specifications.
- Results should be organized as: (1) method concept and design, (2) performance validation, (3) benchmarking against alternatives, (4) biological demonstration.
- Figures should include performance metrics with error bars, representative data showing the biological application, and honest failure-mode analysis.
- Code deposited in a public repository (GitHub, Zenodo); a stable versioned release should accompany submission; protocols deposited to protocols.io where appropriate.

## Official-submission checklist

- Before giving submission-ready advice, read `../../resources/source-basis.md` and `../../resources/official-source-map.md`; start from the official source anchors for this journal family, then cite the current journal-specific page you checked.
- Search "Nature Methods author information" on the Nature Portfolio site and follow the current version.
- Re-check article types (Article, Brief Communication, Analysis), length and figure limits, and Extended Data policy.
- Confirm Nature reporting summary requirements and any field-specific checklists.
- Re-check code/software deposition and documentation standards (README, installation, example data).
- Verify data availability: raw benchmarking data, test datasets, and protocol deposition requirements.
- Re-check competing-interests (particularly tool-commercialization disclosures), funding, and AI-use disclosure requirements.
- Confirm preprint policy and open-access/APC options.
- If the live official instructions conflict with this skill, the official instructions win.

## Pre-submission self-check

- [ ] One sentence stating what new experimental or analytical capability this method provides that was previously impossible or substantially impractical.
- [ ] Benchmarking against the current best alternatives is complete, objective, and uses the same evaluation conditions.
- [ ] The method is demonstrated in at least two biological contexts or datasets to establish generalizability.
- [ ] Code or protocols are fully documented, deposited, and independently installable/reproducible.
- [ ] Nature reporting summary is prepared; biological application data show what new biology the method enables.
- [ ] Usability for a typical lab — reagent access, computational requirements — is honestly assessed.

## Common desk-reject triggers

- A method demonstrated only on the authors' own biological system with no generalizability evidence.
- Incremental improvement over an existing method — faster by 10%, slightly better sensitivity — without a step-change in capability or a qualitatively new application.
- A computational tool paper without rigorous benchmarking against current alternatives on publicly available datasets.
- A method paper where the biological discovery, not the method, is the real advance — better submitted to the appropriate biology journal.
- Code is not released, is available only on reasonable request, or is undocumented and non-reproducible.

## Re-routing decision

- New method primarily enabling biotech/therapeutic applications → `nature-biotechnology` (broader applied-science scope, more tolerant of translational framing).
- Genomics/bioinformatics tool with strong biological application → `genome-biology` (OA, bioinformatics-friendly, benchmark papers welcome).
- Excellent method below Nature Methods significance or generalizability bar → `nature-communications`, Bioinformatics, or a specialty methods journal.
- New method for a specific biological field where the biology is the primary advance → the relevant biology journal (e.g., `neuron` for a neuroscience imaging technique).

## Output format

```text
[Fit] High / Medium / Low (one-line reason)
[Target] Nature Methods
[Topic tags] <2–3 closest topics>
[Method/evidence] <is the method generalizable, benchmarked, and enabling of new biology?>
[Top risk] <the single most likely reason for rejection>
[Official items to re-check] <article type / Extended Data limit / reporting summary / code deposition / protocols / disclosure>
[Re-route suggestion] <if not a fit, a better-matched venue>
```

Attribution

brycewang-stanfordbrycewang-stanford
View sourceMore from brycewang-stanford →
SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1066601 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

693161 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

651 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →