researchzy-data-availabilitylisted
Install: claude install-skill Researchzy/Researchzy-academic-skills
# Researchzy Data Availability — Router
<!-- Modified by Researchzy; the changes are listed in THIRD_PARTY_NOTICES.md. -->
## 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](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
This skill 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** — accept author notes in any language. Draft the submission-ready statement in English unless the user explicitly asks otherwise; when the user writes in another language, explain the unresolved fields in that language. Translate intent, not wording: a vague request-only note still needs a restriction reason and an access route.
### 3. Run the workflow
For a wording edit or audit of on