Content Research Writer
weapp-tailwindcss/weapp-tailwindcss
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section.
A skill your agent uses 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…
Install Pnasnexus Data
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pnasnexus-data -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pnasnexus-data --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/PNAS-Nexus-Skills/skills/pnasnexus-data .claude/skills/pnasnexus-data && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "pnasnexus-data" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PNAS-Nexus-Skills/skills/pnasnexus-data into .claude/skills/pnasnexus-data/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pnasnexus-data", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PNAS-Nexus-Skills/skills/pnasnexus-dataType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pnasnexus-data -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pnasnexus-data --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/PNAS-Nexus-Skills/skills/pnasnexus-data .agents/skills/pnasnexus-data && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pnasnexus-data" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PNAS-Nexus-Skills/skills/pnasnexus-data into .agents/skills/pnasnexus-data/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pnasnexus-data", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pnasnexus-data -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pnasnexus-data --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/PNAS-Nexus-Skills/skills/pnasnexus-data .cursor/skills/pnasnexus-data && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "pnasnexus-data" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PNAS-Nexus-Skills/skills/pnasnexus-data into .cursor/skills/pnasnexus-data/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pnasnexus-data", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path PNAS-Nexus-Skills/skills/pnasnexus-data--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pnasnexus-data -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pnasnexus-data --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/PNAS-Nexus-Skills/skills/pnasnexus-data .gemini/skills/pnasnexus-data && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "pnasnexus-data" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PNAS-Nexus-Skills/skills/pnasnexus-data into .gemini/skills/pnasnexus-data/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pnasnexus-data", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pnasnexus-dataInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pnasnexus-data -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/PNAS-Nexus-Skills/skills/pnasnexus-data .github/skills/pnasnexus-data && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "pnasnexus-data" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PNAS-Nexus-Skills/skills/pnasnexus-data into .github/skills/pnasnexus-data/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pnasnexus-data", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pnasnexus-data -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pnasnexus-data --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/PNAS-Nexus-Skills/skills/pnasnexus-data .opencode/skills/pnasnexus-data && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "pnasnexus-data" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PNAS-Nexus-Skills/skills/pnasnexus-data into .opencode/skills/pnasnexus-data/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pnasnexus-data", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
pnasnexus-data- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 656 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses 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…
- Build PNAS Nexuss Data and Code Availability — mandatory public-repository deposition of all materials
- SKILL.md covers When to trigger, PNAS Nexus's standard (the bar…, Deposit in approved… and Cite data and software…, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Protocols upon publication
What it does
Pnasnexus Data is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Research & Science, covering Citation management. The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Build PNAS Nexuss Data and Code Availability — mandatory public-repository deposition of all materials
- Protocols upon publication
- Retention of raw unprocessed images
- Accession numbers/DOIs
Example prompts
- “Available on request”
- “/pnasnexus-data”
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Pnasnexus Data loads about 1.5k tokens when it runs. Until then it costs about 101 tokens; SKILL.md has 656 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 656 words, ~1,530 tokens.
Download SKILL.mdSave it as
.claude/skills/pnasnexus-data/SKILL.md (or your agent's skills folder).- name
- pnasnexus-data
- description
- 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.
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 deposition upon publication is required, raw images must be kept, and non-compliance is an explicit rejection/retraction risk. (Confirm the current wording in PNAS Nexus author guidelines.)
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 |
| Proteomics | PRIDE / ProteomeXchange |
| Crystallographic data | CCDC / CSD |
| Generic datasets | Dryad / Zenodo / Figshare / OSF |
| Code / scripts | GitHub/GitLab + archived to Zenodo (DOI) |
- Obtain accession numbers / DOIs before/at publication; cite them in the Data Availability Statement and Materials and Methods.
- Code and scripts that produce the results must be public and archived (a versioned release with a citable DOI; a bare GitHub link is not durable).
Cite data and software properly: the [dataset] tag
PNAS Nexus follows the FORCE11 Data Citation Principles and asks authors to flag dataset references with the [dataset] tag in the reference list, so deposited data are formally cited (confirm the exact mechanics in current guidelines). Treat datasets and software as first-class citable objects, not just URLs in the text.
Show full SKILL.md (310 more words)Show less
Data & Code Availability Statement (template)
All data and code needed to evaluate the conclusions are present in the paper and/or the Supporting Information and have been deposited in a public repository. [Sequencing data: GEO, accession GSEXXXXXX.] [Structures: PDB, XXXX.] [Analysis code and scripts: Zenodo, DOI 10.5281/zenodo.XXXXXXX.] [Previously published data used here are available at …] [Restricted data (e.g., identifiable human-subjects data) are available from … under … subject to …, in line with the journal's policy.]
Avoid a bare "data available on request" for the primary data behind the figures; restricted human/clinical data must state the access procedure and the controlling body.
Where the statement and the data live
- The Data and Code Availability Statement is a required element of the article (near the end, with the back matter — confirm placement in current guidelines).
- Reference the deposited data in both the availability statement and the Materials and Methods, so a reader following the methods can reach the data.
- Datasets too large for a figure but central to the conclusions go to a repository cited by accession/DOI — not "available on request."
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/scripts public + archived DOI】 yes/no (link + DOI)
【Raw unprocessed images retained】 yes/no (required)
【Availability statement】 drafted? compliant (public repo on publication; no "on request" only for primary data)?
【[dataset] tags】 data/software cited as first-class objects? yes/no
【Materials sharing】 plan for unique reagents (Addgene/MTA)
【Ethics approvals】 IRB / IACUC / permits present where needed?
【Next】 pnasnexus-significanceAnti-patterns
- Do not write "data available on request" as the only provision for the primary data behind the figures.
- Do not discard raw/unprocessed image files — the policy requires retaining them.
- Do not link only to a personal/lab website (not durable) — use an archival repository with a DOI.
- Do not forget to deposit code and scripts publicly and archive a versioned release.
- Do not treat the data policy as advisory — non-compliance is an explicit rejection/retraction risk.
© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in PNAS-Nexus-Skills/skills/pnasnexus-data of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Pnasnexus Data next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Pnasnexus Data this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Content Research Writerweapp-tailwindcss/weapp-tailwindcss | 1.9k | 25 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Systematic Review ScreenerImbad0202/academic-research-skills | 51k | — | ~8.4k | Automated safety check: Pass | Custom licence | |
| NetworkxzLanqing/codex-claude-academic-skills | 4.7k | 15 repos | ~3.2k | Automated safety check: Pass | BSD-3-Clause | |
| Literature Reviewneflibata-feng/MyArxiv-Agent | 126 | 20 repos | ~5.9k | Automated safety check: Notes | MIT | |
| Openalex Databaseneflibata-feng/MyArxiv-Agent | 126 | 12 repos | ~3k | Automated safety check: Pass | Custom licence |
Similar skills
Systematic Review Screener
Imbad0202/academic-research-skills
Screens records for systematic, scoping and rapid reviews against fixed eligibility rules, using two blinded AI reviewers and a third adjudicator, with traceable PRISMA counts.
Networkx
zLanqing/codex-claude-academic-skills
Comprehensive toolkit for creating, analyzing, and visualizing complex networks and graphs in Python.
Literature Review
neflibata-feng/MyArxiv-Agent
Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.).
Openalex Database
neflibata-feng/MyArxiv-Agent
Query and analyze scholarly literature using the OpenAlex database.
Citation Verification Guide
Galaxy-Dawn/claude-scholar
Reference guidance for checking every citation in academic writing against canonical sources such as DOI, arXiv, CrossRef and Semantic Scholar, to catch fake or wrong references.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Related
Categories
Questions about Pnasnexus Data
What does Pnasnexus Data do?
A skill your agent uses 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…. Pnasnexus Data is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
When should I use Pnasnexus Data?
Pnasnexus Data fits situations like: build PNAS Nexuss Data and Code Availability — mandatory public-repository deposition of all materials; protocols upon publication; retention of raw unprocessed images; accession numbers/DOIs.
How do I install Pnasnexus Data in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pnasnexus-data -a claude-code`. Or copy the skill folder (PNAS-Nexus-Skills/skills/pnasnexus-data in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/pnasnexus-data in your project. Claude Code loads it when a task matches its description.
How do I install Pnasnexus Data in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pnasnexus-data -a codex`. Or copy the skill folder (PNAS-Nexus-Skills/skills/pnasnexus-data in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/pnasnexus-data in your project. Codex loads it when a task matches its description.
Can I use Pnasnexus Data in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pnasnexus-data -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pnasnexus-data, .gemini/skills/pnasnexus-data, .github/skills/pnasnexus-data and .opencode/skills/pnasnexus-data in your project.
What does Pnasnexus Data need to run?
SKILL.md names no scripts, command-line tools or credentials: Pnasnexus Data is instructions for the agent only.
Does Pnasnexus Data access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Pnasnexus Data safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Pnasnexus Data use?
Pnasnexus Data is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Pnasnexus Data use?
About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Pnasnexus Data?
Skills that share tags, products or a category with Pnasnexus Data: Content Research Writer (weapp-tailwindcss/weapp-tailwindcss, 1.9k stars), Systematic Review Screener (Imbad0202/academic-research-skills, 51k stars), Networkx (zLanqing/codex-claude-academic-skills, 4.7k stars) and Literature Review (neflibata-feng/MyArxiv-Agent, 126 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Pnasnexus Data?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.