CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tooluniverse-metabolomics-analysis

Analyze metabolomics data end-to-end — metabolite identification, quantification (TIC normalization, batch correction), differential analysis, and pathway interpretation. Use for processing mass-spec metabolomics output, normalization choice, untargeted metabolomics workflows, and integrating with other omics layers.

Quality

80%

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-metabolomics-analysis/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 body delivers strong domain-specific decision guidance (normalization tradeoffs, QC thresholds, confidence levels) and unusually concrete tool-call documentation, but it is padded by triple restatement of the same pipeline and long verification narratives. The tool catalogs belong in reference files, and the two referenced companion files are missing from the bundle.

Suggestions

Collapse the triple restatement: drop either the "Core Capabilities" table or the ASCII "Workflow Overview" diagram — the Phase Summaries already carry the same pipeline with more specificity, freeing ~60 lines.

Move the MassBank and GNPS tool tables plus the two "Verified live" narrative paragraphs into a reference file (e.g., references/spectral_libraries.md), keeping a one-line pointer and the key decision rule (MassBank for unknown spectrum, HMDB once a name is suspected) in the body.

Ship code_examples.md and report_template.md alongside SKILL.md — the relative links currently resolve to nothing in the bundle — or inline minimal executable snippets for QC and normalization, the phases currently lacking concrete code.

DimensionReasoningScore

Conciseness

The pipeline is restated three times — the "Core Capabilities" table, the ~50-line ASCII "Workflow Overview" diagram, and the "Phase Summaries" — and the MassBank/GNPS sections carry long "Verified live" narrative paragraphs and library-comparison digressions ("a compound absent from one may well be present in the other") that are more than minor padding. The Domain Reasoning and tool-parameter content is genuinely non-obvious, so this is not the severely-padded anchor (2); it sits at mostly-efficient-but-needs-tightening.

3 / 5

Actionability

Guidance is concrete and near-executable throughout: exact thresholds (CV < 30%, blank > 3x, +/- 5 ppm, adj. p < 0.05, |log2FC| > 1.0, IS recovery 95-105%), named tests (Welch's t-test, Benjamini-Hochberg FDR), and tool calls with literal parameter strings ("163.0601;100,145.0495;60,127.0390;30", cosine thresholds, USI format). It falls short of fully copy-paste-ready (5) because no executable code is inlined and the referenced code_examples.md is absent from the bundle, leaving the core analysis phases as prose instructions.

4 / 5

Workflow Clarity

The 8-phase sequence is clear (diagram plus per-phase summaries) with explicit validation checkpoints: QC gates ("reject >30%", "keep >3x blank", "filter features with >50% missing", IS recovery range), MSI confidence levels L1-L4, R2/Q2 reporting for PLS-DA, "check each candidate's formula/mass before treating a hit as a confirmed match", and the GNPS mirror-plot sanity check. It misses anchor 5 because there is no systematic if-validation-fails-then-retry feedback loop across the phases, only scattered per-check criteria.

4 / 5

Progressive Disclosure

Structure is good: a concise overview with well-labeled sections, a clearly signaled "Reference Files" section, and one-level-deep references (code_examples.md, report_template.md) plus external database/method links. However, the ~40-line MassBank/GNPS tool catalogs with verification narratives are inlined content that belongs in a reference file, and both referenced .md files are absent from the bundle, making the section-navigating links dead as shipped. That places it between the good-structure anchor (4) and the should-be-separate-is-inline anchor (3).

4 / 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: third-person, specific, and comprehensive, with an explicit 'Use for' clause carrying concrete triggers. The only weaknesses are missing common platform synonyms (LC-MS, GC-MS, NMR, biomarker) in the trigger list and slight overlap with a dedicated multi-omics skill via the integration trigger.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete actions covering the full pipeline — "metabolite identification, quantification (TIC normalization, batch correction), differential analysis, and pathway interpretation" — with parenthetical specifics (TIC normalization, batch correction) beyond generic verbs. It matches the comprehensive-coverage anchor; coverage spans identification through interpretation, so the minor-gaps anchor (4) fits less well. Voice is third person ("Analyze"), so no voice penalty applies.

5 / 5

Completeness

It explicitly answers both questions: the "what" via the end-to-end action list (identification, quantification, differential analysis, pathway interpretation) and the "when" via an explicit "Use for processing mass-spec metabolomics output, normalization choice, untargeted metabolomics workflows, and integrating with other omics layers" clause with concrete trigger phrases. This matches the top anchor; the explicit 'Use when' guidance rule (cap at 3 if absent) is not triggered.

5 / 5

Trigger Term Quality

Natural trigger phrases users would say are present: "processing mass-spec metabolomics output", "untargeted metabolomics workflows", "normalization choice", "integrating with other omics layers". Common variations are missing — no platform terms (LC-MS, GC-MS, NMR), file formats (.mzML), or "biomarker" — so it falls at the good-but-incomplete anchor rather than the comprehensive-synonyms anchor (5), and clearly above the sparse-keywords anchor (3).

4 / 5

Distinctiveness Conflict Risk

The metabolomics niche is clear and triggers are domain-specific, but "integrating with other omics layers" reaches into multi-omics territory where a sibling skill (the body lists tooluniverse-multi-omics-integration) could also claim the request. That is minor overlap with a closely related skill — anchor 4 — rather than the clean-niche anchor (5) or the still-generic anchor (3).

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

relative_links

Relative link issues: 3 missing

Warning

Total

15

/

16

Passed

Repository

mims-harvard/ToolUniverse

Path

plugin/skills/tooluniverse-metabolomics-analysis/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.