Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Jama Statistics

ASecurity

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.

1,052 stars
0 votes
0 copies
0 views
Added 6/5/2026
ai-agentstesting

Works with

cli

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill jama-statistics --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Jama Statistics?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Jama Statistics
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-jama-statistics/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-jama-statistics)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: jama-statistics
description: 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.
---

# 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-generating only.
5. **Missing data.** State the mechanism assumed and the method (e.g., multiple imputation); report a sensitivity analysis. Complete-case-only needs justification.
6. **Model assumptions.** Justify the model (proportional hazards, linearity, clustering, repeated measures) and report how assumptions were checked.
7. **Absolute and relative effects.** Pair relative measures (RR, OR, HR) with absolute measures (risk difference, NNT) so clinicians grasp magnitude.

## Reporting conventions to follow

- Report exact p-values (e.g., P = .03), not "P < .05"; very small as "P < .001"
- Round sensibly; do not imply false precision
- Give denominators with every percentage; report n/N
- Pre-register and report the analysis population for each estimate
- Describe software and key procedures so the analysis is reproducible
- For meta-analysis: report heterogeneity (e.g., I²), the model (fixed/random), and sensitivity analyses

## Audit table

| Symptom                                          | Fix                                                  |
|--------------------------------------------------|------------------------------------------------------|
| "P < 0.05" with no estimate                      | Add point estimate + 95% CI                          |
| Five "key" secondary outcomes, all "significant" | Pre-specify hierarchy; correct for multiplicity      |
| Subgroup result drives the conclusion            | Label exploratory; report interaction test           |
| RCT analyzed per-protocol as primary             | Re-run ITT as primary                                |
| 20% dropout, complete-case only                  | Multiple imputation + sensitivity analysis           |
| Only relative risk reported                      | Add absolute risk difference / NNT                   |

## Checklist

- [ ] Every primary/secondary estimate has a 95% CI
- [ ] Single pre-specified primary outcome; secondaries labeled
- [ ] Multiplicity handled with a pre-specified plan
- [ ] ITT is the primary analysis for the RCT
- [ ] Missing-data method stated + sensitivity analysis
- [ ] Absolute and relative effects both reported
- [ ] Model assumptions justified and checked
- [ ] Analysis is reproducible (software, code/procedures described)

## Anti-patterns

- Reporting p-values without effect sizes or CIs
- Switching or under-reporting pre-specified outcomes
- Mining subgroups and reporting only the "significant" one
- Claiming "no difference" from an underpowered study (absence of evidence ≠ evidence of absence)
- Per-protocol-as-primary to make an RCT look better
- Conclusions built on a secondary outcome while the primary was null

## Output format

```
【Primary outcome estimate + 95% CI】...
【All estimates have CIs】yes / no
【Multiplicity plan】... 
【ITT primary (RCT)】yes / no / n.a.
【Missing-data handling】...
【Absolute + relative effects reported】yes / no
【Stat-review risks remaining】...
【Next skill】jama-figures-tables
```

Attribution

brycewang-stanfordbrycewang-stanford
View sourceMore from brycewang-stanford →
SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1066601 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

693161 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

651 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →