CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tooluniverse-metagenomics-analysis

Microbiome and metagenomics analysis using MGnify, GTDB taxonomy, ENA sequencing data, and EuropePMC literature. Covers taxonomic classification, genome quality assessment, biome-clinical phenotype linkage, and pathway interpretation. Use for amplicon/shotgun metagenomics study analysis.

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-structured, information-dense skill body: a clear phase workflow, concrete tool syntax, domain-specific gotchas, fallbacks, and honest limitations. The consistent weakness across dimensions is the last increment — trimmed duplicate framing, one executable example per database tool, explicit validation checkpoints, and offloading detail tables to reference files would lift it.

Suggestions

Remove the introductory paragraph that restates the frontmatter description, and fold the 'Guiding principles' list into the phase notes it duplicates.

Add one copy-paste-ready example call for each core tool (MGnify_search_studies, GMrepo lookup) mirroring the concrete kegg_search_pathway(keyword=...) pattern, plus a minimal pandas/scipy snippet to make the 'COMPUTE, DON'T DESCRIBE' mandate executable.

Move the KEGG pathway-significance table and per-database API quirks into a single one-level-deep reference file (e.g., references/tool-notes.md), keeping SKILL.md as a lean overview; add an explicit step after each phase to sanity-check results (e.g., non-empty result count) before proceeding.

DimensionReasoningScore

Conciseness

The body is dense with domain facts Claude cannot reliably recall (tool parameter names, MeSH mappings, MIMAG quality thresholds) and avoids explaining known concepts. It is not a 5 because the opening paragraph restates the frontmatter description and the 'Guiding principles' list overlaps the phase notes, tokens that could be trimmed.

4 / 5

Actionability

Concrete guidance is given with exact call signatures (GTDB_search_taxon(operation="search_taxon", query=name), kegg_search_pathway(keyword=...), study_title="*IBD*"), so most instructions are executable as written. It is not a 5 because no complete executable example exists for MGnify or GMrepo calls, and the mandated Python computation has no sample code, leaving minor gaps.

4 / 5

Workflow Clarity

An explicit 8-phase sequence is paired with per-phase notes and error-recovery fallbacks ('If ENA fails, fall back to MGnify', 'GMrepo 0 results: use formal MeSH terms or NCBI taxon IDs'). It is not a 5 because there are no explicit result-validation checkpoints — nothing instructs verifying result sanity before proceeding to the next phase.

4 / 5

Progressive Disclosure

Sections are well organized and clearly navigable, and no bundle files exist so nothing is buried. It is not a 5 because all ~100 lines are inlined — the KEGG pathway significance table and per-tool API quirks are natural candidates for a one-level-deep reference file that would keep the overview leaner.

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 that pairs a concrete capability list with named domain databases and an explicit 'Use for' trigger clause. The main improvement space is richer trigger-term coverage (synonyms like 16S and MAGs) and extending the when-clause to cover the clinical-linkage capabilities it advertises.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions ('taxonomic classification, genome quality assessment, biome-clinical phenotype linkage, and pathway interpretation') anchored by named data sources (MGnify, GTDB, ENA, EuropePMC), giving comprehensive coverage with no notable gaps. It is not a 4 because the action list leaves no significant capability unstated for the domain.

5 / 5

Completeness

Both 'what' and an explicit 'Use for amplicon/shotgun metagenomics study analysis' trigger are present, satisfying the when-clause requirement. It is not a 5 because the when-clause is narrower than the stated capabilities — clinical phenotype linkage and literature context have no corresponding trigger phrasing.

4 / 5

Trigger Term Quality

Natural terms users would say are present ('microbiome', 'metagenomics', 'amplicon', 'shotgun'), providing good keyword coverage. It falls short of 5 because common variations users actually type — '16S', 'MAGs', 'metagenomic sequencing', 'gut microbiome' — are missing.

4 / 5

Distinctiveness Conflict Risk

The niche is clearly demarcated by domain-specific database names (MGnify, GTDB, GMrepo, ENA) and metagenomics-specific vocabulary, so overlap with other skills is minimal. It matches the 'clear niche with distinct triggers' anchor exactly.

5 / 5

Total

18

/

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-metagenomics-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.