Nature Data Availability, Router

Routing protocol

For a new task, load the core and matching resources below. Reuse already loaded guidance on follow-ups; load more only when the task needs it.

1. Load the manifest and the core layer

Read manifest.yaml. Then read every file listed under always_load:

• static/core/stance.md, what the data-availability package is, the default stance, and the source hierarchy.
• static/core/workflow.md, the eight-step workflow and the output format.

2. No content axis, confirm journal and language inline

Unlike nature-writing or nature-figure, nature-data has no fragment axis. Its variation is handled at runtime, not by loading different content bodies:

• journal/article type, if journal-specific instructions conflict with this skill, follow the journal.
• access route, each dataset is classified into one route (public repository, controlled access, within paper, reused public, third-party restricted, justified request, or not applicable).
• user language, if the user writes Chinese or requests Chinese guidance, read static/core/chinese-mode.md and add the 中文核对 block unless the user requested statement text only.

3. Run the workflow

For a wording edit or audit of one existing statement, preserve supplied repository identifiers and access conditions and check the affected claims. Report gaps relevant to that statement; do not require a full study-wide dataset inventory or repository redesign. Use the complete workflow below for a new data-sharing plan, full statement, or submission audit.