Agent skill · Code Review & Quality

jama-statistics

Use when preparing or auditing the statistical analysis and reporting of a JAMA manuscript so it survives JAMA's dedicated statistical review. Enforces effect sizes with 95% CIs, multiplicity control, and pre-specification; it does NOT choose the study design or write prose.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jama-statistics --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Path: JAMA-Skills/skills/jama-statistics/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Statistics & Statistical Review (jama-statistics) ## When to trigger - Results report p-values without effect sizes or confidence intervals - Many comparisons but no multiplicity plan - The analysis was not pre-specified, or outcomes drifted from the protocol - Preparing for JAMA's **dedicated statistical review** of accepted-pending manuscripts ## Core reporting rules at JAMA 1. **Effect sizes with 95% CIs, not p-values alone.** Report the estimate (mean difference, risk/hazard/odds ratio, absolute risk difference) **with its 95% CI**. P-values supplement; they do not substitute. Treat "significance" as a statement about the interval, not a 0.05 threshold ritual. 2. **Pre-specified outcomes.** State the single primary outcome and the secondary outcomes exactly as registered/protocoled. Flag any post hoc analysis as exploratory. 3. **Intention-to-treat for RCTs.** Primary analysis is ITT; per-protocol and as-treated are secondary/sensitivity. 4. **Multiplicity.** With multiple outcomes, subgroups, or time points, pre-specify the testing hierarchy and the correction (e.g., hierarchical testing, Bonferroni/Holm, gatekeeping). Subgroups without a multiplicity plan are hypothesis-gen

What's inside
Steps it walks through
  1. When to trigger
  2. Core reporting rules at JAMA
  3. Reporting conventions to follow
  4. Audit table
  5. Surviving JAMA's independent statistical review
  6. Worked example: a primary-outcome readout (illustrative)
  7. Reviewer pushback and the JAMA fix
  8. Checklist
  9. Anti-patterns
  10. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the jama-statistics skill do?

Use when preparing or auditing the statistical analysis and reporting of a JAMA manuscript so it survives JAMA's dedicated statistical review. Enforces effect sizes with 95% CIs, multiplicity control, and pre-specification; it does NOT choose the study design or write prose.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jama-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.

Keep going