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 Research In Context

ASecurity

Use to build The Lancet's signature Research in context panel — the three mandatory headed parts (Evidence before this study, Added value of this study, Implications of all the available evidence), grounded in a systematic literature search with stated databases, terms, and dates. Mandatory for original research Articles.

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

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-research-in-context --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Lancet Research In Context?

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

Security grade badge for Lancet Research In Context
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-lancet-research-in-context/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-lancet-research-in-context)

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

Download with Pro
Files
SKILL.md
---
name: lancet-research-in-context
description: Use to build The Lancet's signature Research in context panel — the three mandatory headed parts (Evidence before this study, Added value of this study, Implications of all the available evidence), grounded in a systematic literature search with stated databases, terms, and dates. Mandatory for original research Articles.
---

# Research in Context Panel (lancet-research-in-context)

## When to trigger

- Writing an original research **Article** for The Lancet (the panel is mandatory).
- There is no panel, or it reads like a discussion paragraph rather than the three required parts.
- The "Evidence before this study" part asserts what was known without a documented systematic search.
- New evidence appeared during review and the panel needs updating.

## Why this is the most distinctive Lancet skill

The **Research in context** panel is The Lancet's signature artifact and is **required for every original research Article**. It forces authors to place their study inside a **systematically searched** evidence base — not a cherry-picked introduction. Editors and reviewers read it early; a weak or search-free panel signals an unsystematic literature review.

## The panel has EXACTLY three headed parts

### 1. Evidence before this study

What was known **before** you did this study, and **how you found it**. This must describe a **systematic search**, not a casual reading:

- The databases searched (e.g., MEDLINE/PubMed, Embase, the Cochrane Library, regional databases such as LILACS/Global Index Medicus for global-health work).
- The **exact search terms / strategy** used.
- The **date range** (and the date the search was last run).
- Any **language restrictions** and inclusion criteria.
- A brief synthesis of what that evidence showed and what remained uncertain — including the **quality/limitations** of prior evidence (a GRADE-style judgement is welcome).

### 2. Added value of this study

What **your study adds** that the prior evidence did not provide — the specific new knowledge, in one short paragraph. Concrete and non-promotional: the new effect estimate, the new population/setting, the resolved uncertainty.

### 3. Implications of all the available evidence

What your findings **plus** the existing evidence mean **together** — for **clinical practice, public-health policy, and future research**. Calibrate causal/practice-changing language to the design. This is where the global-health/equity and policy implications belong.

## Exact template

```
Research in context

Evidence before this study
We searched [databases] for [study types] published between [start date] and
[end date / "the search was last updated on <date>"] using the terms
"[term 1]" AND "[term 2]" [AND "[term 3]"], with [language restrictions / none].
[Inclusion criteria.] [What the existing evidence showed and its key
uncertainties/limitations, ideally with a quality judgement.]

Added value of this study
[In one short paragraph: the specific new knowledge this study provides —
the new estimate, population, setting, or resolved uncertainty.]

Implications of all the available evidence
[What the totality of evidence now implies for clinical practice, for
public-health policy, and for future research — with calibrated causal
language and any equity/global-health implications.]
```

## Quality checks

- [ ] All three headed parts present, in order, with the exact headings.
- [ ] "Evidence before this study" documents a **real systematic search**: databases + terms + dates + language.
- [ ] The search supports the introduction and the abstract's Background (consistent claims).
- [ ] "Added value" is specific and non-promotional.
- [ ] "Implications" speaks to practice, policy, **and** research — not just "more research is needed."
- [ ] Total panel is concise (typically a few hundred words; confirm the current word guidance).

## Output format

```
【Panel parts present】 Evidence before / Added value / Implications — all three? yes/no
【Systematic search documented】 databases + terms + dates + language? yes/no (list gaps)
【Consistency】 search matches Introduction + abstract Background? yes/no
【Added value specific?】 yes/no
【Implications cover practice + policy + research?】 yes/no
【Drafted panel】 the three-part panel, filled
【Next】 lancet-abstract
```

## Anti-patterns

- **Do not** write "Evidence before this study" from memory — it must reflect a documented search with terms and dates.
- **Do not** merge the three parts into one paragraph or drop a heading.
- **Do not** overstate "Added value" beyond what the data support.
- **Do not** end "Implications" on a generic "further studies are warranted" — name the practice/policy consequence.

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 →