From science-skills
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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/science-skills:sci-dataThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- There is no data-availability statement, or it says "available on request".
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.
| 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) |
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.
Use this as a second-pass capability check. First lock the broad discovery claim, decisive evidence, uncertainty/limitations, and why the result belongs in a general-science weekly; then test whether the manuscript addresses general-science reviewers and editors who ask whether the result changes a broad field, is technically decisive, and can be understood outside the subdiscipline.
claim / evidence / blocker / next edit rows so the next pass can patch the manuscript directly.resources/official-source-map.md for volatile rules and name the one unresolved fact that could change the recommendation.【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
npx claudepluginhub brycewang-stanford/awesome-journal-skills --plugin science-skillsBuilds PNAS-compliant Data Availability Statements and deposition plans, enforcing mandatory repository deposition, accession numbers/DOIs, and public archived code for code and data.
Builds Cell's data and code deposition plan and formats the Data and Code Availability statement for STAR Methods, including approved repositories, accession tracking, and the three-bullet availability format with Mendeley Data as default.
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.