CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

case-control-study-planner

Design a structured case-control study framework with explicit source population logic, control selection rules, matching decisions, exposure measurement planning, and bias-control checkpoints.

Quality

74%

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

Fix and improve this skill with Tessl

tessl review fix ./awesome-med-research-skills/Protocol Design/case-control-study-planner/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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.

The body delivers a well-sequenced, genuinely actionable design workflow with a clearly signaled one-level-deep reference bundle. Its main weakness is redundancy: prohibition and hard-rule content is restated across multiple body sections and largely duplicated in the reference files, inflating token cost without adding guidance value.

Suggestions

Consolidate the overlapping prohibition sections — 'What This Skill Is Not For', 'Hard Rules', and 'What This Skill Should Not Do' repeat matching, biomarker-timing, and OR-vs-RR rules; keep one authoritative rule set and delete the duplicates.

Move the detailed Hard Rules and Formatting Expectations content into the existing reference modules (especially references/05_output-style-and-hard-rules.md) and keep only a brief pointer in SKILL.md, reducing the body to a lean overview.

Add one worked mini-example of the mandatory output structure (e.g., a filled-in Bias-Control Matrix row or Variable Collection tier table) to make the required output format fully concrete.

DimensionReasoningScore

Conciseness

The body is mostly efficient domain decision logic rather than basic-concept padding, but prohibitions repeat across sections: matching rules appear in 'What This Skill Is Not For', 'Hard Rules > Matching Discipline', Step 5, and 'What This Skill Should Not Do'; source-population, biomarker-timing, and OR-vs-RR rules similarly recur, and 'Quality Standard' mostly restates earlier content. It matches the score-3 anchor (mostly efficient but could be tightened) rather than score 2, since the bulk is genuinely skill-specific guidance rather than filler or explanations of things Claude already knows.

3 / 5

Actionability

As an instruction-only skill, it provides concrete, executable guidance: a 10-step execution logic with explicit decision options at each step, a 12-section mandatory output structure, and defined input-extraction and non-fabrication rules. It matches the score-4 anchor (mostly executable guidance with concrete specifics, minor gaps) — it stops short of score 5 because it offers no worked example of the required output sections or tables.

4 / 5

Workflow Clarity

The 10-step sequence is clear and ordered, with a design-fit gate in Steps 1–2 ('If the user's actual goal is not well served by a case-control design, say so clearly'), an input-validation pass before output, and a Quality Standard checklist. This matches the score-4 anchor (clear sequence, most checkpoints present, minor validation gaps); it lacks the explicit validate-output-then-revise feedback loop of the score-5 anchor.

4 / 5

Progressive Disclosure

Five real, one-level-deep reference files are clearly signaled, each with a 'Use to...' purpose line and mandated as active reading, and the paths verified to exist. It sits at the score-4 anchor rather than 5 because the body is not a lean overview: it inlines substantial material duplicated in the references — notably 'Hard Rules' and 'Formatting Expectations' overlap heavily with references/05_output-style-and-hard-rules.md, and matching/exposure rules overlap reference 03.

4 / 5

Total

15

/

20

Passed

Description

71%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.

The description is specific, domain-grounded, and clearly distinguishes the skill's purpose, but it omits any 'Use when...' trigger clause, which caps its completeness and leaves a few natural synonyms uncovered. Adding explicit trigger guidance would move it into the top tier.

Suggestions

Append an explicit trigger clause, e.g., 'Use when the user asks to design or structure a case-control study, choose controls, plan matching, or lay out bias controls for a retrospective outcome study.'

Include natural synonyms users would actually say — 'retrospective study', 'study design', 'controls', 'epidemiology', 'risk factors' — to broaden trigger coverage.

Optionally name the audience/setting (clinical or translational research) to further reduce overlap with sibling epidemiology-design skills.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete actions — 'explicit source population logic, control selection rules, matching decisions, exposure measurement planning, and bias-control checkpoints' — giving comprehensive coverage of the skill's capabilities. It matches the score-5 anchor (multiple specific concrete actions, comprehensive coverage); the score-4 anchor would imply notable gaps in coverage, which is not the case here.

5 / 5

Completeness

The 'what' is clearly and concretely answered ('Design a structured case-control study framework with...'), but there is no 'Use when...' clause or any equivalent explicit trigger guidance in the description. Per the rubric guideline, a missing 'Use when...' clause caps completeness at 3 even with a clear 'what'.

3 / 5

Trigger Term Quality

Terms like 'case-control study', 'control selection', 'matching', 'exposure measurement', and 'bias-control' are natural phrases a clinical researcher would say, so keyword coverage is good. However, common variations are missing — e.g., 'retrospective study', 'study design', 'epidemiology', 'controls', or 'risk factors' — matching the score-4 anchor (good coverage, a few natural terms missing) rather than the comprehensive synonym coverage of score 5.

4 / 5

Distinctiveness Conflict Risk

'Case-control study' carves out a clear niche with distinct triggers, so wrong-skill triggering is unlikely in general use. It sits at the score-4 anchor (mostly distinct, minor overlap risk with closely related skills) because sibling skills in the same epidemiology/design family (e.g., a cohort study planner or general protocol-writing skill) could plausibly compete for similar queries.

4 / 5

Total

16

/

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/case-control-study-planner/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.