Agent skill

Pnasnexus Abstract

by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills

A skill your agent uses to write the PNAS Nexus abstract — a single self-contained paragraph of up to 250 words, with no headings, quantified and accessible to a broad scientific audience.

MITAuto-check passed

Install Pnasnexus Abstract

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pnasnexus-abstract -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills pnasnexus-abstract --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ 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-abstract .claude/skills/pnasnexus-abstract && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "pnasnexus-abstract" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PNAS-Nexus-Skills/skills/pnasnexus-abstract into .claude/skills/pnasnexus-abstract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pnasnexus-abstract", 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

$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PNAS-Nexus-Skills/skills/pnasnexus-abstract

Type 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.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pnasnexus-abstract -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills pnasnexus-abstract --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ 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-abstract .agents/skills/pnasnexus-abstract && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "pnasnexus-abstract" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PNAS-Nexus-Skills/skills/pnasnexus-abstract into .agents/skills/pnasnexus-abstract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pnasnexus-abstract", 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.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pnasnexus-abstract -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills pnasnexus-abstract --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ 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-abstract .cursor/skills/pnasnexus-abstract && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "pnasnexus-abstract" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PNAS-Nexus-Skills/skills/pnasnexus-abstract into .cursor/skills/pnasnexus-abstract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pnasnexus-abstract", 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

$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path PNAS-Nexus-Skills/skills/pnasnexus-abstract

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pnasnexus-abstract -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills pnasnexus-abstract --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ 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-abstract .gemini/skills/pnasnexus-abstract && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "pnasnexus-abstract" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PNAS-Nexus-Skills/skills/pnasnexus-abstract into .gemini/skills/pnasnexus-abstract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pnasnexus-abstract", 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.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills pnasnexus-abstract

Installs 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).

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pnasnexus-abstract -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ 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-abstract .github/skills/pnasnexus-abstract && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "pnasnexus-abstract" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PNAS-Nexus-Skills/skills/pnasnexus-abstract into .github/skills/pnasnexus-abstract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pnasnexus-abstract", 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.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pnasnexus-abstract -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills pnasnexus-abstract --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ 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-abstract .opencode/skills/pnasnexus-abstract && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "pnasnexus-abstract" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PNAS-Nexus-Skills/skills/pnasnexus-abstract into .opencode/skills/pnasnexus-abstract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pnasnexus-abstract", 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-abstract
GitHub stars: 1.2k
Token cost: ~1k tokens
SKILL.md length: 429 words
Files: 1
Skills in repo: 2,387
Repo updated: Sep 27, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

A skill your agent uses to write the PNAS Nexus abstract — a single self-contained paragraph of up to 250 words, with no headings, quantified and accessible to a broad scientific audience.

Works in 5 steps: Context / stakes (1–2 sentences) — the… → Gap / question (1 sentence) — what was… → What we did (1–2 sentences) — approach,… → …
Write the PNAS Nexus abstract — a single self-contained paragraph of up to 250 words
SKILL.md covers When to trigger, The PNAS Nexus abstract: ≤250…, Abstract vs Significance… and Recommended five-move…, plus 4 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Pnasnexus Abstract is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use to write the PNAS Nexus abstract — a single self-contained paragraph of up to 250 words, with no headings, quantified and accessible to a broad scientific audience. Distinguishes the abstract (what/how/found, for scientists) from the 50–120-word Significance Statement (why-it-matters, for everyone). Late-stage polish.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

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

Write the PNAS Nexus abstract — a single self-contained paragraph of up to 250 words
With no headings
Quantified and accessible to a broad scientific audience

Example prompts

“/pnasnexus-abstract”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

Context / stakes (1–2 sentences) — the broad problem.
Gap / question (1 sentence) — what was unknown.
What we did (1–2 sentences) — approach, in plain terms.
Key results, quantified (2–3 sentences) — the advance, with numbers and uncertainty.
Conclusion / implication (1 sentence) — what it means for the field, ideally across fields.

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 Abstract loads about 1k tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 429 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~86
When it runs · the whole SKILL.md, loaded when a task matches: ~1k

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). 429 words, ~1,004 tokens.

Download SKILL.mdSave it as .claude/skills/pnasnexus-abstract/SKILL.md (or your agent's skills folder).

name: pnasnexus-abstract
description: Use to write the PNAS Nexus abstract — a single self-contained paragraph of up to 250 words, with no headings, quantified and accessible to a broad scientific audience. Distinguishes the abstract (what/how/found, for scientists) from the 50–120-word Significance Statement (why-it-matters, for everyone). Late-stage polish.

Abstract (pnasnexus-abstract)

When to trigger

Fit, open access, structure, figures, stats, and data are settled (do this late).
The abstract reads like a methods recap with no result.
The abstract is being confused with, or duplicated from, the Significance Statement.
The abstract is over 250 words, has subheadings, or is jargon-dense.

The PNAS Nexus abstract: ≤250 words, single paragraph, no headings

Length: up to 250 words (PNAS Nexus states a 250-word maximum — confirm in current guidelines).
A single paragraph with no headings, no reference citations, no figure/table callouts. (PNAS Nexus's wording: "They should appear as a single paragraph with no headings.")
Self-contained: a reader who sees only the abstract should understand the question, what was done, what was found (quantified), and what it means.
Accessible to the broad PNAS Nexus readership spanning biological/health/medical, physical sciences & engineering, and social & political sciences — define or avoid acronyms.

The short, plain artifact PNAS Nexus requires is the Significance Statement (pnasnexus-significance, 50–120 words) — it is separate from the abstract. Do not merge them.

Abstract vs Significance Statement (keep them distinct)

Abstract	Significance Statement (`pnasnexus-significance`)
What/how/found, for scientists	Why it matters, for everyone
≤250 words, quantified, technical-but-clear	50–120 words, plain language
Stands in for the paper	Stands in for the "so what"

If the two read the same, the Significance Statement is wrong — fix it in pnasnexus-significance.

Recommended five-move structure (no labels in the text)

Context / stakes (1–2 sentences) — the broad problem.
Gap / question (1 sentence) — what was unknown.
What we did (1–2 sentences) — approach, in plain terms.
Key results, quantified (2–3 sentences) — the advance, with numbers and uncertainty.
Conclusion / implication (1 sentence) — what it means for the field, ideally across fields.

Show full SKILL.md (148 more words)Show less

Hard constraints

≤ 250 words (confirm the current cap).
Single paragraph, no subheadings, no citations, no figure/table references.
Define any acronym on first use, or avoid it.
At least one quantified result — magnitude + unit + uncertainty (CI/P), not "significantly increased".
First sentence comprehensible to a scientist outside the field.
Distinct in content and register from the Significance Statement.

Jargon blacklist (rewrite on sight)

"Herein we report…", "Importantly,", "Interestingly,", "Notably,"
Strings of ≥2 undefined acronyms in one sentence.
"elucidate", "delineate", "interrogate", "leverage" as filler verbs.
Hedging stacks: "may potentially suggest that it could…".

Output format

【Abstract】 single paragraph (word count: N ≤ 250)
【Single paragraph, no headings?】 yes/no
【Five moves present?】 context / gap / approach / quantified result / implication
【Quantified headline result?】 yes/no + the number
【Distinct from Significance Statement?】 yes/no
【Jargon hits removed】 [...]
【Next】 pnasnexus-citation

Anti-patterns

Do not reuse the 50–120-word Significance Statement as the abstract (or vice versa).
Do not add subheadings — PNAS Nexus abstracts are single unstructured paragraphs.
Do not open with method or organism; open with the stake.
Do not end on "further work is needed" — end on the implication.
Do not exceed 250 words "to be thorough".

Files

Just SKILL.md in PNAS-Nexus-Skills/skills/pnasnexus-abstract of brycewang-stanford/Awesome-Journal-Skills.

Open the folder on GitHubat commit 932eb23

Compare with similar skills

Pnasnexus Abstract 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.

Pnasnexus Abstract compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Pnasnexus Abstract this skillbrycewang-stanford/Awesome-Journal-Skills	1.2k	—	~1k	Automated safety check: Pass	MIT	14 days ago
Pnas Abstractfranklee16/academic-research-skills	223	1 repos	~965	Automated safety check: Pass	None	22 days ago
Apple Containersickn33/agentic-awesome-skills	47k	1 repos	~2.5k	Automated safety check: Pass	Apache-2.0	2 days ago
Abstractbrycewang-stanford/Auto-Empirical-Research-Skills	4.6k	—	~495	Automated safety check: Notes	Custom licence	5 days ago
Container Security Hardeningsickn33/agentic-awesome-skills	47k	1 repos	~1k	Automated safety check: Notes	MIT	2 days ago
Container Queriesthedaviddias/Front-End-Checklist	74k	—	~526	Automated safety check: Pass	MIT	4 days ago

Similar skills

Pnas Abstract
franklee16/academic-research-skills
A skill your agent uses to write the PNAS abstract — a single self-contained paragraph of ~250 words, quantified and accessible to a broad scientific audience.
223 GitHub starsUsed in 1 repo~965 tokens
Auto-check passed
Apple Container
sickn33/agentic-awesome-skills
Build, run, and manage OCI/Linux containers as lightweight per-container VMs on Apple-silicon macOS using Apple's open-source container CLI, no Docker daemon required.
47k GitHub starsUsed in 1 repo~2.5k tokens
DevOps & CloudAuto-check passed
Abstract
brycewang-stanford/Auto-Empirical-Research-Skills
Reads the manuscript and notebooks to generate a structured abstract.
4.6k GitHub stars~495 tokensUpdated 5 days ago
Auto-check: notes
Container Security Hardening
sickn33/agentic-awesome-skills
Harden Docker/container images and runtime deployments with secure base images, non-root users, CVE scanning, SBOM/signing, seccomp/AppArmor, and Kubernetes pod security controls.
47k GitHub starsUsed in 1 repo~1k tokens
SecurityAuto-check: notes
Container Queries
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing stylesheets, component styles, and responsive behavior related to Use container queries for component-level responsiveness.
74k GitHub stars~526 tokensUpdated 4 days ago
Frontend & DesignAuto-check passed
CSS Containment
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing stylesheets, component styles, and responsive behavior related to Use CSS containment to limit repaint scope.
74k GitHub stars~512 tokensUpdated 4 days ago
Frontend & DesignAuto-check passed

More from brycewang-stanford/Awesome-Journal-Skills

All 2,387 skills in this repo

Aaag 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…
1.2k GitHub stars~1.3k tokensUpdated 14 days ago
Auto-check passed
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…
1.2k GitHub stars~1.3k tokensUpdated 14 days ago
Auto-check passed
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…
1.2k GitHub stars~1.4k tokensUpdated 14 days ago
Auto-check passed
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…
1.2k GitHub stars~1.4k tokensUpdated 14 days ago
Auto-check passed
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…
1.2k GitHub stars~1.3k tokensUpdated 14 days ago
Auto-check passed
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…
1.2k GitHub stars~1.6k tokensUpdated 14 days ago
Auto-check passed

Questions about Pnasnexus Abstract

What does Pnasnexus Abstract do?

A skill your agent uses to write the PNAS Nexus abstract — a single self-contained paragraph of up to 250 words, with no headings, quantified and accessible to a broad scientific audience. Pnasnexus Abstract is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use to write the PNAS Nexus abstract — a single self-contained paragraph of up to 250 words, with no headings, quantified and accessible to a broad scientific audience.

When should I use Pnasnexus Abstract?

Pnasnexus Abstract fits situations like: write the PNAS Nexus abstract — a single self-contained paragraph of up to 250 words; with no headings; quantified and accessible to a broad scientific audience.

How do I install Pnasnexus Abstract in Claude Code?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pnasnexus-abstract -a claude-code`. Or copy the skill folder (PNAS-Nexus-Skills/skills/pnasnexus-abstract in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/pnasnexus-abstract in your project. Claude Code loads it when a task matches its description.

How do I install Pnasnexus Abstract in Codex?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pnasnexus-abstract -a codex`. Or copy the skill folder (PNAS-Nexus-Skills/skills/pnasnexus-abstract in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/pnasnexus-abstract in your project. Codex loads it when a task matches its description.

Can I use Pnasnexus Abstract 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-abstract -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-abstract, .gemini/skills/pnasnexus-abstract, .github/skills/pnasnexus-abstract and .opencode/skills/pnasnexus-abstract in your project.

What does Pnasnexus Abstract need to run?

SKILL.md names no scripts, command-line tools or credentials: Pnasnexus Abstract is instructions for the agent only.

Does Pnasnexus Abstract 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 Abstract 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 Abstract use?

Pnasnexus Abstract 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 Abstract use?

About 1k tokens (SKILL.md is roughly 4k 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 Abstract?

Skills that share tags, products or a category with Pnasnexus Abstract: Pnas Abstract (franklee16/academic-research-skills, 223 stars), Apple Container (sickn33/agentic-awesome-skills, 47k stars), Abstract (brycewang-stanford/Auto-Empirical-Research-Skills, 4.6k stars) and Container Security Hardening (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Pnasnexus Abstract?

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.

Install Pnasnexus Abstract

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Abstract (pnasnexus-abstract)

When to trigger

The PNAS Nexus abstract: ≤250 words, single paragraph, no headings

Abstract vs Significance Statement (keep them distinct)

Recommended five-move structure (no labels in the text)

Hard constraints

Jargon blacklist (rewrite on sight)

Output format

Anti-patterns

Files

Compare with similar skills

Similar skills

More from brycewang-stanford/Awesome-Journal-Skills

Questions about Pnasnexus Abstract