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 Reporting

ASecurity

Use to select and apply the correct EQUATOR reporting guideline for a Lancet manuscript — CONSORT for RCTs (with the mandatory flow diagram), STROBE for observational studies, PRISMA for systematic reviews/meta-analyses, SPIRIT for protocols — and to attach the completed checklist and study-flow diagram.

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

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Lancet Reporting?

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

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

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

Download with Pro
Files
SKILL.md
---
name: lancet-reporting
description: Use to select and apply the correct EQUATOR reporting guideline for a Lancet manuscript — CONSORT for RCTs (with the mandatory flow diagram), STROBE for observational studies, PRISMA for systematic reviews/meta-analyses, SPIRIT for protocols — and to attach the completed checklist and study-flow diagram.
---

# Reporting Guidelines & Flow Diagrams (lancet-reporting)

## When to trigger

- The study type is settled and you need the matching reporting checklist.
- There is no participant flow diagram (CONSORT/PRISMA) in the manuscript.
- A reviewer or editor asks for a completed reporting checklist with page/line references.
- The manuscript mixes endpoints/numbers that the flow diagram should reconcile.

## Pick the guideline by study type (via EQUATOR)

The Lancet requires the appropriate [EQUATOR Network](https://www.equator-network.org/) reporting guideline and a completed checklist on submission.

| Study type | Guideline | Mandatory diagram |
|------------|-----------|-------------------|
| Randomized controlled trial | **[CONSORT](https://www.consort-statement.org/)** (+ extensions: cluster, non-inferiority, pragmatic, harms, PRO) | **CONSORT flow diagram** (enrollment → allocation → follow-up → analysis) |
| Observational (cohort, case-control, cross-sectional) | **[STROBE](https://www.strobe-statement.org/)** | Participant flow / selection diagram |
| Systematic review / meta-analysis | **[PRISMA](https://www.prisma-statement.org/)** (+ PRISMA-P for protocols) | **PRISMA flow diagram** (records → screened → included) |
| Trial / review **protocol** | **SPIRIT** (trials) / **PRISMA-P** (reviews) | — |
| Diagnostic accuracy | **STARD** | Patient flow |
| Prediction model | **TRIPOD** | — |
| Quality improvement | **SQUIRE** | — |
| Economic evaluation | **CHEERS** | — |

## The flow diagram is mandatory for RCTs and systematic reviews

- [ ] **CONSORT flow diagram** present for every RCT: numbers assessed for eligibility, excluded (with reasons), randomized, allocated, lost to follow-up/discontinued (with reasons), and analyzed in each arm.
- [ ] **PRISMA flow diagram** present for every systematic review/meta-analysis: records identified, duplicates removed, screened, full-text assessed, excluded (with reasons), and included.
- [ ] Every number in the flow diagram **reconciles** with Table 1, the analysis populations, and the abstract.

## Checklist discipline

- [ ] Complete the official checklist for the chosen guideline.
- [ ] Map each item to a **page and line** in the manuscript (editors and reviewers check this).
- [ ] Use the correct **extension** (e.g., CONSORT cluster for cluster-randomized trials; CONSORT harms for adverse-event reporting; CONSORT-PRO for patient-reported outcomes).
- [ ] Submit the checklist as a supplementary file.

## Equity-relevant reporting

- Apply equity-focused extensions where relevant (e.g., **PRISMA-Equity**, **CONSORT-Equity** considerations) and the **PROGRESS-Plus** framework for reporting equity-relevant participant characteristics.
- Coordinate sex/gender and race/ethnicity reporting with `lancet-ethics` (SAGER guidelines).

## Output format

```
【Study type】 RCT / observational / systematic review / protocol / other
【Guideline + extension】 CONSORT(+ext) / STROBE / PRISMA(+ext) / SPIRIT / STARD / TRIPOD / ...
【Flow diagram】 present & required? CONSORT / PRISMA / N/A  → gaps
【Flow numbers reconcile】 with Table 1 + analysis populations + abstract? yes/no
【Checklist】 completed + page/line mapped? yes/no
【Equity reporting】 PROGRESS-Plus / equity extension applied where relevant? yes/no
【Next】 lancet-statistics
```

## Anti-patterns

- **Do not** submit an RCT without a CONSORT flow diagram, or a systematic review without a PRISMA one.
- **Do not** leave flow-diagram numbers that disagree with the analysis populations or Table 1.
- **Do not** submit a checklist with "see manuscript" instead of specific page/line references.
- **Do not** use the base guideline when an extension fits the design better (cluster, non-inferiority, pragmatic, harms).

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 →