sci-data
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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sci-data --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.
# 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
- When to trigger
- Science's standard (the bar)
- Deposit in approved repositories (with accessions)
- Data-availability statement (template)
- Materials & reagents
- Ethics & compliance (as applicable)
- Data pass for Science
- Output format
- Anti-patterns
What does the sci-data skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sci-data --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.