# Nature Manuscript Workflow

> Plan, draft, revise, and audit broad-journal or high-impact manuscripts, including claim framing, figure logic, data availability, submission readiness, and reviewer response. Use for story-driven journal strategy, broad-audience manuscript framing, figure-to-claim alignment, and Nature-family targets when explicit.

- Skill: `yuukias/nature-manuscript-workflow` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add yuukias/nature-manuscript-workflow`
- Raw SKILL.md: https://api.skillmd.com/api/skills/yuukias/nature-manuscript-workflow/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- Author: YuukiAS (https://skillmd.com/u/yuukias)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/yuukias/nature-manuscript-workflow

---

# Broad-Journal Manuscript Workflow

Use this for broad-audience or high-impact manuscript strategy, including Nature-family targets when explicit. It complements general `scientific-writing`; it does not replace current venue-specific author instructions.

## Workflow

1. Identify the target venue family if known, article type, field, current manuscript state, audience breadth, and submission deadline.
2. Build the claim map:
   - headline claim;
   - significance beyond technical performance;
   - main figures and their panel-level claims;
   - methods/results needed to support the scope of the claim.
3. Audit broad-journal and submission risks:
   - overclaiming relative to evidence;
   - figure panels that are descriptive but not argumentative;
   - missing source data or code availability;
   - vague data availability statements;
   - terminology drift between title, abstract, results, figures, and discussion.
4. Route palette choice, figure color accessibility, and publication-ready plot
   snippets to `scientific-visualization`; journal-inspired palettes must remain
   non-official visual inspiration rather than Nature branding.
5. Draft or revise in this order: title/abstract framing, figure logic, results narrative, discussion boundaries, methods/data availability, cover or rebuttal text.
6. Before delivery, list unresolved policy or evidence checks that require the journal's current instructions.

## Data Availability

Treat data availability as a submission artifact, not boilerplate. Include repository, accession, restricted-access reason, code availability, source-data coverage, and timing. If a dataset cannot be shared, name the restriction and access mechanism.

## Reviewer Response

For reviewer comments, classify each point as evidence request, clarity request, scope challenge, method challenge, or policy/format issue. Draft response text only after mapping the manuscript edit that answers the comment.

## Boundaries

- Do not promise journal compliance without checking current author instructions.
- Do not imitate a journal voice by adding hype.
- Preserve scientific uncertainty and limitations.