CtrlK
BlogDocsLog inGet started
Tessl Logo

tooluniverse-pathway-disease-genetics

Connect GWAS variants to biological pathways and druggable targets. Maps GWAS hits to causal genes (via fine-mapping/eQTL), then to pathways (Reactome, KEGG, WikiPathways), then to existing drugs hitting those pathways. Use for pathway-level disease mechanisms, druggable-pathway prioritization from GWAS, SNP-to-pathway-to-target tracing, and tissue-specific eQTL evidence for drug target hypotheses.

72

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 high-quality, actionable skill body with precise tool-call guidance and a clear three-step workflow. The main gaps are implicit (rather than explicit) validation checkpoints and a few sentences that could be tightened for token efficiency.

Suggestions

Add explicit validation/feedback checkpoints in the workflow (e.g., 'If GTEx returns no eQTL, fall back to positional mapping and flag as Low evidence') to strengthen workflow_clarity.

Tighten the 'Core Reasoning Principles' section by merging the narrative paragraphs into terse heuristics, trimming the few sentences that restate the workflow.

If the tool-parameter reference grows further, consider moving the 'Key Parameter Gotchas' list into a reference file and linking it one level deep to improve progressive_disclosure.

DimensionReasoningScore

Conciseness

Efficient overall — exact tool signatures, gotchas, and evidence tiers with no basic-concept padding — but a few reasoning sentences restate what the workflow already implies and could be trimmed.

4 / 5

Actionability

Fully concrete and executable: real tool calls with exact parameter names and values, a dedicated gotchas section, explicit evidence tiers, and a final ranking formula (Genetic Evidence x Druggability x Pathway Centrality).

5 / 5

Workflow Clarity

The three-step workflow is clearly sequenced with evidence-tier checkpoints in Step 1, but validation/feedback loops for tool failures or empty results are only implicit rather than stated as explicit checkpoints.

4 / 5

Progressive Disclosure

Single, well-organized SKILL.md with clear section headers (When to Use, Tool Selection Guide, Three-Step Workflow, Gotchas, Limitations) and no nested references; no bundle files exist, but the inlined structure is appropriately sectioned.

4 / 5

Total

17

/

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, specific description that clearly states both the multi-step capability and concrete use-when triggers, using appropriate third-person voice. Minor room to add lay synonyms alongside the technical jargon for trigger terms.

DimensionReasoningScore

Specificity

Lists a comprehensive, concrete action chain: 'Maps GWAS hits to causal genes (via fine-mapping/eQTL), then to pathways (Reactome, KEGG, WikiPathways), then to existing drugs' — multiple specific actions with named resources.

5 / 5

Completeness

Explicitly answers both what (the maps/connect chain with named databases) and when ('Use for pathway-level disease mechanisms, druggable-pathway prioritization from GWAS, SNP-to-pathway-to-target tracing, and tissue-specific eQTL evidence').

5 / 5

Trigger Term Quality

Includes natural domain terms a user would say ('GWAS', 'pathway', 'eQTL', 'drug target', 'SNP-to-pathway-to-target') but is somewhat jargon-heavy and lacks common synonym variations, so a few natural terms are missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (GWAS→causal gene→pathway→drug target) with specific tool ecosystem and explicit trigger phrases, giving it minimal overlap with sibling ToolUniverse skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.