CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

69

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 dense, expert-level instruction body with excellent token efficiency, concrete tool calls, and a clearly sequenced multi-phase workflow with fallback chains. Its main defects are missing mid-workflow validation checkpoints and a 'Reference Files' section where three of the four listed files are absent from the bundle, undermining the progressive-disclosure structure.

Suggestions

Ship the three referenced files (DIAGNOSTIC_WORKFLOW.md, REPORT_TEMPLATE.md, CHECKLIST.md) in the bundle or remove/inline those references — currently only scripts/clinical_patterns.py exists, so the Reference Files section contains three dangling links.

Add explicit validation checkpoints between phases, e.g., 'confirm each symptom resolved to a valid HPO term before Phase 2' and 'verify MARRVEL_get_gene resolved all IDs before gene-panel scoring'.

Include one complete end-to-end example (exact tool calls in order for a sample phenotype) either inline or in the workflow reference file, so the most common path is fully executable without improvisation.

DimensionReasoningScore

Conciseness

The body is lean and information-dense: terse tables for parameter corrections, evidence tiers, and fallback chains; no space spent explaining what HPO, OMIM, or ACMG are; every section carries skill-specific values (scoring tiers, frequency thresholds, tool quirks). It matches the level-5 'lean and efficient; assumes Claude's competence' anchor, with only a one-line intro that loosely restates the frontmatter — not enough to drop to level 4's 'minor instances of over-explanation'.

5 / 5

Actionability

Highly concrete guidance: exact call signatures like 'Orphanet_search_diseases(operation="search_diseases", query=keyword)', 'FAVOR_annotate_variant("chr-pos-ref-alt") (GRCh38)', a WRONG/CORRECT parameter table, numeric scoring tiers, and ACMG criteria mappings. It sits at level 4 rather than 5 because several tools (HPO_search_terms, CELLxGENE, GTEx) are named without call syntax, and the promised 'code examples and algorithms per phase' are deferred to the DIAGNOSTIC_WORKFLOW.md reference rather than shown — leaving minor gaps in copy-paste readiness.

4 / 5

Workflow Clarity

The Phase 0–7 sequence is explicit and well-ordered, with key phase details, evidence-grading gates, and fallback chains that function as error-recovery loops (primary → fallback 1 → fallback 2). It falls short of the level-5 anchor because explicit mid-workflow validation checkpoints are missing — e.g., no step to verify HPO term conversion output before disease matching, or to confirm MARRVEL ID resolution before gene scoring — though this diagnostic (read-only) skill avoids the destructive/batch cap.

4 / 5

Progressive Disclosure

The in-body structure is good with a clearly signaled 'Reference Files' section, but scoring against the actual bundle reveals that three of the four referenced files — DIAGNOSTIC_WORKFLOW.md, REPORT_TEMPLATE.md, and CHECKLIST.md — do not exist anywhere in the bundle (only scripts/clinical_patterns.py is present). Dangling references break navigation and leave the promised detailed material absent, which fits level 3 ('references present but' the organization is undermined) better than level 4's 'references mostly clear; minor organization gaps' — the gap here is missing files, not just organization.

3 / 5

Total

16

/

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: third-person voice, concrete capability list, and an explicit 'Use for...' trigger clause with realistic scenarios. The only weakness is that a few natural user phrasings (e.g., 'undiagnosed disease', 'suspected genetic disorder') are missing while some trigger wording leans technical.

DimensionReasoningScore

Specificity

The description lists multiple concrete, specific actions — 'HPO term matching to candidate diseases (Orphanet, OMIM)', 'gene panel prioritization', 'ACMG variant interpretation', and 'structure-based variant analysis' — comprehensively covering the diagnostic pipeline. This matches the level-5 anchor ('lists multiple specific concrete actions; comprehensive coverage') and exceeds level 4 because coverage of the workflow stages is complete rather than having minor gaps.

5 / 5

Completeness

It explicitly answers both questions: 'what' is the opening clause ('Rare disease differential diagnosis from patient phenotype — HPO term matching... variant analysis') and 'when' is an explicit 'Use for...' clause with three concrete trigger scenarios ('diagnostic odyssey assistance, phenotype-to-disease ranking, and genetic-counseling differential generation'). This is a direct match to the level-5 anchor and avoids the level-3 cap since the 'when' guidance is explicit, not implied.

5 / 5

Trigger Term Quality

Good natural keyword coverage: 'rare disease', 'differential diagnosis', 'diagnostic odyssey assistance', 'genetic-counseling differential generation' are phrases clinicians and users would plausibly say. It falls short of the level-5 'comprehensive coverage including synonyms' anchor because common variations like 'undiagnosed disease', 'suspected genetic disorder', or 'syndrome evaluation' are absent, while 'phenotype-to-disease ranking' is more technical than natural.

4 / 5

Distinctiveness Conflict Risk

The rare-disease/gene-diagnostics niche is highly distinct with domain-specific triggers (HPO, Orphanet, OMIM, ACMG) that no general medical or literature skill would claim, matching the level-5 'clear niche with distinct triggers; minimal conflict risk' anchor. It is clearly above level 4 because the specialized vocabulary makes overlap with adjacent skills very unlikely.

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