pnasnexus-statistics
Use to enforce PNAS Nexus's statistics and reproducibility reporting — n and replication, test choice and assumptions, effect sizes with uncertainty, multiple-comparison control, randomization/blinding, sample-size justification, and reproducible code. Also covers whether a Registered Report (Stage 1/2) is the right route for confirmatory work.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pnasnexus-statistics --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.
# Statistics & Reproducibility (pnasnexus-statistics) ## When to trigger - Results report P values but not effect sizes or n. - "Three independent experiments" is claimed but replication is unclear. - Multiple comparisons are run with no correction. - A reviewer is likely to ask "were analyses pre-specified?" and there's no answer. - The analysis is not reproducible from the deposited code (`pnasn
What does the pnasnexus-statistics skill do?
Use to enforce PNAS Nexus's statistics and reproducibility reporting — n and replication, test choice and assumptions, effect sizes with uncertainty, multiple-comparison control, randomization/blinding, sample-size justification, and reproducible code. Also covers whether a Registered Report (Stage 1/2) is the right route for confirmatory work.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pnasnexus-statistics --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.