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 Study Design

ASecurity

Use to confirm study-design rigor and the mandatory prospective trial registration, protocol, and statistical analysis plan before writing up a clinical study for NEJM. Surfaces registration problems early — they cannot be fixed retroactively.

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

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-study-design --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Nejm Study Design?

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

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

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

Download with Pro
Files
SKILL.md
---
name: nejm-study-design
description: Use to confirm study-design rigor and the mandatory prospective trial registration, protocol, and statistical analysis plan before writing up a clinical study for NEJM. Surfaces registration problems early — they cannot be fixed retroactively.
---

# Study Design & Registration (nejm-study-design)

## When to trigger

- A trial is being written up and you must confirm it was registered **before enrollment**.
- There is no finalized protocol or statistical analysis plan to submit.
- The design (randomization, blinding, endpoints) needs to be stated rigorously for the Methods.
- An observational study needs its design (cohort / case-control / cross-sectional) named and justified.

## The non-negotiable: prospective trial registration

Per **ICMJE** policy (which NEJM enforces), a clinical trial must be **prospectively registered** in a public registry — **ClinicalTrials.gov** or a **WHO ICTRP** primary registry — **before the first patient is enrolled**. This is a deal-breaker, not a formatting detail.

- The **trial registration number** (e.g., an NCT number) is reported in the abstract and Methods.
- Registration must predate enrollment; retrospective registration is generally disqualifying for an Original Article.
- The registered **primary outcome** must match the reported primary outcome — discrepancies are a top reviewer flag.

> If a trial was never prospectively registered, raise it now. It changes venue and framing and cannot be repaired by writing.

## Protocol and statistical analysis plan (SAP)

For trials, NEJM expects the **full trial protocol** and the **statistical analysis plan** to be submitted (typically as a supplement) and made available to reviewers.

- The **SAP must be pre-specified** — finalized (and dated) before unblinding / database lock.
- Any **deviation** from the registered protocol or SAP must be disclosed and explained in the manuscript.
- A **CONSORT-aligned** trial write-up depends on these documents existing (see `nejm-reporting`).

## Design rigor checklist (trials)

- [ ] **Randomization** — method (e.g., permuted blocks, stratification factors) stated.
- [ ] **Allocation concealment** — mechanism described (central randomization, sealed envelopes).
- [ ] **Blinding** — who was blinded (participants, clinicians, outcome assessors, analysts); if open-label, justify and address bias.
- [ ] **Primary endpoint** — single, pre-specified, patient-important, with a clear definition and time point.
- [ ] **Secondary endpoints** — pre-specified and ordered; multiplicity handled (see `nejm-statistics`).
- [ ] **Sample size / power** — assumptions, effect size, alpha, power stated; not post hoc.
- [ ] **Analysis population** — **intention-to-treat** as primary; per-protocol as sensitivity.
- [ ] **Interim analyses / stopping rules** — DSMB, pre-specified boundaries (e.g., O'Brien-Fleming) if used.

## Observational studies

- Name the design: **cohort** (prospective/retrospective), **case-control**, **cross-sectional**, or nested designs.
- Pre-specify the primary exposure and outcome; define confounders and the adjustment strategy a priori.
- Address selection bias, information bias, and confounding explicitly; use cautious, non-causal language.
- Report per **STROBE** (see `nejm-reporting`); registration of observational protocols is encouraged though not mandated.

## Output format

```
【Study type】 RCT / other interventional / cohort / case-control / cross-sectional / SR-MA
【Registration】 registry + number + registered BEFORE enrollment? yes/no/UNREGISTERED-FLAG
【Registered vs reported primary outcome】 match? yes/no
【Protocol + SAP】 available, pre-specified, dated? yes/no
【Design rigor gaps】 randomization / concealment / blinding / endpoints / power / ITT
【Protocol/SAP deviations to disclose】 [...]
【Next】 nejm-reporting
```

## Anti-patterns

- **Do not** write up an unregistered trial as an Original Article without flagging it to the user.
- **Do not** present a post-hoc analysis plan as if it were pre-specified.
- **Do not** report a primary outcome that differs from the registered one without disclosing the change.
- **Do not** treat per-protocol as the primary analysis for a superiority trial — ITT is primary.

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 →