pnasnexus-workflow
Use when deciding which pnasnexus-* sub-skill to invoke next, or when sequencing a manuscript from scope/significance test through reviewer rebuttal for PNAS Nexus (the fully open-access sibling journal of PNAS, published by Oxford University Press for the U.S. National Academy of Sciences). Routes — it does not replace — the specialized skills.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pnasnexus-workflow --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.
# PNAS Nexus Workflow Router (pnasnexus-workflow) ## Overview This is the router. It does not replace any specialized skill. It tells you **which pnasnexus-* skill to use at the current stage** of a manuscript aimed at *PNAS Nexus*. **PNAS Nexus is not flagship PNAS.** It is the **gold open-access sibling journal**, published by **Oxford University Press (OUP)** in partnership with the **National
What does the pnasnexus-workflow skill do?
Use when deciding which pnasnexus-* sub-skill to invoke next, or when sequencing a manuscript from scope/significance test through reviewer rebuttal for PNAS Nexus (the fully open-access sibling journal of PNAS, published by Oxford University Press for the U.S. National Academy of Sciences). Routes — it does not replace — the specialized skills.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pnasnexus-workflow --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.