Real-World Evidence Suitability Checklist Agent Skill

This skill reviews a proposed real-world evidence (RWE) study plan and drafts a checklist covering question readiness, data source fitness…

Context cost
3.7k tokensestimated from the bundle, loaded when it triggers
Bundle
5 files · 14.7 kBtext throughout, nothing executable
Licence
CC-BY-4.0the author’s own terms
Last change
—v0.1.0
Servers it uses
Noneruns standalone

What it does

This skill reviews a proposed real-world evidence (RWE) study plan and drafts a checklist covering question readiness, data source fitness (coding, capture, linkage, follow-up), design threats (confounding by indication, immortal time, channeling), and the transparency items regulators and journals expect. It is a planning and education tool; it does not generate evidence and does not support regulatory submissions by itself.

What this skill changes about the agent has not been set out here as a list. Its SKILL.md, shown below, says it in the author’s own words.

claims datadata sciencepharmacoepidemiologyreal-world evidencetarget trial emulation

The skill itself

A skill is instructions the model reads, so you can see what you are getting: below is the start of its SKILL.md. The front matter loads with every session, the body loads when the skill triggers, and the whole file comes with the install.

SKILL.md8.4 kB · preview
--- id: rwe-suitability-checklist name: "Real-World Evidence Suitability Checklist" version: "0.1.0" category: observational_research subcategory: real_world_evidence summary: "Check whether a data source and design can support a real-world evidence question, and what to disclose." intended_users: - pharmacoepidemiologists - health data scientists - regulatory affairs learners use_cases: - RWE study planning - data source assessment - methods education domain: - epidemiology - clinical_research task_type: - checklist - evaluate modality: - text - ehr lifecycle_stage: - protocol - analysis tags: - real-world evidence - pharmacoepidemiology - target trial emulation - claims data risk_class: R1 maturity: draft runtime: - prompt - checklist permissions: phi_allowed: false real_patient_data_allowed: false clinical_decision_making: false medication_dosing: false diagnosis: false internet_required: false external_api_required: false inputs: - name: study_plan type: string outputs: - name: checklist_json type: object parameters: [] prompt_system: > You are a real-world evidence methods reviewer. Draft a suitability checklist for a proposed RWE plan. Name threats and disclosure items; leave design decisions to the team. Do not produce evidence and do not give clinical advice. prompt_user: | Review the following real-world evidence plan and draft a suitability checklist. Plan: {study_plan} Return JSON with: { "question_readiness": [], "data_source_fitness": [], "design_threats": [], "transparency_items": [] } examples: - input: | plan: Does new users of a fictional oral anticoagulant have lower gastrointestinal bleeding risk than new users of an older comparator, using 5 years of a national claims database, new-user active-comparator design with propensity weighting? output: | { "question_readiness": [ "State the target trial: who is eligible, what is assigned, when follow-up starts, and what the contrast means; the observational plan should emulate it", "Define the outcome with the code set and a validation strategy (validated algorithms or chart review on a sample)" ], "data_source_fitness": [ "Claims capture dispensing well; verify bleeding outcomes are coded reliably in this database (validation studies exist for several code sets)", "Check linkage to any laboratory or hospital source the outcome needs", "Confirm follow-up length supports the event window" ], "design_threats": [ "Confounding by indication: record the indication and severity covariates the claims capture, and state what remains unmeasured", "Immortal time: cohort entry at dispensing with immediate follow-up; no person-time before treatment counted as treated", "Channeling: prior treatment history drives allocation; require new-user status for both groups" ], "transparency_items": [ "Pre-register the protocol and analysis plan", "Report the code sets, the propensity model specification, and diagnostics", "Report negative and positive control outcomes where available" ] } safety_notes: - "Planning and education tool only." - "Regulatory use of RWE requires formal frameworks and qualified review." limitations: - "Cannot assess data quality without the data; the checklist names what to check." - "Does not replace target-trial specification work by the study team." human_review_required: true references: - name: "Hernán MA, Robins JM" note: "Using big data to emulate a target trial when a randomized trial is not available. Am J Epidemiol 2016;183(8):758-64." - name: "Ray WA" note: "Evaluating medication effects outside of clinical trials: new-user designs. Am J Epidemiol 2003;158(9):915-20." - name: "GRACE principles" note: "Good ReseArch for Comparative Effectiveness (GRACE) principles for database studies." - name: "ICH M14" note: "ICH guideline work on real-world data suitability for regulatory decision-making (2024-2026 drafts)." status: active license: CC-BY-4.0 maintainers: - name: OpenMedSkills maintainers last_updated: "2026-08-29" content_reviewed: "2026-08" ---
135# Real-World Evidence Suitability Checklist
136
137## Purpose
138
139Real-world evidence requests usually arrive backwards: someone has a database and asks
140what it can prove. The useful question runs the other way. This skill reviews a
141proposed RWE plan and drafts a checklist in four parts: is the question ready to be
142asked of data, is the data source fit for it, which design threats must be handled,
143and what transparency items the output must carry. It is a planning and education tool
144for pharmacoepidemiology and health data teams.
145
146## Question readiness: start from the target trial
147
148The single most useful discipline in this field is writing the randomized trial you
149would have run: who is eligible, what is assigned, when follow-up starts, what the
150contrasts are, and what the analysis would be. The observational plan then emulates
151that trial with the data available. Where the emulation is impossible (no eligible
152population in the data, no plausible assignment time), the checklist says the question
153is not answerable with this source, which is a finding rather than a failure. Plans
This is a preview of SKILL.md. Download or install the skill to get the whole thing.
In the file
SKILL.md1,129 words
Files5
LicenceCC-BY-4.0
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈1,250
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
2,425
on trigger
The instruction body and 4 supporting files, read only when the skill fires.
1.8%
of a 200k window
Ten skills this size would take about 18% of the window before you open a file.
050k100k150k200k context window

3.7k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Middling. Fine to keep on in a project where you use it weekly, worth unloading in one where you never do.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

The procedure it runs

The procedure has not been set out here step by step. It is in the body of its SKILL.md: the start of it is shown above, and the whole file comes with the install.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

Its SKILL.md does not declare which tools it asks the agent for, so what it touches is whatever the instructions themselves ask for — read them before you install it.

What it asks for
Writes filesnot declared
Network accessnot declared

This SKILL.md carries no allowed-tools line, so neither is declared. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

5 files, 14.7 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • SKILL.md8.4 kB
  • whats-new-2026.md1.0 kB
  • evals/evals.md1.3 kB
  • examples/examples.md2.5 kB
  • references/references.md1.5 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 5 files you can review in full before installing. The CC-BY-4.0 licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

# Real-World Evidence Suitability Checklist · 3.7k tokens when loaded · macOS, Linux mkdir -p .claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/real-world-evidence-suitability-checklist/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/real-world-evidence-suitability-checklist" ] && { [ ! -e .claude/skills/real-world-evidence-suitability-checklist ] || { mv .claude/skills/real-world-evidence-suitability-checklist "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/real-world-evidence-suitability-checklist" .claude/skills/ && echo "Installed .claude/skills/real-world-evidence-suitability-checklist"
On Windows, or any OS with Node 20+
npx mcprush@latest skill add salikkhann/real-world-evidence-suitability-checklist

Windows PowerShell says 'running scripts is disabled on this system'? Run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither. Writes to .claude/skills/real-world-evidence-suitability-checklist/ in the current project. For every project instead, run mkdir -p ~/.claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/real-world-evidence-suitability-checklist/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/real-world-evidence-suitability-checklist" ] && { [ ! -e ~/.claude/skills/real-world-evidence-suitability-checklist ] || { mv ~/.claude/skills/real-world-evidence-suitability-checklist "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/real-world-evidence-suitability-checklist" ~/.claude/skills/ && echo "Installed ~/.claude/skills/real-world-evidence-suitability-checklist" (macOS, Linux) — or add --global to the npx line. The curl line replaces .claude/skills/real-world-evidence-suitability-checklist/ only after the download succeeds, so files left there by another skill of the same name, or by an older release, do not mix in. A copy already there is moved aside, not deleted, and the line prints where. It appears as Real-World Evidence Suitability Checklist in Gemini CLI, Codex, Copilot and Grok (its own name); Claude Code lists it by the folder name, real-world-evidence-suitability-checklist.

Which clients pick it up on their own

A skill is a folder of text. Most of these read a skills folder and pick it up without being told; the rest take the same folder another way — an upload in the app, a parameter on an API call — and then choose it by its description just the same.

Claude Code.claude/skills/
Claude DesktopCustomize › Skills
ChatGPTSkills › Create › Upload
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok Build.grok/skills/
Microsoft CopilotSkills › Upload a skill
PerplexityComputer › Skills › Upload a skill
DeepSeek Harness.dsh/skills/
Zed.agents/skills/
Devin Desktop.devin/skills/
Windsurf (legacy).windsurf/skills/
OpenAI Agents SDKInstructions or sandbox Skills
HTTP / APIa request parameter
This release
Version0.1.0
Publishedno release date on file
PriceFree
Referencesalikkhann/real-world-evidence-suitability-checklist

Versions

v0.1.0 is what is on the shelf; no release here carries a date. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v0.1.0
  • No earlier releases have been published to the marketplace.
Pinning

The install command always fetches the release that is current the day you run it — v0.1.0 today — and cannot ask for an earlier one. The copy on your disk does not change until you run it again.

Reviews

—no reviews yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Sign in to review it

A review is tied to an account so it can be answered, edited and taken down by the person who wrote it.

Sign in
Who can post

Anybody with an account, one review each. It carries the version that was current when you wrote it, and the publisher may reply once.

Who wrote it

SA
salikkhann

Publishes on mcprush.

0 servers listed1 skill listednot claimed
Profile
Publisher
Servers0
Claim this skill