nature-datalisted

# Nature Data Availability — Router This skill is split into two layers: - A **static layer** under `static/` that holds versioned, reusable content fragments (the default stance and source hierarchy, the Chinese-user operating mode, and the workflow with output format). - A **dynamic layer** (this file plus `manifest.yaml`) that loads the core every time and reaches for the deeper policy/repository/FAIR references only when a step needs them. Do not try to apply the data-availability logic from memory or from this router. Always load fragments from disk as described below. ## Routing protocol Follow these four steps every time the skill is invoked. ### 1. Load the manifest and the core layer Read [manifest.yaml](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/chinese-mode.md` — how to operate when the user writes in Chinese (accept Chinese, draft English, convert terms precisely). - `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 int