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

Lancet Statistics

ASecurity

Use to enforce The Lancet's clinical-statistics reporting — confidence intervals over bare P values, a pre-specified primary analysis, intention-to-treat with per-protocol sensitivity, multiplicity control for secondary endpoints, cautious pre-specified subgroup analyses with interaction tests, missing-data handling, and absolute plus relative effects.

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 lancet-statistics --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Lancet Statistics?

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

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

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

Download with Pro
Files
SKILL.md
---
name: lancet-statistics
description: Use to enforce The Lancet's clinical-statistics reporting — confidence intervals over bare P values, a pre-specified primary analysis, intention-to-treat with per-protocol sensitivity, multiplicity control for secondary endpoints, cautious pre-specified subgroup analyses with interaction tests, missing-data handling, and absolute plus relative effects.
---

# Clinical Statistics (lancet-statistics)

## When to trigger

- Results report P values but not confidence intervals or effect sizes.
- The primary analysis population (ITT vs per-protocol) is unclear.
- Many secondary endpoints or subgroups are reported with no multiplicity/interaction handling.
- A **statistical reviewer** is likely (The Lancet uses them) and the analysis is not pre-specified.

## The reporting backbone (every clinical estimate)

Each estimate needs: **effect measure + 95% CI + the analysis population + the pre-specified test.**

- [ ] **Confidence intervals** for every key estimate — CIs over bare P values; The Lancet de-emphasises isolated significance.
- [ ] **Exact P values** (e.g., p=0·013), not "p<0·05," reported alongside CIs, not instead of them.
- [ ] **Absolute and relative effects**: report the absolute risk/rate difference *and* the relative measure (RR/OR/HR); add **NNT/NNH** where clinically relevant.
- [ ] **Analysis population stated**: ITT as the primary population for superiority RCTs.
- [ ] The **test/model named** and matched to outcome type (survival → Cox/log-rank; binary → logistic/risk; count → Poisson/negative binomial; clustered → mixed/GEE).

## Pre-specification and the primary analysis

- The **primary analysis is pre-specified** in the SAP (see `lancet-study-design`) before unblinding.
- Report the pre-specified primary analysis first; clearly label any post-hoc analysis as post-hoc.
- For **non-inferiority/equivalence** trials: state the margin, justify it, and analyse both ITT and per-protocol (per-protocol matters here).

## ITT and sensitivity analyses

- **ITT** primary; **per-protocol** as a pre-specified sensitivity analysis (especially for non-inferiority).
- Report **missing data** explicitly: amount, pattern, and the handling method (e.g., multiple imputation), with sensitivity analyses under different assumptions. Do not silently use complete-case only.

## Multiplicity and secondary endpoints

- Control for **multiplicity** across multiple primary/secondary endpoints (hierarchical testing, alpha-splitting, or correction) and state the strategy.
- Secondary endpoints are **supportive**, not confirmatory, unless pre-specified within a multiplicity-controlled hierarchy — say so.

## Subgroups — pre-specified and cautious

- Report only **pre-specified** subgroups; label any post-hoc subgroup as exploratory.
- Test the **interaction** (treatment × subgroup), not separate within-subgroup P values — and interpret cautiously; subgroup claims are a classic over-interpretation trap.
- Present subgroups in a **forest plot** with interaction P values (see `lancet-figures-tables`).

## Survival and time-to-event

- Kaplan–Meier estimates with **numbers at risk**; hazard ratios with 95% CI from Cox models; state the proportional-hazards assumption check.

## Output format

```
【Per-estimate backbone】 effect measure + 95% CI / analysis population / test  → list gaps
【CIs over bare P?】 yes/no   【Exact P reported?】 yes/no
【Absolute + relative effects (NNT where relevant)?】 yes/no
【Primary analysis pre-specified + ITT?】 yes/no
【Missing data handled + sensitivity?】 yes/no
【Multiplicity strategy for secondary endpoints?】 stated / missing
【Subgroups pre-specified + interaction tested + cautious?】 yes/no
【Survival: KM + numbers at risk + HR(CI)?】 yes/no/NA
【Next】 lancet-figures-tables
```

## Anti-patterns

- **Do not** report P values without confidence intervals or effect sizes.
- **Do not** report only a relative effect (HR/OR/RR) when the absolute effect changes the clinical message.
- **Do not** present per-protocol as the primary analysis for a superiority trial.
- **Do not** mine subgroups: separate within-subgroup P values without an interaction test invite over-interpretation.
- **Do not** infer "no effect" from a non-significant result in an underpowered analysis.

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', ...

686011 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 →