CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

inclusion-exclusion-criteria-builder

Builds clear, executable, and auditable inclusion and exclusion criteria for biomedical and clinical research protocols. Always use this skill when a user needs to translate a target population into operational screening rules tied to chart fields, time windows, tests, procedures, prior therapies, exclusions, and reviewable edge cases. Focus on protocol-stage precision, ambiguity reduction, auditability, and screening reproducibility rather than generic study design advice.

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, instruction-only skill with an effective progressive-disclosure bundle: nine real reference files are clearly routed to specific output sections, and the workflow has strong validation checkpoints (clarification gate, pressure-test, self-critical review). The main cost is internal redundancy — reference routing and the clarification rule are each stated multiple times — which inflates token usage without adding guidance.

Suggestions

Merge 'Reference Module Integration' and 'Decision Logic' into a single section: keep the step order (Step 1–7) with its per-step reference and section mapping, and delete the duplicate file-by-file list, since both sections currently state the same routing twice.

State the clarification gate once — in 'Clarification-First Rule' (or Step 1 of Decision Logic) — and reduce the restatements in Hard Rule 1, 'Formatting Expectations', and 'Quality Standard' to brief cross-references.

Consolidate the three overlapping negative-scope lists ('This skill should not' in Core Function, 'What This Skill Should Not Do', and the out-of-scope list in Input Validation) into one canonical scope-boundary section.

DimensionReasoningScore

Conciseness

There is no over-explanation of concepts Claude already knows, but the body is noticeably repetitive and could be tightened: the nine reference modules are routed twice (once in 'Reference Module Integration' with section mappings, again step-by-step in 'Decision Logic'), the clarification gate is restated in 'Clarification-First Rule', Decision Logic Step 1, Hard Rule 1, 'Formatting Expectations', and 'Quality Standard', and 'What This Skill Should Not Do' overlaps 'Core Function' and 'Input Validation'. Not a 2 because the padding is structural duplication rather than explanatory filler, and each section is individually lean.

3 / 5

Actionability

For an instruction-only skill the guidance is largely executable: a mandatory output structure with defined sections A–J, a concrete operationalization-table column schema, a fill-in redirect template for out-of-scope requests, three labeled draft-status outcomes, and concrete input examples. Minor gaps remain — a few directives stay abstract ('This skill must be precise, skeptical, and implementation-aware') and the substantive criterion-drafting rules are deferred to the reference files rather than exemplified in the body, so it does not fully reach copy-paste-ready equivalent guidance.

4 / 5

Workflow Clarity

Decision Logic Steps 1–7 are clearly sequenced, each bound to a reference module and output sections, with validation checkpoints present: the mandatory clarification gate (Step 1), the ambiguity/contradiction pressure-test (Step 6), the self-critical risk review (Hard Rule 11), and Section J draft-status labeling. Not a 5 because there is no explicit iterate-back instruction — if Step 6 surfaces contradictions, the workflow proceeds to Step 7 without a stated fix-and-recheck loop.

4 / 5

Progressive Disclosure

The body is a genuine overview: all nine referenced files exist in references/ and each is signaled one level deep with a clear purpose and mapped output sections ('use when drafting inclusion rules in Sections C and F', etc.). Spot checks confirm the reference files contain the actual rules and do not nest further, so navigation is easy and content is appropriately split.

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 description: third-person voice, concrete multi-action capability statement, and an explicit 'Always use this skill when...' trigger clause with specific trigger conditions. The only weakness is a few missing natural synonyms ('eligibility criteria', 'EHR', 'chart review') that users would commonly say.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'Builds clear, executable, and auditable inclusion and exclusion criteria', 'translate a target population into operational screening rules tied to chart fields, time windows, tests, procedures, prior therapies, exclusions' — with comprehensive coverage of the skill's scope. It is not a level-4 case because there are no meaningful coverage gaps; the actions span drafting, operationalizing, and edge-case review.

5 / 5

Completeness

It explicitly answers both questions: what ('Builds clear, executable, and auditable inclusion and exclusion criteria for biomedical and clinical research protocols') and when ('Always use this skill when a user needs to translate a target population into operational screening rules...'). The 'when' clause includes concrete trigger conditions, matching the level-5 anchor exactly.

5 / 5

Trigger Term Quality

Good natural-term coverage: 'inclusion and exclusion criteria', 'target population', 'screening rules', 'chart fields', 'time windows', 'biomedical and clinical research protocols'. It misses common synonyms a user would naturally say, notably 'eligibility criteria' and 'EHR/chart review', which appear only in the body, not the description.

4 / 5

Distinctiveness Conflict Risk

Clear niche with distinct triggers — protocol-stage eligibility criteria construction — and it explicitly fences itself off from adjacent territory ('rather than generic study design advice'), minimizing conflict risk with broader study-design or statistics skills.

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/inclusion-exclusion-criteria-builder/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.