CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tooluniverse-disease-research

Generate comprehensive disease research reports covering genetics (causal genes, GWAS, OMIM), pathways (Reactome, KEGG), drugs (existing therapies, repurposing candidates), clinical trials, epidemiology (prevalence, incidence), and phenotypes (HPO). Use for full disease overviews, comprehensive disease characterization, and orphan/rare-disease profiling.

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/tooluniverse/skills/tooluniverse-disease-research/SKILL.md

The canonical home for this skill is tooluniverse-disease-research in mims-harvard/ToolUniverse

SKILL.md
Quality
Evals
Security

Quality

Content

63%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 well-organized instruction skill with a clear workflow, strong evidence-grading guidance, and one genuinely executable code example, but it is held back by a duplicated inline template, a pseudocode update pattern, and a references section pointing at files that are missing from the bundle.

Suggestions

Include the five referenced bundle files (REPORT_TEMPLATE.md, RESEARCH_PROTOCOL.md, tool_usage_details.md, TOOLS_REFERENCE.md, EXAMPLES.md) in the skill bundle — currently the links point at files that do not exist — and place them under references/ with matching relative paths.

Remove the ~70-line inline report template (or reduce it to a skeleton) since it duplicates REPORT_TEMPLATE.md, keeping the detailed version only in the referenced file.

Replace the comment-only "Progressive Update Pattern" code block with an actual executable snippet (read file, replace section, write back) or move it into RESEARCH_PROTOCOL.md with concrete code.

DimensionReasoningScore

Conciseness

Dense, useful tables (dimensions, evidence grading, conflict handling), but the ~70-line report template is inlined even though REPORT_TEMPLATE.md is supposedly available, the "Disease Mechanism Reasoning" section spells out a causal cascade Claude can reason through itself, and the "Progressive Update Pattern" block is four comment lines. Mostly efficient but could be tightened — matching the anchor-3 example's profile.

3 / 5

Actionability

Fully executable ZOOMA examples with real parameters and expected outputs, a concrete cross-skill command, and explicit per-context citation formats. Not 5 because most dimension tool calls are only named (deferred to tool_usage_details.md) and the core "Progressive Update Pattern" is comment-only pseudocode.

4 / 5

Workflow Clarity

Clear create-research-update-cite sequence plus an end-of-run quality checklist that verifies sections, citations, and leftover placeholders. Not 5 because there are no explicit per-step validation or error-recovery loops (e.g., what to do when a tool call fails or returns nothing).

4 / 5

Progressive Disclosure

The "Reference Files" section is well signaled and one level deep, but none of the five referenced files (REPORT_TEMPLATE.md, RESEARCH_PROTOCOL.md, tool_usage_details.md, TOOLS_REFERENCE.md, EXAMPLES.md) exist in the bundle, and the report template that should live in a separate file is inlined instead. Structure and signaling are present but the actual bundle does not support the claimed structure.

3 / 5

Total

14

/

20

Passed

Description

88%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, source-annotated capabilities paired with an explicit "Use for..." trigger clause. Its main gaps are a few missing natural user phrasings (e.g., "what do we know about X") and slight overlap risk with sibling biomedical skills.

DimensionReasoningScore

Specificity

Multiple specific concrete actions with named data sources — "causal genes, GWAS, OMIM", "Reactome, KEGG", "repurposing candidates", "prevalence, incidence", "phenotypes (HPO)" — give comprehensive coverage of the skill's outputs.

5 / 5

Completeness

Clearly answers both "what" (generate reports covering genetics, pathways, drugs, trials, epidemiology, phenotypes) and "when" ("Use for full disease overviews, comprehensive disease characterization, and orphan/rare-disease profiling") with concrete trigger phrases. Not 4 because the "when" clause is already explicit and specific, not merely present.

5 / 5

Trigger Term Quality

Good natural keywords ("disease research reports", "full disease overviews", "orphan/rare-disease profiling") but common user phrasings like "what do we know about [disease]", "syndrome", or "medical condition" are absent. Not 5 because anchor-level synonym/variation coverage is not reached.

4 / 5

Distinctiveness Conflict Risk

A clear disease-research-report niche with distinct triggers, but the broad "any disease" scope overlaps general biomedical Q&A and a companion rare-disease-diagnosis skill. Not 5 because minor overlap risk remains with closely related disease skills.

4 / 5

Total

18

/

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: 5 missing

Warning

Total

15

/

16

Passed

Repository

mims-harvard/ToolUniverse

Path

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