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 Abstract

ASecurity

Use to write The Lancet's structured abstract — ≤300 words under the exact headings Background, Methods, Findings, Interpretation, Funding — leading with the clinical question, reporting the primary outcome with effect size and 95% CI, citing the registration number, and naming the funder.

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-abstract --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Lancet Abstract?

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

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

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

Download with Pro
Files
SKILL.md
---
name: lancet-abstract
description: Use to write The Lancet's structured abstract — ≤300 words under the exact headings Background, Methods, Findings, Interpretation, Funding — leading with the clinical question, reporting the primary outcome with effect size and 95% CI, citing the registration number, and naming the funder.
---

# Structured Abstract (lancet-abstract)

## When to trigger

- The design, reporting, and statistics are settled (do this late).
- The abstract is unstructured prose, over 300 words, or uses the wrong headings.
- The abstract uses "Results" and "Conclusions" — The Lancet uses **Findings** and **Interpretation**.
- The registration number or funder is missing from the abstract.

## The Lancet's five mandatory headings

The Lancet uses a structured abstract of **≤300 words** (confirm the exact cap in the current author guidelines) under these specific headings — and the wording of two of them is distinctive:

1. **Background** — the clinical/public-health problem and the specific question. One or two sentences.
2. **Methods** — design, setting (and countries, for multi-country trials), participants and eligibility, intervention/exposure and comparator, primary outcome, analysis population (ITT), and the **trial registration number** (e.g., ClinicalTrials.gov NCTxxxxxxxx; ISRCTN).
3. **Findings** *(not "Results")* — recruitment dates and numbers analysed; the **primary outcome with effect size and 95% CI** (absolute and relative where relevant); key secondary outcomes; principal harms/adverse events.
4. **Interpretation** *(not "Conclusions")* — what the findings mean for practice or policy, calibrated to the design; the single most important takeaway. No "more research is needed" as the whole message.
5. **Funding** — name the **funder(s)** (and "none" if unfunded). The Lancet requires the funding source in the abstract.

## Concrete template

```
Background  [The clinical/public-health problem and the specific question this study answers.]

Methods  We did a [design: e.g., multicentre, double-blind, randomised, placebo-controlled
trial] in [n] centres in [countries]. [Eligible participants were ...]. We randomly assigned
participants ([ratio]) to [intervention] or [comparator] [stratified by ...]. The primary
outcome was [outcome] in the [intention-to-treat] population. This trial is registered with
[registry], [number].

Findings  Between [date] and [date], we [screened/enrolled n and] assigned [n] participants
([n] to intervention, [n] to comparator). [Primary outcome] occurred in [n/N (%)] versus
[n/N (%)] (absolute difference [x%, 95% CI a–b]; [relative measure e.g. HR/RR/OR x.x,
95% CI a–b]; p=[exact]). [Key secondary outcome.] [Principal harms: serious adverse events
in n (%) vs n (%).]

Interpretation  [What this means for practice or policy, calibrated to the design — the
single most important, globally relevant takeaway.]

Funding  [Funder name(s); or "None".]
```

## Hard constraints

- [ ] ≤ ~300 words (confirm current cap; treat 300 as the ceiling).
- [ ] Exact headings: **Background, Methods, Findings, Interpretation, Funding** — "Findings" not "Results", "Interpretation" not "Conclusions".
- [ ] **Registration number** present (in Methods).
- [ ] Primary outcome reported with **effect size + 95% CI** (absolute and relative where applicable), not P alone.
- [ ] **Funder named** (or "None").
- [ ] Numbers in the abstract match the flow diagram and Table 1.

## Output format

```
【Headings correct?】 Background / Methods / Findings / Interpretation / Funding — exact? yes/no
【Word count】 N ≤ 300
【Registration number in Methods?】 yes/no
【Primary outcome with effect size + 95% CI?】 yes/no + the numbers
【Funder named?】 yes/no
【Findings/abstract numbers reconcile with flow diagram + Table 1?】 yes/no
【Drafted abstract】 the five-section abstract, filled
【Next】 lancet-writing
```

## Anti-patterns

- **Do not** label the sections "Results" / "Conclusions" — use Findings / Interpretation.
- **Do not** omit the registration number or the funder.
- **Do not** report only a relative effect (HR/OR/RR) when an absolute effect is informative.
- **Do not** end Interpretation on "further research is needed" as the sole message — state the practice/policy implication.

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 →