gcb-reporting-and-data-policy
Use when preparing the data availability statement and the data/code archive for a Global Change Biology (GCB) manuscript. GCB requires data and code to be archived in a public repository with a persistent DOI as a condition of publication, and "available on request" is not accepted. Prepares the deposit; it does not waive requirements.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill gcb-reporting-and-data-policy --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Reporting & Data Policy (gcb-reporting-and-data-policy) 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. ## When to trigger - Writing the **data availability statement** - Choosing repositories and minting DOIs for data and code - Handling data that cannot be fully shared (sensitive species locations, third-party/licensed data) - Final reporting checks before submission ## What GCB requires (verify current wording) 1. **Archive data with a DOI.** Deposit primary and secondary data in a public, DOI-minting repository (e.g., **Dryad**, **Zenodo**, **PANGAEA**) with metadata sufficient for a third party to interpret the data correctly — before acceptance/publication. 2. **Archive code with a DOI.** Code, software, and documentation supporting the results go to an ap
- When to trigger
- What GCB requires (verify current wording)
- When data cannot be fully shared
- Build-as-you-go checklist
- Repository fit by data type
- Worked micro-example (illustrative)
- Compliance pushback patterns and the fix
- Anti-patterns
- Output format
- Supplementary resources
What does the gcb-reporting-and-data-policy skill do?
Use when preparing the data availability statement and the data/code archive for a Global Change Biology (GCB) manuscript. GCB requires data and code to be archived in a public repository with a persistent DOI as a condition of publication, and "available on request" is not accepted. Prepares the deposit; it does not waive requirements.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill gcb-reporting-and-data-policy --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.