pnasnexus-data
Use to build PNAS Nexus's Data and Code Availability — mandatory public-repository deposition of all materials, data, code, and protocols upon publication, retention of raw unprocessed images, accession numbers/DOIs, the [dataset] citation tag, and a compliant availability statement. "Available on request" alone is not sufficient, and failure can be grounds for rejection or retraction.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pnasnexus-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 (pnasnexus-data) ## When to trigger - There is no **Data Availability Statement**, or it says only "available on request". - Sequences/structures/datasets are not deposited or have no accession numbers. - Custom analysis code or scripts are not in a public, archived repository. - Raw, unprocessed image files have been discarded. - Unique reagents/strains/cell lines have no sharing plan. ## PNAS Nexus's standard (the bar is strict, with teeth) PNAS Nexus has a **mandatory** open-data/open-code policy. In the journal's own words: - *"Authors must make all materials, data, and associated protocols, including code and scripts, used in the analysis of the study available to readers in a **public repository upon publication**."* - *"Authors agree to make all data and code used in the analysis of their study fully available upon request during the peer review process or upon publication."* - *"All data and any direct outputs from imaging systems must be retained in their **raw, unprocessed versions**."* - *"Failure or refusal to provide data upon request may be grounds for **rejection of the manuscript or retraction of the article**."* So: **public-repository de
- When to trigger
- PNAS Nexus's standard (the bar is strict, with teeth)
- Deposit in approved repositories (with accessions)
- Cite data and software properly: the [dataset] tag
- Data & Code Availability Statement (template)
- Where the statement and the data live
- Materials & reagents
- Ethics & compliance (as applicable)
- Output format
- Anti-patterns
What does the pnasnexus-data skill do?
Use to build PNAS Nexus's Data and Code Availability — mandatory public-repository deposition of all materials, data, code, and protocols upon publication, retention of raw unprocessed images, accession numbers/DOIs, the [dataset] citation tag, and a compliant availability statement. "Available on request" alone is not sufficient, and failure can be grounds for rejection or retraction.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pnasnexus-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.