CtrlK
BlogDocsLog inGet started
Tessl Logo

tooluniverse-rare-disease-genomics

Rare disease genomics — disease identification (Orphanet), causative gene discovery, gene-disease validity (GenCC), variant interpretation (ClinVar), and translational research (ClinicalTrials.gov, drug repurposing for orphans). Use for rare-disease-gene curation, novel-gene-discovery analysis, and rare-disease drug-development support.

67

Quality

81%

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

70%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 a dense, well-sequenced playbook with genuinely valuable tool-specific knowledge (parameter names, gotchas, evidence semantics) and a clear 10-phase workflow with fallbacks and a validation checklist. Its weaknesses are inlined textbook-genetics explanations that pad the token budget, non-executable workflow sketches, and a monolithic structure that should push the per-tool API reference into separate reference files.

Suggestions

Move the per-tool API details (parameters, defaults, aliases) for each phase into references/ files (e.g., references/orphanet-tools.md, references/clinvar-tools.md), keeping SKILL.md as a workflow overview with one-line tool summaries and clear links.

Trim the explanations of knowledge Claude already has — the inheritance-mode definitions, the basic consequence hierarchy, and the long deep-intronic parenthetical — down to one-line pointers on how they change the filtering strategy.

Add one fully executable Python example showing how to call a ToolUniverse tool (e.g., Orphanet_search_diseases) from a Bash-run script, so the 'COMPUTE, DON'T DESCRIBE' directive is backed by a copy-paste template.

DimensionReasoningScore

Conciseness

Mostly efficient — the bulk is genuinely tool-specific knowledge (parameter gotchas like 'name (NOT query)', association-type semantics, GenCC tiers, review-star confidence levels) — but it includes unnecessary explanation of concepts Claude already knows: the four inheritance-mode definitions ('Autosomal dominant: look for heterozygous variants in ONE copy...'), the basic consequence hierarchy, and a long padded parenthetical on deep intronic variants. This is more than the 'minor instances' of the level-4 anchor, so level 3 fits best.

3 / 5

Actionability

Concrete, executable guidance throughout: exact parameter names, defaults, and aliases for ~25 tools, explicit gotchas, and two example workflows with real call signatures like Orphanet_search_diseases(name="Marfan syndrome"). It falls short of the copy-paste-ready level 5 because the workflows are tool-call sketches, not runnable Python — the 'COMPUTE, DON'T DESCRIBE' section instructs running Python via Bash but never shows how to invoke a ToolUniverse tool from code.

4 / 5

Workflow Clarity

The 10 phases (0-9) are clearly sequenced with an explicit ordering rationale ('phenotype -> disease -> gene -> variant, not the reverse'), fallback strategies provide error-recovery loops when tools return nothing, and the Completeness Checklist and evidence-grading tiers act as end-of-workflow validation. No destructive or batch operations apply a cap. This matches the level-5 anchor; level 4 would lack the checklist or fallback loops.

5 / 5

Progressive Disclosure

Structure is present and well-organized (phase headers, examples, mistakes, limitations), but this is a 283-line monolithic SKILL.md with no bundle files — the per-tool API reference (parameters, defaults, aliases for ~25 tools) is inlined in the body when it clearly belongs in references/ files, matching the level-3 anchor 'content that should be separate is inline' rather than level 4's 'most content is appropriately placed'.

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: it names concrete capabilities with specific resources, gives an explicit use-for clause, and occupies a distinct niche. The only weakness is that the natural-language trigger phrases users actually say live in the triggers block rather than the description itself, where hyphenated compounds like 'rare-disease-gene curation' are less natural.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete actions with named resources — 'disease identification (Orphanet), causative gene discovery, gene-disease validity (GenCC), variant interpretation (ClinVar), and translational research (ClinicalTrials.gov, drug repurposing for orphans)' — covering the full workflow comprehensively, which matches the level-5 anchor rather than the minor-gaps level 4.

5 / 5

Completeness

Both 'what' and 'when' are explicitly answered: the what is a detailed multi-capability list, and the when is the explicit clause 'Use for rare-disease-gene curation, novel-gene-discovery analysis, and rare-disease drug-development support', matching the level-5 anchor exactly; level 4 would require the when to be less explicit.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('rare disease', 'rare-disease-gene curation', 'novel-gene-discovery analysis', 'rare-disease drug-development support'), but common user phrasings and synonyms like 'orphan disease', 'HPO', or 'what genes cause' are absent from the description text itself (they only exist in the separate triggers block), so it falls short of the comprehensive-synonym level-5 anchor.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear niche (rare-disease genomics with distinct named resources Orphanet/GenCC/ClinVar) with minimal overlap risk against generic genomics or disease-research skills, matching the level-5 'clear niche with distinct triggers' anchor.

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

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.