CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

epidemiology

Performs epidemiological analyses including disease modeling (SIR/SEIR), outbreak investigation, risk factor identification, incidence/prevalence estimation, and causal inference from observational data; trigger when users discuss disease spread, public health data, or populat...

Quality

79%

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 ./scientific-skills/Data Analysis/epidemiology/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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-organized, lean instruction-only skill with a genuinely concrete seven-step methodology, specific statistical method mappings, a validation checklist, and honest error handling. The main gaps are minor: no worked example or executable snippet anywhere, validation as a post-hoc checklist rather than inline checkpoints, and a redundant Input Validation section duplicating Error Handling.

Suggestions

Add one short worked example (e.g., a minimal R0-from-growth-rate or epidemic-curve snippet) so the most technical steps are executable rather than directional.

Fold the "Input Validation" section into "Error Handling" to remove the duplicated stop-on-missing-input guidance.

Fix the "Hills criteria" typo (should be "Hill's criteria for causation") and consider promoting the Quality Checklist items into inline checkpoints at the relevant methodology steps.

DimensionReasoningScore

Conciseness

The 65-line body is efficient and imperative ("Compute incidence rate (person-time denominator)", "draw a DAG to identify confounders and colliders") with no padding or explanation of concepts Claude already knows. It stays at 4 rather than 5 because the "Input Validation" section largely restates "Error Handling" (both tell the model to stop on missing inputs/out-of-scope requests) and the canned refusal quote is template boilerplate that could be trimmed.

4 / 5

Actionability

Concrete method-to-data mappings appear throughout: "logistic for OR, Poisson/negative binomial for rates, Cox for time-to-event", "incidence rate (person-time denominator)", "Estimate R0 from early epidemic growth rate or next-generation matrix", plus named tools (EpiEstim, DAGitty). Per the code_vs_instruction note the absence of code is not itself penalized, but it stays at 4 rather than 5 because several steps remain directional ("Apply propensity score methods if needed", "Translate findings into public health actions") with no worked example, formula, or command, and 3 would undervalue how specific the method selection guidance is.

4 / 5

Workflow Clarity

The seven numbered steps give a clear, correctly sequenced methodology (question → data → descriptive → measures → analytic → modeling → communication), and the Quality Checklist supplies validation checkpoints ("Confidence intervals provided for all estimates", "Confounders identified via DAG and adjusted for"). This is analysis work, not destructive/batch operations, so the workflow-clarity cap does not apply; it falls short of 5 only because validation lives in a separate end-of-work checklist rather than inline checkpoints with explicit fix-and-retry loops between steps.

4 / 5

Progressive Disclosure

The body is cleanly sectioned (When to Trigger, Methodology, Databases, Output Format, Checklist, Error Handling) with no buried references and no nested files — the bundle directories (references/, scripts/, assets/) don't exist, so nothing dangles. It scores 4 rather than 5 because at 65 lines it exceeds the under-50-line simple-skill threshold and is entirely monolithic — all guidance is inline (e.g., the databases list) with nothing split out — yet it is well above 3 since no content is misplaced or hard to navigate.

4 / 5

Total

16

/

20

Passed

Description

76%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, specific, third-person description with comprehensive capability enumeration and a distinct epidemiological niche. Its one real defect is that the trigger clause is truncated mid-word ("populat..."), which both weakens the when-guidance and leaves the natural-keyword list short of common synonyms.

Suggestions

Fix the truncated trigger clause — complete the cut-off phrase (e.g., "population health") and finish the sentence so the 'when to use' guidance is intact.

Add natural trigger synonyms users actually say — "epidemic", "pandemic", "outbreak", "surveillance data" — to the when-clause.

Keep the description within typical frontmatter limits by trimming the capability list slightly (e.g., merging "risk factor identification" into the causal-inference phrase) so future edits don't re-truncate.

DimensionReasoningScore

Specificity

The description lists five concrete capabilities: "disease modeling (SIR/SEIR), outbreak investigation, risk factor identification, incidence/prevalence estimation, and causal inference from observational data" — comprehensive coverage of the domain in third-person voice ("Performs"). It matches the 5 anchor (multiple specific concrete actions) and not 4, because no meaningful capability of the epidemiology domain is left out of the enumeration.

5 / 5

Completeness

Both "what" (the five listed capabilities) and "when" ("trigger when users discuss...") are explicitly present, satisfying the 4 anchor. It does not reach 5 because the when-clause is cut off mid-word ("populat..."), so the trigger guidance is present but incomplete rather than "clearly and explicitly" fully specified.

4 / 5

Trigger Term Quality

The trigger clause "trigger when users discuss disease spread, public health data, or populat..." is truncated mid-word, leaving only two complete natural trigger phrases. Common variations users would actually say ("epidemic", "pandemic", "surveillance") are absent, matching the 3 anchor (some relevant keywords, missing common variations) rather than 4, whose keyword coverage is complete with only a few gaps.

3 / 5

Distinctiveness Conflict Risk

Terms like "SIR/SEIR", "outbreak investigation", and "public health data" carve out a clear epidemiology niche with minimal overlap with generic data-analysis or statistics skills. It sits at 5 rather than 4 because the triggers are domain-unique and would not plausibly fire a neighboring skill (only "causal inference from observational data" mildly touches statistics territory).

5 / 5

Total

17

/

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

scientific-skills/Data Analysis/epidemiology/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.