Use to build Science's data, code, and materials availability — mandatory deposition in approved repositories, accession numbers, a compliant data-availability statement, and materials/reagent sharing.
Scanned 6/6/2026
Install to Claude Code
npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill sci-data --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Sci Data?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/brycewang-stanford-sci-data)More formats (shields.io, HTML) on the badges page.
---
name: sci-data
description: Use to build Science's data, code, and materials availability — mandatory deposition in approved repositories, accession numbers, a compliant data-availability statement, and materials/reagent sharing.
---
# Data, Code & Materials Availability (sci-data)
## When to trigger
- There is no data-availability statement, or it says "available on request".
- Sequences/structures/datasets are not deposited or have no accession numbers.
- Custom analysis code is not in a public repository.
- Unique reagents/strains/cell lines have no sharing plan.
## Science's standard (the bar)
Science requires that **all data and methods needed to evaluate and reproduce the conclusions be available** at publication. "Available upon request" is **not** sufficient for primary data underlying the results.
## Deposit in approved repositories (with accessions)
| Data type | Deposit in (examples) |
|------------------------------------|--------------------------------------------|
| Nucleotide / genome sequences | GenBank / ENA / DDBJ |
| High-throughput sequencing | GEO / SRA / ArrayExpress |
| Protein structures | PDB; maps → EMDB |
| Proteomics | PRIDE / ProteomeXchange |
| Crystallographic data | CCDC / CSD |
| Generic datasets | Dryad / Zenodo / Figshare / OSF |
| Code | GitHub/GitLab **+ archived** to Zenodo (DOI) |
- Obtain **accession numbers / DOIs before submission**; cite them in the data-availability statement and Methods.
- Code that produces the results must be public; archive a release to get a citable DOI (a bare GitHub link is not durable).
## Data-availability statement (template)
> All data needed to evaluate the conclusions are present in the paper and/or the Supplementary Materials. [Sequencing data are deposited at GEO under accession GSEXXXXXX.] [Structures are deposited at the PDB under XXXX.] [Analysis code is available at Zenodo (DOI: 10.5281/zenodo.XXXXXXX).] [Any additional materials are available from the corresponding author / under an MTA as noted.]
Avoid bare "data available on request" for primary data; restricted human/clinical data must state the access procedure and the controlling body.
## Materials & reagents
- Unique materials (plasmids, cell lines, strains, antibodies) should be available, e.g., via Addgene/repositories or under an MTA; state how.
- Identify key reagents with RRIDs where available.
## Ethics & compliance (as applicable)
- Human-subjects: IRB/ethics approval + informed consent statement.
- Animal work: IACUC/animal-ethics approval and guideline compliance.
- Field/biodiversity: permits and the Nagoya Protocol where relevant.
- Dual-use / biosafety: flag if applicable.
## Output format
```
【Data deposited】 type → repository → accession/DOI (list each) | gaps
【Code public + archived DOI】 yes/no (link + DOI)
【Availability statement】 drafted? compliant (no "on request" for primary data)?
【Materials sharing】 plan for unique reagents (Addgene/MTA)
【Ethics approvals】 IRB / IACUC / permits present where needed?
【Next】 sci-abstract
```
## Anti-patterns
- **Do not** write "data available on request" for the primary data behind figures.
- **Do not** link only to a personal/lab website (not durable) — use an archival repository with a DOI.
- **Do not** forget to make code public and versioned; reviewers may try to run it.
- **Do not** submit without accession numbers in hand for deposited data.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!