CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

real-world-evidence-study-designer

Designs a structured real-world evidence study using EHR, claims, or registry data, with explicit handling of time zero, eligibility windows, exposure definitions, outcome windows, censoring, confounding control, and target-trial-emulation logic. Use this skill when the user needs study-type design and protocol framing for an observational clinical study based on routine-care data. Do not invent database fields, follow-up completeness, linkage, coding validity, or causal identifiability.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, disciplined instruction skill with excellent progressive disclosure (verified real one-level reference bundle), strong actionability, and a clearly sequenced workflow with input-validation and completeness checkpoints. The main weakness is redundancy: Core Function, Workflow Standard, What This Skill Should Not Do, and Quality Standard substantially restate the output structure and hard rules, inflating token cost without adding guidance.

Suggestions

Merge 'Core Function' (12 items) and 'Workflow Standard' (10 steps) into a single workflow→output mapping, since both restate the A–L section structure; keep one canonical sequence and cut roughly 40-60 lines.

Fold 'What This Skill Should Not Do' and 'Quality Standard' into 'Hard Rules' and the existing 'Out-of-scope' handling — their bullets are near-duplicates of rules 1–10 and the input-validation section.

Add one worked micro-example (e.g., a filled-out Section E for the 'time zero and exposure windows for a claims analysis' trigger) to lift actionability from mostly-executable to copy-paste-ready guidance.

DimensionReasoningScore

Conciseness

The body avoids tutoring Claude on basic epidemiology and every section carries real content, but there is substantial redundancy across sections: 'Core Function' (12 numbered items) restates the A–L 'Mandatory Output Structure', 'Workflow Standard' (10 steps) repeats the same sequence, and 'What This Skill Should Not Do' and 'Quality Standard' overlap heavily with 'Hard Rules' and the 'Out-of-scope' list. This fits the level-3 anchor ('mostly efficient but... could be tightened') — not level 4, since the overlap is more than minor trimming, and not level 2, since no section is pure padding or explains things Claude already knows.

3 / 5

Actionability

Concrete, executable guidance for an instruction-only skill: an input-validation gate with a quoted redirect message to deliver verbatim, five concrete example inputs, an explicit A–L output template with per-section content specs, and ten hard rules phrased as checkable constraints. It is not level 5 because there is no worked example of a completed blueprint (e.g., a filled-out Section D/E for one of the sample triggers) covering the common case.

4 / 5

Workflow Clarity

The 10-step 'Workflow Standard' is clearly sequenced and maps onto output sections A–L and the reference modules; input validation is explicit ('respond with the redirect below and stop') and there is a completeness checkpoint ('If any output section is generated without using its corresponding reference module, the output should be treated as incomplete'). It falls short of level 5 because there are no explicit feedback/recovery loops (e.g., what to do when the user's data source is ambiguous mid-design), though the non-destructive nature of the task means the batch/destructive cap does not apply.

4 / 5

Progressive Disclosure

SKILL.md acts as an overview with all detail pushed to 9 real, one-level-deep reference files, each clearly signaled with a purpose and an explicit trigger ('use when judging whether an RWE design is appropriate in Section B'). All referenced paths exist in references/, none of them nest further references (verified), and mapping each module to specific output sections makes navigation easy — matching the level-5 anchor.

5 / 5

Total

16

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong third-person description that clearly states what the skill does and when to use it, with concrete design dimensions and an explicit anti-fabrication boundary. Trigger-term coverage is good but would benefit from a few more natural synonyms (e.g., 'RWE', 'cohort', 'retrospective').

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'explicit handling of time zero, eligibility windows, exposure definitions, outcome windows, censoring, confounding control, and target-trial-emulation logic' — covering the design task comprehensively, matching the level-5 anchor. It stays concrete rather than abstract, and the closing 'Do not invent database fields, follow-up completeness, linkage, coding validity, or causal identifiability' adds a concrete negative boundary.

5 / 5

Completeness

It explicitly answers 'what' ('Designs a structured real-world evidence study using EHR, claims, or registry data, with explicit handling of...') and 'when' ('Use this skill when the user needs study-type design and protocol framing for an observational clinical study based on routine-care data'), with concrete trigger phrases — matching the level-5 anchor. The scope boundary in the final sentence further sharpens both.

5 / 5

Trigger Term Quality

Good keyword coverage with natural terms users would say: 'real-world evidence', 'EHR', 'claims', 'registry', 'observational clinical study', 'routine-care data', 'target-trial-emulation'. A few common synonyms are missing — the 'RWE' abbreviation itself, 'cohort study', 'retrospective database study', 'pharmacoepidemiology' — which fits the level-4 anchor ('good keyword coverage; a few natural terms missing') rather than the comprehensive level-5 anchor.

4 / 5

Distinctiveness Conflict Risk

This is a clear niche — observational study design on routine-care data sources (EHR/claims/registry) with target-trial-emulation framing — with distinct triggers and minimal overlap risk against generic statistics, literature-review, or trial-design skills. It matches the level-5 anchor; it is not merely 'mostly distinct' as in level 4.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

awesome-med-research-skills/Protocol Design/real-world-evidence-study-designer/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.