CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ebm-calculator

Evidence-Based Medicine diagnostic test calculator. Computes sensitivity, specificity, PPV, NPV, likelihood ratios, NNT, and pre/post-test probability.

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 ./scientific-skills/Other/ebm-calculator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

62%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 operational core is strong: a clear, validated 7-step workflow, concrete commands, and a complete parameter reference. However, roughly half the body is generic boilerplate (risk tables, security checklists, evaluation criteria, lifecycle metadata, response templates) that wastes context, the reference file is never linked, and there is no worked example.

Suggestions

Remove or drastically trim the generic boilerplate sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status, Output Requirements, Response Template) that add no EBM-specific guidance Claude doesn't already know.

Add one fully worked example invocation with real numbers, e.g. "python scripts/main.py --mode diagnostic --tp 90 --fn 10 --tn 80 --fp 20" with its expected JSON output.

Link the existing bundle reference, e.g. "**Formulas and methodology**: See [guidelines.md](references/guidelines.md)", so the provided reference file is discoverable.

DimensionReasoningScore

Conciseness

Several padded boilerplate sections add no EBM-specific value: the "Risk Assessment" table, the generic "Security Checklist", "Evaluation Criteria" with placeholder test cases ("Standard input → Expected output"), "Lifecycle Status" including a time-sensitive date ("Next Review Date: 2026-03-06"), and the generic "Response Template". This is noticeably verbose (anchor 2), not mostly efficient (anchor 3).

2 / 5

Actionability

Concrete, executable commands are provided ("python -m py_compile scripts/main.py", "python scripts/main.py --help") plus a complete CLI parameter table and a concrete JSON output shape. Minor gaps keep it below 5: no worked invocation with real numbers, and the Output Format uses "float"/"string" placeholders instead of an example result.

4 / 5

Workflow Clarity

The Workflow is a clear seven-step sequence with explicit input validation ("Check that all counts are non-negative integers, rates are between 0 and 1, and denominators are not zero. If invalid, report exact error and stop"), a confirmation checkpoint before computing, and a fallback template for missing parameters, plus a dedicated Error Handling section. Matches anchor 5: explicit validation steps and feedback loops for error recovery.

5 / 5

Progressive Disclosure

The body is well-sectioned and correctly references scripts/main.py, but the bundle's references/guidelines.md is never linked or signaled anywhere in the body, so a provided reference file is orphaned. Boilerplate that adds no operational value is inlined in SKILL.md. Structure exists but organization could be better (anchor 3).

3 / 5

Total

14

/

20

Passed

Description

75%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 description with excellent concrete capability coverage and a distinct niche, undermined only by the complete absence of a "Use when..." trigger clause, which caps completeness and slightly limits trigger-term quality.

Suggestions

Append a trigger clause such as: "Use when the user asks to calculate sensitivity, diagnostic accuracy, likelihood ratios, NNT, or convert pre/post-test probability."

Add natural synonyms users would say ("EBM", "diagnostic accuracy", "test characteristics") to the description or trigger clause.

DimensionReasoningScore

Specificity

"Computes sensitivity, specificity, PPV, NPV, likelihood ratios, NNT, and pre/post-test probability" lists multiple specific concrete actions with comprehensive coverage of the calculator's feature set. Anchor 5 fits; not 4, since there are no coverage gaps.

5 / 5

Completeness

The "what" is clear and comprehensive, but there is no "Use when..." clause or equivalent explicit trigger guidance anywhere in the description, which caps completeness at 3 per the judging guidelines. Not 4, since the "when" is entirely absent rather than merely under-specified.

3 / 5

Trigger Term Quality

Good natural keyword coverage ("sensitivity", "PPV", "likelihood ratios", "diagnostic test", "Evidence-Based Medicine") but common variations users would actually say ("diagnostic accuracy", "EBM", "test characteristics") are missing. Fits anchor 4 better than 3 (coverage is strong, not just "some relevant keywords").

4 / 5

Distinctiveness Conflict Risk

A clear niche (EBM diagnostic test statistics) with distinct, domain-specific triggers; minimal overlap risk with other skills. Anchor 5 fits; the named metrics are unlikely to trigger the wrong skill.

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/Other/ebm-calculator/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.