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

ASecurity

Use to lock study design and mandatory prospective registration for a Lancet clinical manuscript — trial registration before enrollment, protocol + statistical analysis plan, and design rigor (randomization, allocation concealment, blinding, pre-specified endpoints, power, ITT). Covers observational design choices too.

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

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

Installs into .claude/skills of the current project.

Are you the author of Lancet Study Design?

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

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

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

Download with Pro
Files
SKILL.md
---
name: lancet-study-design
description: Use to lock study design and mandatory prospective registration for a Lancet clinical manuscript — trial registration before enrollment, protocol + statistical analysis plan, and design rigor (randomization, allocation concealment, blinding, pre-specified endpoints, power, ITT). Covers observational design choices too.
---

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

## When to trigger

- Planning or writing up a clinical trial or a major observational study.
- The trial registration number is missing, or registration timing is unclear.
- There is no protocol or no pre-specified statistical analysis plan (SAP).
- A reviewer is likely to ask "was the primary endpoint pre-specified?" and there is no clear answer.

## Mandatory: prospective trial registration

The Lancet follows ICMJE: **clinical trials must be registered prospectively — before the first participant is enrolled — in a WHO-ICTRP primary registry or ClinicalTrials.gov.**

- [ ] Registered **before** enrollment of the first participant (retrospective registration is a serious, often fatal, problem — flag it immediately and disclose honestly).
- [ ] Registration number reported **in the abstract** and Methods (e.g., ClinicalTrials.gov NCTxxxxxxxx; ISRCTN; or a WHO-ICTRP primary registry).
- [ ] Registered outcomes match the reported primary/secondary outcomes; explain and flag any change.

| Registry | Use / region |
|----------|--------------|
| [ClinicalTrials.gov](https://clinicaltrials.gov/) | US and international |
| [ISRCTN](https://www.isrctn.com/) | UK / international |
| [WHO ICTRP](https://trialsearch.who.int/) | global portal aggregating primary registries (e.g., EU-CTR, ANZCTR, CTRI, ChiCTR, PACTR) |

> The Lancet often handles large **international / multi-country** trials — confirm registration in each relevant jurisdiction and report the lead registry.

## Protocol + statistical analysis plan (SAP)

- [ ] A **protocol** exists and (typically) is submitted with the manuscript; published-protocol citation if available.
- [ ] A **pre-specified SAP** defines the primary analysis, populations (ITT / per-protocol), handling of missing data, and pre-specified subgroups **before unblinding**.
- [ ] Any deviation from protocol/SAP is reported transparently with dates and rationale.

## Trial design rigor (RCT)

- [ ] **Randomization** method (sequence generation) described.
- [ ] **Allocation concealment** mechanism described (separate from blinding).
- [ ] **Blinding** of participants, clinicians, outcome assessors, and analysts — or justification if open-label.
- [ ] **Pre-specified primary endpoint**, clinically meaningful, with a clear hierarchy of secondary endpoints.
- [ ] **Sample size / power** justified for the clinically meaningful effect, with assumptions stated.
- [ ] **Intention-to-treat (ITT)** as the primary analysis population.
- [ ] Trial design named (parallel, cluster, crossover, factorial, adaptive, non-inferiority/equivalence — state the margin).
- [ ] Independent **data and safety monitoring committee (DSMC)** and any interim/stopping rules described.

## Observational design choices

- [ ] Design named (cohort, case-control, cross-sectional) and justified.
- [ ] Exposure/outcome definitions, eligibility, and follow-up specified a priori.
- [ ] Confounding strategy (matching, adjustment, propensity methods) pre-specified; causal language calibrated to the design.
- [ ] Registration/protocol encouraged for major observational studies (e.g., a pre-registered analysis plan).

## Output format

```
【Study type】 RCT (parallel/cluster/crossover/factorial/adaptive/NI) / observational (cohort/case-control/cross-sectional)
【Registration】 registry + number + prospective? (before first enrollment: yes/no) + in abstract? yes/no
【Protocol + SAP】 present? primary analysis & populations pre-specified? yes/no
【RCT rigor】 randomization / allocation concealment / blinding / primary endpoint / power / ITT  → gaps
【Observational rigor】 design / confounding strategy / causal language calibrated  → gaps
【Deviations from protocol/SAP】 [...] reported transparently? yes/no
【Next】 lancet-reporting
```

## Anti-patterns

- **Do not** submit a trial that was registered **after** enrollment without flagging it — The Lancet/ICMJE may decline to consider it.
- **Do not** report a primary outcome that differs from the registered one without an explicit, dated explanation.
- **Do not** present a post-hoc analysis as if it were pre-specified.
- **Do not** rely on per-protocol as the primary analysis for a superiority trial — ITT leads.

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 →