CtrlK
BlogDocsLog inGet started
Tessl Logo

tooluniverse-epidemiological-analysis

End-to-end observational epidemiology analysis — from research question (PECO Population/Exposure/Comparator/Outcome) to publication-ready statistical report. Covers cohort/case-control/cross-sectional design, regression with confounders, propensity scoring, sensitivity analysis. Writes Python code for every step. Use for epidemiology study analysis, NHANES/UK-Biobank-style analyses.

77

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

92%

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

A highly actionable, well-sequenced epidemiology workflow with executable code, validation steps, and a checklist; its only weakness is that all material lives in a single SKILL.md with no progressive disclosure into bundle files.

Suggestions

Move the reusable code templates (download_and_parse, sample_size_logistic, the sequential-adjustment regression block) into scripts/ files and reference them one level deep, keeping SKILL.md as an overview.

Extract the detailed model-selection-by-outcome and assumption-check guidance into a references/ file (e.g. STATISTICAL_METHODS.md) linked from Step 5, reducing inline density.

Add a short 'References' section near the top signaling the bundle files so navigation is explicit rather than implicit.

DimensionReasoningScore

Conciseness

The body is dense and directive — almost every section leads with executable Python and brief, non-padded context ('Never describe what you "would do" — do it'), avoiding re-explaining concepts Claude already knows.

3 / 3

Actionability

It provides copy-paste-ready, executable code throughout (data loading, regression, stratification, VIF, power analysis), with placeholder variables explicitly justified as adaptable ('adapt to your variables'), not pseudocode.

3 / 3

Workflow Clarity

Nine steps are clearly sequenced with validation checkpoints (power analysis before dataset commitment, VIF/assumption checks, try/except in stratified runs) and capped by an explicit completeness checklist.

3 / 3

Progressive Disclosure

Content is well-organized into sections but entirely monolithic — no bundle files exist and nothing is split into references/scripts, so ~260 lines of templates and code live inline where separation would aid discovery.

2 / 3

Total

11

/

12

Passed

Description

100%

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 that clearly states capabilities, includes an explicit 'Use for' trigger, and occupies a distinctive niche. No meaningful gaps relative to the rubric anchors.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions: 'regression with confounders, propensity scoring, sensitivity analysis' and 'Writes Python code for every step', spanning several specific analytical techniques rather than vague language.

3 / 3

Completeness

It answers both 'what' (end-to-end analysis from PECO to report, named designs and methods) and 'when' via the explicit trigger clause 'Use for epidemiology study analysis, NHANES/UK-Biobank-style analyses.'

3 / 3

Trigger Term Quality

It surfaces natural terms a user would actually say — 'epidemiology study analysis', 'NHANES/UK-Biobank-style analyses' — alongside the domain-defining PECO phrasing, giving good keyword coverage.

3 / 3

Distinctiveness Conflict Risk

The observational-epidemiology niche with PECO and NHANES/UK-Biobank triggers is highly specific and unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
mims-harvard/ToolUniverse
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.