CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tooluniverse-multiomic-disease-characterization

Comprehensive disease characterization across genomics, transcriptomics, proteomics, and pathways for systems-level understanding. Identifies therapeutic opportunities and biomarker candidates by integrating multi-layer molecular data. Use for full-omics disease deep-dive reports, mechanism mapping, and biomarker-and-target identification from multi-omics data.

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

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 well-engineered pipeline skill: lean, tool-specific, and clearly sequenced, with genuine progressive disclosure of details to reference files. The main weaknesses are the unverifiable/missing reference files in the bundle, no inline example invocations, and error-recovery loops being deferred entirely to a reference file.

Suggestions

Ship the five referenced files (tool-reference.md, report-template.md, integration-scoring.md, response-formats.md, use-patterns.md) in the skill bundle — SKILL.md currently points to files that are not present, breaking the progressive-disclosure path.

Add one or two complete example tool invocations with literal arguments (e.g., STRING_get_network(identifiers=['APOE'], species=9606)) to make the body's guidance copy-paste ready rather than deferred to tool-reference.md.

Inline a brief fallback loop for the most common failure (tool returns null/empty — e.g., the noted OpenTargets MONDO-vs-EFO ID issue) instead of delegating all error handling to use-patterns.md, so mid-pipeline recovery is visible in the workflow itself.

DimensionReasoningScore

Conciseness

The body is dense and assumes domain competence — no explaining what GWAS, PPI networks, or enrichment are; every line carries tool names, parameter formats, or phase requirements. Not 5 because the conceptual paragraph 'Multi-omics disease characterization asks: what molecular layers are dysregulated?...' is inference Claude could make, and the 13-item KEY PRINCIPLES list partially restates phase content.

4 / 5

Actionability

Highly concrete, executable guidance: exact tool names with exact parameter requirements ('gwas_search_associations (use efo_id...not free-text disease_trait)', 'STRING_get_network (param: identifiers, species=9606)', 'ReactomeAnalysis_pathway_enrichment — identifiers are newline-separated', 'search_clinical_trials: query_term is REQUIRED'). Not 5 because no complete example invocations with literal arguments appear in SKILL.md itself — those are deferred to tool-reference.md and response-formats.md — so the body alone is not fully copy-paste ready.

4 / 5

Workflow Clarity

Nine phases are explicitly sequenced with Phase 0 marked 'ALWAYS FIRST', an ambiguity checkpoint ('If ambiguous, present top 3-5 options and ask user to select'), and Phase 8 report verification backed by a mandated completeness checklist (principle 12). Not 5 because mid-pipeline error-recovery feedback loops (e.g., null/empty tool responses, fallback strategies) are not stated in the body — they are delegated to use-patterns.md — leaving a minor validation gap between the start and end checkpoints.

4 / 5

Progressive Disclosure

Textbook structure: concise overview, critical parameter pitfalls kept inline, and a Reference Files table clearly signaling five one-level-deep files, each with a stated purpose, plus inline pointers like 'See integration-scoring.md for full details'. Not 5 because the five referenced files (tool-reference.md, report-template.md, integration-scoring.md, response-formats.md, use-patterns.md) are not present in the skill bundle alongside SKILL.md, so the navigation points to files that could not be verified to exist.

4 / 5

Total

16

/

20

Passed

Description

83%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: third-person, concrete, with an explicit 'Use for...' clause covering the main trigger cases. It clearly delimits the multi-omics integration niche, with only minor room to add more natural user phrasings and to tighten abstract phrases like 'systems-level understanding'.

DimensionReasoningScore

Specificity

Concrete actions are stated in third person — 'Identifies therapeutic opportunities and biomarker candidates by integrating multi-layer molecular data' plus disease characterization across four named omics layers. Not 5 because 'Comprehensive disease characterization' and 'systems-level understanding' lean abstract, and the action list has minor coverage gaps.

4 / 5

Completeness

Both parts are explicit: what — 'Comprehensive disease characterization across genomics, transcriptomics, proteomics, and pathways... Identifies therapeutic opportunities and biomarker candidates'; when — 'Use for full-omics disease deep-dive reports, mechanism mapping, and biomarker-and-target identification from multi-omics data'. This matches the anchor-5 example (action list + explicit 'Use for...' trigger phrases), not anchor 4 where the 'when' is only loosely specified.

5 / 5

Trigger Term Quality

Good natural-term coverage: 'multi-omics', 'genomics, transcriptomics, proteomics', 'biomarker', 'mechanism mapping', 'deep-dive reports', 'therapeutic'. Not 5 because common user phrasings like 'integrated omics analysis', 'disease profiling', or 'systems biology' are absent, though the latter is deliberately reserved for a sibling skill.

4 / 5

Distinctiveness Conflict Risk

The multi-omics integration niche ('integrating multi-layer molecular data') is distinct from single-layer skills (variant interpretation, GWAS, pathway-only analysis), and the body's 'NOT for' section explicitly diverts those cases to sibling skills. Not 5 because the description itself doesn't state the boundaries and generic 'disease characterization' has minor overlap with a general disease-research skill.

4 / 5

Total

17

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

mims-harvard/ToolUniverse

Path

plugin/skills/tooluniverse-multiomic-disease-characterization/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.