From gcb-skills
Prepares data availability statements and archives data/code with DOIs for Global Change Biology manuscripts. Use during manuscript preparation when GCB open-data requirements apply.
How this skill is triggered — by the user, by Claude, or both
Slash command
/gcb-skills:gcb-reporting-and-data-policyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
GCB treats open data and code as a **condition of publication**, not a courtesy. Primary and secondary
GCB treats open data and code as a condition of publication, not a courtesy. Primary and secondary data supporting the results must be archived in a publicly accessible repository with a persistent identifier (DOI), code/software likewise (e.g., Zenodo), and the manuscript must carry a data availability statement. Crucially, "available on request" is not accepted. Build the deposit as you go. Confirm current wording on the policy page before submission.
Different global-change data types land best in different DOI-minting archives. Treat this as a routing guide, then confirm the current accepted list against the journal's author guidelines.
| Data type | Typical archive | Note |
|---|---|---|
| Ecological tabular / experimental | Dryad | Curated, ecology-oriented |
| Code + figure pipeline | Zenodo via a GitHub release | Versioned, DOI per release |
| Oceanographic / Earth-system | PANGAEA | Geo/environmental specialist |
| Sequences | INSDC (GenBank/ENA) | Domain-mandated, then cite accession |
| Sensitive species locations | Restricted deposit + access pathway | Share de-sensitized layer + full code |
A remote-sensing carbon-flux paper archives three things, not one: the gap-filled flux table to a DOI-minting repository; the processing and modelling code to Zenodo via a tagged GitHub release; and the raw tower coordinates with a stated restriction because one site is on a protected reserve. The data availability statement names each DOI and the access route for the restricted coordinates. A weak version deposits only the figures' CSV and writes "code available on request" — which GCB does not accept. The DOIs here are illustrative placeholders; mint real ones before submission.
【Data archived】DOI-minting repo + metadata? [Y/N]
【Code archived】Zenodo/release with DOI? [Y/N]
【Availability statement】names repo + access (not "on request")? [Y/N]
【Sensitive data】restriction explained + access path + shareable subset?
【Reproducible reporting】n, units, versions complete? [Y/N]
【Next】gcb-writing-style
../../resources/external_tools.md — repositories (Dryad/Zenodo/PANGAEA) and reproducibility tooling../../resources/official-source-map.md — GCB data- and code-archiving policynpx claudepluginhub brycewang-stanford/awesome-journal-skills --plugin gcb-skillsPrepares data-availability statements and data/code archives for Conservation Biology manuscripts, including handling sensitive species data restrictions.
Guides users in complying with Science's data/code/materials availability policy: deposit data in approved repositories, obtain accession numbers, write a compliant data-availability statement, and plan material sharing.
Builds PNAS-compliant Data Availability Statements and deposition plans, enforcing mandatory repository deposition, accession numbers/DOIs, and public archived code for code and data.