CtrlK
BlogDocsLog inGet started
Tessl Logo

tooluniverse-multi-omics-integration

Multi-omics integration — orchestrate per-layer analysis (transcriptomics, proteomics, epigenomics, genomics, metabolomics) then perform cross-omics correlation, multi-omics clustering, and pathway-level integration. Use for integrative systems-biology analysis, multi-modal disease characterization, and cross-omics biomarker discovery.

64

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/tooluniverse/skills/tooluniverse-multi-omics-integration/SKILL.md

The canonical home for this skill is tooluniverse-multi-omics-integration in mims-harvard/ToolUniverse

SKILL.md
Quality
Evals
Security

Quality

Content

57%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.

Well-organized and dense with useful domain-specific reasoning, but it leans on a phase_details.md reference that is absent from the bundle, leaving core implementations inaccessible, and the multi-step pipeline lacks explicit validation feedback loops between phases.

Suggestions

Add the missing phase_details.md to a references/ directory (or inline the essential code) so the repeated 'See: phase_details.md' pointers resolve to real content.

Insert explicit validation checkpoints between phases (e.g., after Phase 1 QC and Phase 2 sample matching: assert minimums met before proceeding; on failure, diagnose and re-run) to satisfy the batch-pipeline feedback-loop requirement.

Replace the partial correlation loop and pathway_score comment with complete, copy-paste-ready functions rather than fragments deferred elsewhere.

DimensionReasoningScore

Conciseness

Mostly efficient and assumes domain competence; the Domain Reasoning and LOOK UP DON'T GUESS sections add genuine non-obvious value rather than restating basics. A few sections (Use Cases, Limitations) could be tightened slightly.

4 / 5

Actionability

Provides some executable code (match_samples_across_omics, spearmanr loop, pathway_score formula) but key implementations are fragments or comments, and full code is deferred to phase_details.md — a file that is not present in the bundle, leaving guidance incomplete.

3 / 5

Workflow Clarity

Eight phases are clearly sequenced and Quantified Minimums act as a partial checklist, but this batch/multi-step pipeline lacks explicit validation checkpoints and fix→retry feedback loops between phases (the destructive/batch cap applies).

3 / 5

Progressive Disclosure

Good section structure and clear signaling toward phase_details.md, but that referenced file does not exist (no references/ dir), so the one-level-deep navigation is broken rather than resolvable.

3 / 5

Total

13

/

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, third-person description that concisely states concrete capabilities and provides an explicit 'Use for' trigger clause covering several realistic scenarios. Trigger-term synonyms could be broadened slightly, but distinctiveness and completeness are excellent.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'orchestrate per-layer analysis (transcriptomics, proteomics, epigenomics, genomics, metabolomics)', 'cross-omics correlation, multi-omics clustering, and pathway-level integration' — with comprehensive coverage of the integration workflow.

5 / 5

Completeness

Clearly answers 'what' (per-layer orchestration + correlation/clustering/pathway integration) and explicitly answers 'when' via 'Use for integrative systems-biology analysis, multi-modal disease characterization, and cross-omics biomarker discovery.'

5 / 5

Trigger Term Quality

Strong natural domain phrases a practitioner would say ('multi-omics integration', 'cross-omics correlation', 'biomarker discovery', 'systems-biology analysis'), but lacks synonyms/variations and any file-format triggers; not quite comprehensive.

4 / 5

Distinctiveness Conflict Risk

'Multi-omics integration' is a clear niche with distinct, specific triggers; the coordinated cross-layer framing minimizes overlap with single-omics 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.