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

Nejm Statistics

ASecurity

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.

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

Works with

cli

Security Analysis

A100/100

Scanned 6/6/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Nejm Statistics?

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

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

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

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

# 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; **per-protocol** is a sensitivity analysis. (For non-inferiority, both ITT and per-protocol matter — report both.)
- State the analysis model (e.g., Cox, logistic, mixed model) and pre-specified covariates/stratification.

## Multiplicity (the secondary-endpoint trap)

- Pre-specify a **testing hierarchy** or a multiplicity adjustment (e.g., gatekeeping, Hochberg, Bonferroni) for multiple primary/secondary endpoints.
- Endpoints **not** in the controlled testing scheme are **exploratory** — say so, and report estimates with CIs but no inferential P claims.
- Do not declare a secondary endpoint "significant" if it sits outside the multiplicity plan.

## Subgroups (warn against over-interpretation)

- Subgroup analyses must be **pre-specified**; label post-hoc subgroups as exploratory.
- Test the **interaction** (treatment × subgroup), not just within-subgroup P values — a within-subgroup "significant" effect without a significant interaction is weak evidence.
- Present subgroups in a **forest plot** with interaction P values (see `nejm-figures-tables`).
- Do not let a subgroup result become the headline of an otherwise null trial.

## Absolute risk and NNT

- Report **absolute risk difference** alongside relative measures — a large relative reduction on a rare outcome can be a tiny absolute one.
- Where clinically meaningful, give the **number needed to treat (NNT)** (or number needed to harm).
- For safety, report **absolute event rates** by arm, not relative comparisons alone.

## Missing data, survival, and other essentials

- State the **amount and pattern of missing data** and the handling (e.g., multiple imputation); avoid naive last-observation-carried-forward as the primary approach.
- **Time-to-event**: Kaplan–Meier with numbers-at-risk; Cox model with the proportional-hazards assumption checked; report median follow-up.
- Pre-specify **interim analyses / stopping boundaries**; report them if a DSMB acted.
- For non-inferiority: state the pre-specified **margin** and its justification.

## Output format

```
【Per-outcome reporting】 effect + 95% CI present for primary + key secondary? gaps: [...]
【Primary analysis population】 ITT primary? per-protocol as sensitivity? yes/no
【Multiplicity】 hierarchy/adjustment pre-specified? exploratory endpoints labeled? yes/no
【Subgroups】 pre-specified? interaction tests reported? over-interpretation flags: [...]
【Absolute risk + NNT】 reported alongside relative measures? yes/no
【Missing data / survival / non-inferiority margin】 handled & stated? yes/no
【Causal language (observational)】 appropriately cautious? yes/no
【Next】 nejm-figures-tables
```

## Anti-patterns

- **Do not** report relative risk without absolute risk for clinical outcomes.
- **Do not** declare secondary or subgroup endpoints significant outside the multiplicity plan.
- **Do not** infer "no effect" from a wide CI crossing the null on an underpowered comparison.
- **Do not** use causal verbs ("reduced", "caused") for observational associations.
- **Do not** make per-protocol the primary analysis in a superiority trial.

Attribution

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

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

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

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

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 →