nejm-statistics
Use to enforce NEJM's clinical statistical reporting — confidence intervals over bare P values, the pre-specified intention-to-treat primary analysis, multiplicity control for secondary endpoints, pre-specified subgroups with interaction tests, missing-data handling, and absolute risk with NNT alongside relative measures.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nejm-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.
# Clinical Statistics & Reporting (nejm-statistics) ## When to trigger - Results report P values without confidence intervals. - The primary analysis population (ITT vs per-protocol) is unclear. - Many secondary endpoints are tested with no multiplicity plan. - Subgroup findings are highlighted without pre-specification or interaction tests. - Only relative risk is reported, with no absolute risk or NNT. ## Confidence intervals over bare P values NEJM's statistical reporting guidance favors **effect estimates with 95% confidence intervals** over bare significance tests. - [ ] Every primary and key secondary outcome: **effect estimate + 95% CI** (HR/RR/OR or mean difference). - [ ] Report **exact P values** (e.g., P=0.03), not "P<0.05", except for very small values. - [ ] A CI that includes the null is not "no difference" — report the estimate and its width; interpret precision. - [ ] For observational data, use **cautious, non-causal language** (associated with, not causes). ## The pre-specified primary analysis - The **primary outcome** is single and pre-specified; its analysis follows the SAP. - **Intention-to-treat** is the primary analysis population for superiority trials; **p
- When to trigger
- Confidence intervals over bare P values
- The pre-specified primary analysis
- Multiplicity (the secondary-endpoint trap)
- Subgroups (warn against over-interpretation)
- Absolute risk and NNT
- Missing data, survival, and other essentials
- What the statistical reviewer probes
- Worked micro-example — a subgroup claim (before → after)
- Output format
- Anti-patterns
What does the nejm-statistics skill do?
Use to enforce NEJM's clinical statistical reporting — confidence intervals over bare P values, the pre-specified intention-to-treat primary analysis, multiplicity control for secondary endpoints, pre-specified subgroups with interaction tests, missing-data handling, and absolute risk with NNT alongside relative measures.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nejm-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.