CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tooluniverse-kegg-disease-drug

KEGG-based disease-drug-variant network research. Connects diseases to causal genes, drugs to molecular targets, and variants to pathways using KEGG's editorially curated databases (KEGG Disease, Drug, Network, Variant, Pathway). Use for drug repurposing via shared pathways, mechanistic disease-gene-drug networks, and pathway-based target discovery. Distinguishes direct (binding) vs indirect (pathway co-membership) drug-target relationships.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

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

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.

Highly actionable content with a clear five-phase workflow, concrete tool documentation, and executable examples throughout. The main weaknesses are repeated caveats that inflate token cost and a monolithic structure that inlines interpretation guidance which would be better split into a reference file.

Suggestions

Consolidate the direct-vs-indirect drug-target distinction into a single statement (Reasoning Strategy) and drop the repetitions in the network interpretation bullet and Evidence Grading table; likewise state the hsa-ID namespace caveat and the KEGG-coverage limitation once each.

Move the Evidence Grading table and Interpretation Guidance bullets into a references/ file (e.g., references/interpretation.md), keeping a two-line pointer in SKILL.md so the main file stays a lean overview.

Add a short fallback step at the end of the workflow (e.g., "If a phase returns no entries, verify the ID via KEGG_search_* before concluding KEGG lacks coverage") to make the existing implicit error handling an explicit validate-and-retry loop.

DimensionReasoningScore

Conciseness

The body is mostly efficient (lean tool table, terse code blocks), but the same guidance is repeated: the direct-vs-indirect drug-target distinction appears three times (Reasoning Strategy, network interpretation, Evidence Grading), and both the hsa-ID namespace caveat and "KEGG coverage is not exhaustive" appear twice. This fits the mostly-efficient-but-could-be-tightened anchor at 3; it is not so padded as to match the 2 anchor's "several unnecessary explanations".

3 / 5

Actionability

A 12-tool inventory with key params and returns, per-phase copy-paste-ready Python with real identifiers (H00031, D09996, hsa:672), expected result shapes ("result['data'] -> [{...}]"), and a complete worked end-to-end example fully cover the common cases, matching the 5 anchor.

5 / 5

Workflow Clarity

The five phases are clearly sequenced with code for each, backed by a "LOOK UP DON'T GUESS" pre-check, an evidence-grading scheme, and error-path hints ("Failed conversions may indicate the gene is not in KEGG's curated set"). However there is no explicit validate-and-retry loop per phase, so it fits the most-checkpoints-present anchor at 4 rather than the explicit-feedback-loops anchor at 5; the destructive/batch cap at 3 does not apply since these are read-only lookups.

4 / 5

Progressive Disclosure

A single ~190-line file with no bundle: the Evidence Grading table and multi-bullet Interpretation Guidance are reference-grade material that belongs in a separate file, and the skill is well beyond the under-50-line exception. Sections are well organized, but content that should be separate is inline, matching the 3 anchor rather than the 4 anchor's "most content appropriately placed".

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: concrete, third-person capability statements, explicit "Use for" trigger guidance, and a clearly bounded KEGG niche. The only weaknesses are a few missing natural trigger phrasings and some overlap risk with related drug/disease bioinformatics skills on generic terms.

DimensionReasoningScore

Specificity

"Connects diseases to causal genes, drugs to molecular targets, and variants to pathways" and "Distinguishes direct (binding) vs indirect (pathway co-membership) drug-target relationships" list multiple concrete capabilities, matching the comprehensive-coverage anchor rather than the minor-gaps anchor at 4.

5 / 5

Completeness

It explicitly answers "what" ("Connects diseases to causal genes, drugs to molecular targets, and variants to pathways using KEGG's editorially curated databases") and "when" ("Use for drug repurposing via shared pathways, mechanistic disease-gene-drug networks, and pathway-based target discovery") with concrete trigger phrases, matching the 5 anchor exactly.

5 / 5

Trigger Term Quality

"Use for drug repurposing via shared pathways, mechanistic disease-gene-drug networks, and pathway-based target discovery" gives good natural-phrase coverage, but common user phrasings like "which drugs target a gene" or "disease genes" as standalone triggers are missing, so it fits the good-coverage-with-a-few-missing anchor at 4 rather than the comprehensive-synonyms anchor at 5.

4 / 5

Distinctiveness Conflict Risk

The KEGG-specific framing ("KEGG's editorially curated databases (KEGG Disease, Drug, Network, Variant, Pathway)") creates a clear niche, but generic triggers like "drug repurposing" and "target discovery" risk overlap with sibling bioinformatics skills such as drug-mechanism or systems-biology skills, fitting the minor-overlap anchor at 4 rather than minimal-conflict at 5.

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

mims-harvard/ToolUniverse

Path

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