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

83%

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 a well-structured, largely executable playbook with a clear report-first workflow, concrete tooling, evidence grading, and a quality checklist. Its main weaknesses are structural: every referenced bundle file is missing from the package, and the report template is duplicated inline instead of being offloaded to the reference file that claims to contain it.

Suggestions

Ship the referenced files (REPORT_TEMPLATE.md, RESEARCH_PROTOCOL.md, tool_usage_details.md, TOOLS_REFERENCE.md, EXAMPLES.md) in the bundle alongside SKILL.md — five of five links currently dead-end, breaking progressive disclosure navigation.

Move the full report template out of SKILL.md into REPORT_TEMPLATE.md (which already claims to hold it), keeping only the 10-section skeleton and citation format inline to cut ~70 duplicated lines.

Replace the commented pseudocode in the 'Progressive Update Pattern' with an executable read-modify-write snippet, and add a brief error-recovery step for tool calls that fail or return empty results.

DimensionReasoningScore

Conciseness

The body is dense and task-specific — the dimension-to-tool table, evidence-grading table, and conflict-resolution table carry no general-knowledge padding. It is not anchor 5 because the ~70-line inline report template duplicates the referenced REPORT_TEMPLATE.md and the 'Expected Output Scale' section could be trimmed, matching anchor 4's 'minor instances that could be trimmed'.

4 / 5

Actionability

Concrete guidance dominates: an executable ZOOMA python block with real parameters and expected output, an executable cross-skill command, a copy-ready report scaffold, and a per-dimension tool mapping. Not anchor 5 because the 'Progressive Update Pattern' is commented pseudocode and the core loop ('Research each dimension - Use all relevant tools') defers the actual calls to tool_usage_details.md.

4 / 5

Workflow Clarity

The report-first sequence (create file → research each dimension → update progressively → cite) is clearly ordered, reinforced by a mechanism-reasoning cascade, mandatory synthesis questions, and a final quality checklist that serves as an explicit checkpoint. Not anchor 5: there is no error-recovery feedback loop (e.g., what to do when a tool call fails or returns no data).

4 / 5

Progressive Disclosure

The 'Reference Files' section lists five well-labeled, one-level-deep links, but none of the referenced files (REPORT_TEMPLATE.md, RESEARCH_PROTOCOL.md, tool_usage_details.md, TOOLS_REFERENCE.md, EXAMPLES.md) exist in the bundle, so navigation dead-ends. The full report template is inlined in SKILL.md even though REPORT_TEMPLATE.md is supposed to hold it — content that should be separate is inline, matching anchor 3 rather than anchor 4's 'minor organization gaps'.

3 / 5

Total

15

/

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: it states concretely what the skill produces, names the six research dimensions with specific data sources, and gives an explicit 'Use for…' trigger clause. The only weakness is incomplete natural-term coverage for how users ask about diseases.

DimensionReasoningScore

Specificity

The description enumerates six concrete coverage areas — 'genetics (causal genes, GWAS, OMIM), pathways (Reactome, KEGG), drugs (existing therapies, repurposing candidates), clinical trials, epidemiology (prevalence, incidence), and phenotypes (HPO)' — each grounded in named data sources. This matches the 'lists multiple specific concrete actions; comprehensive coverage' anchor and exceeds anchor 4, which tolerates coverage gaps.

5 / 5

Completeness

It explicitly answers both questions: the 'what' is 'Generate comprehensive disease research reports covering genetics…phenotypes (HPO)' and the 'when' is the explicit trigger clause 'Use for full disease overviews, comprehensive disease characterization, and orphan/rare-disease profiling' with concrete use cases. Not anchor 4, since the 'when' is specific and multi-triggered rather than improvable.

5 / 5

Trigger Term Quality

Natural phrases like 'disease overviews', 'comprehensive disease characterization', and 'orphan/rare-disease profiling' cover the main ways a user would express this need. It falls short of anchor 5's comprehensive synonym coverage — common variations like 'medical condition', 'syndrome', or 'what do we know about [disease]' are absent.

4 / 5

Distinctiveness Conflict Risk

The biomedical-research niche with database-level identifiers (OMIM, GWAS, Reactome, HPO) is mostly distinct, but 'disease' is broad and could overlap with related bioinformatics skills — the body itself cross-references a rare-disease-diagnosis skill covering adjacent ground. Minor overlap risk, matching anchor 4.

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

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