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.

66

Quality

78%

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 ./plugin/skills/tooluniverse-multi-omics-integration/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 content is well-structured and mostly executable with a clear phased workflow, but it relies on a phase_details.md file that is not present in the bundle and lacks explicit validation/feedback loops for batch integration steps.

Suggestions

Add the missing phase_details.md to the bundle (references/) or inline the essential phase implementations so the repeated 'See: phase_details.md' references resolve to real content.

Insert explicit validation checkpoints in the workflow (e.g., after Phase 1 QC and Phase 2 sample matching) with a validate->fix->retry loop for batch integration operations.

Expand the pathway integration snippet beyond the single-line mean formula into executable code consistent with the correlation example.

DimensionReasoningScore

Conciseness

Dense, mostly assumes Claude's domain knowledge with minimal padding; the short 'Domain Reasoning' prose could be trimmed but is largely justified context rather than fluff.

4 / 5

Actionability

Provides executable code for sample matching and Spearman correlation plus concrete QC tables, but the pathway score is a one-line formula and substantial implementation detail is deferred to phase_details.md.

4 / 5

Workflow Clarity

The 8-phase sequence is clearly laid out, but validation checkpoints are only implicit and no validate->fix->retry feedback loop is given for batch integration operations, which caps workflow clarity per the rubric.

3 / 5

Progressive Disclosure

The body repeatedly signals a one-level-deep phase_details.md reference, but that file is absent from the bundle (no references/ directory), so the signaled reference structure is not actually backed by existing files.

3 / 5

Total

14

/

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.

The description is specific, complete, and distinctive, cleanly answering both what the skill does and when to use it with concrete trigger phrases. Minor synonym/file-extension coverage is the only gap preventing a perfect trigger-term score.

DimensionReasoningScore

Specificity

Lists multiple concrete actions (orchestrate per-layer analysis, cross-omics correlation, multi-omics clustering, pathway-level integration) across five named omics layers, matching the comprehensive-coverage anchor.

5 / 5

Completeness

Explicitly states both what it does (orchestrate per-layer analysis and cross-omics integration tasks) and when to use it ('Use for integrative systems-biology analysis, multi-modal disease characterization, and cross-omics biomarker discovery').

5 / 5

Trigger Term Quality

Strong natural domain phrases ('multi-omics integration', 'cross-omics biomarker discovery', 'multi-modal disease characterization') users would say, but a few synonyms and concrete file/datatype triggers are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (integrative multi-omics) with distinct triggers that are unlikely to fire for single-omics or unrelated 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.