CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tooluniverse-rare-disease-diagnosis

Rare disease differential diagnosis from patient phenotype — HPO term matching to candidate diseases (Orphanet, OMIM), gene panel prioritization, ACMG variant interpretation, and structure-based variant analysis. Use for diagnostic odyssey assistance, phenotype-to-disease ranking, and genetic-counseling differential generation.

Quality

84%

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

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.

The body is an efficient, highly actionable phase-based workflow with exact tool calls, parameter corrections, fallback chains, and scoring thresholds. Its main defects are three dead references in the Reference Files section (the per-phase code examples and report template do not exist in the bundle) and a few phases that name tools without call syntax.

Suggestions

Create the missing DIAGNOSTIC_WORKFLOW.md, REPORT_TEMPLATE.md, and CHECKLIST.md files (or remove/correct the Reference Files links) so the referenced per-phase code examples, report template, and completeness checklist are actually reachable.

Give Phases 5–6 the same treatment as Phases 2–4: one concrete example call each (e.g., AlphaFold2/InterPro and PubMed/OpenAlex syntax) instead of bare tool names.

Add one explicit validation checkpoint between phases (e.g., "confirm ClinGen classification before adding a gene to the panel; if Disputed/Refuted, exclude and record") to make the existing implicit gates into stated steps.

DimensionReasoningScore

Conciseness

The body is dense and table-driven with no explanations of concepts Claude already knows, and every workflow line carries operational content. However, the PanelApp section includes justification prose ("a genuinely different signal from MARRVEL/ClinGen's disease-gene curation, since it reflects what a real diagnostic lab panel would include today") and rationale sentences that could be tightened to bullets — minor instances of over-explanation, matching the level-4 anchor rather than level 5's every-token-earns-its-place.

4 / 5

Actionability

Concrete, executable guidance dominates: a parameter-corrections table with exact WRONG/CORRECT values, specific calls like `Orphanet_search_diseases(operation="search_diseases", query=keyword)` and `FAVOR_annotate_variant("chr-pos-ref-alt")` with expected outputs (panel id 285), plus exact thresholds (gnomAD frequency classes, ACMG codes, overlap-score bands). Minor gaps remain: Phases 5–6 list only tool names ("AlphaFold2, InterPro domains", "PubMed, BioRxiv/MedRxiv, OpenAlex") without call syntax, keeping it at level 4 rather than fully copy-paste-ready level 5.

4 / 5

Workflow Clarity

The Phase 0–7 sequence is explicit and ordered, with fallback chains for tool failure, evidence-grading tiers, and ClinGen confidence gates that function as decision checkpoints. This is an analysis workflow (not destructive/batch), so the validation cap doesn't apply; it sits at level 4 because explicit validate-then-proceed checkpoints between phases are implicit rather than stated, and the completeness checklist (CHECKLIST.md) that would serve as the final checkpoint is a dead reference.

4 / 5

Progressive Disclosure

The body is well structured with clear section headers and a clearly signaled Reference Files list, but scored against the actual bundle, 3 of the 4 referenced files (DIAGNOSTIC_WORKFLOW.md, REPORT_TEMPLATE.md, CHECKLIST.md) do not exist — only scripts/clinical_patterns.py is present. The promised per-phase code examples and report template are unreachable, so navigation breaks where it matters. This lands at level 3 (structure present, but the reference organization fails to deliver) rather than level 2, since nothing is buried or inlined — the content is simply missing.

3 / 5

Total

15

/

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: concrete capabilities with named databases, an explicit "Use for..." trigger clause in third-person voice, and a well-defined niche. The only weakness is keyword coverage that favors technical jargon over a few natural user phrases like "exome" or "undiagnosed disease".

DimensionReasoningScore

Specificity

The description lists multiple specific concrete actions — "HPO term matching to candidate diseases (Orphanet, OMIM)", "gene panel prioritization", "ACMG variant interpretation", and "structure-based variant analysis" — comprehensively covering the skill's capabilities with named databases. It exceeds the level-4 anchor (which permits minor coverage gaps) and matches the level-5 comprehensive anchor; voice is third person throughout, so no penalty applies.

5 / 5

Completeness

It explicitly answers both questions: the what is fully concrete (HPO matching, gene panel prioritization, ACMG interpretation, structure-based analysis), and the when is an explicit trigger clause — "Use for diagnostic odyssey assistance, phenotype-to-disease ranking, and genetic-counseling differential generation". This matches the level-5 anchor exactly; level 4 would require a weaker or less specific when-clause.

5 / 5

Trigger Term Quality

Natural phrases a user in this domain would say are present — "rare disease", "differential diagnosis", "diagnostic odyssey", "genetic-counseling", "phenotype-to-disease ranking" — but a few natural terms are missing (e.g., "exome", "VUS", "undiagnosed disease", "genetic test results"), and the keyword set leans technical (HPO, ACMG, OMIM). This fits the level-4 anchor ("good keyword coverage; a few natural terms missing") rather than level 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

A clear niche (rare-disease genomics) is staked out with named resources (Orphanet, OMIM, HPO) and distinct trigger scenarios, so it would not fire for unrelated bioinformatics or general clinical skills. It matches the level-5 anchor ("clear niche with distinct triggers; minimal conflict risk").

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

relative_links

Relative link issues: 3 missing

Warning

Total

15

/

16

Passed

Repository

mims-harvard/ToolUniverse

Path

plugins/tooluniverse/skills/tooluniverse-rare-disease-diagnosis/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.