pnas-data
Use to build PNAS's Data Availability Statement and deposition plan — mandatory deposition of data in an approved repository at submission, accession numbers/DOIs, public + archived code, and materials sharing. "Available on request" is not sufficient for primary data.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pnas-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 Availability (pnas-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, archived repository. - Unique reagents/strains/cell lines have no sharing plan. ## PNAS's standard (the bar) PNAS requires a **Data Availability Statement** in every research article, and that the **data and materials needed to support the conclusions be deposited and available at the time of submission/publication**. For data types with an established public repository, **deposition is required**, and the **accession numbers/DOIs go in the Data Availability Statement**. **"Available upon request" is not sufficient for the primary data** underlying the figures and conclusions. ## Deposit in approved repositories (with accessions) | Data type | Deposit in (examples) | |------------------------------------|--------------------------------------------| | Nucleotide / genome sequences | GenBank / ENA / DDBJ | | High-throughput sequencing | GEO / SRA / ArrayExpress | | Protein/macromolecular structures | PDB; maps → EMDB | | Pro
- When to trigger
- PNAS's standard (the bar)
- Deposit in approved repositories (with accessions)
- Data Availability Statement (template)
- Where the statement and the data live
- Materials & reagents
- Ethics & compliance (as applicable)
- Output format
- Anti-patterns
What does the pnas-data skill do?
Use to build PNAS's Data Availability Statement and deposition plan — mandatory deposition of data in an approved repository at submission, accession numbers/DOIs, public + archived code, and materials sharing. "Available on request" is not sufficient for primary data.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pnas-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.