CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tooluniverse-microbiome-research

Microbiome research using MGnify, GTDB, ENA, OLS (ENVO biomes), EuropePMC, BacDive (strain phenotypes), MediaDive (growth media recipes), and GMrepo (gut microbiome disease-association counts). Covers study discovery, taxonomic profiling, host-microbe interaction analysis, biome-by-condition queries, strain culturing requirements, and phenotype/disease prevalence lookups. Use for microbiome study selection, organism-environment associations, clinical-microbiome literature review, and "how do I grow this organism" / "how prevalent is this species in condition X" questions. Distinct from analytical workflow (use tooluniverse-metagenomics-analysis for that).

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

Highly actionable content with executable, output-annotated examples and well-sequenced lookup workflows, but the single-file structure inlines an API table and a general microbiome interpretation guide that belong in reference files, and several sections duplicate each other or re-teach concepts Claude already knows.

Suggestions

Move the Core Tools table and the Reasoning Framework (diversity metrics, evidence grading, interpretation guidance) into references/ files (e.g., references/tools.md, references/interpretation.md), keeping SKILL.md as a lean overview with one-level-deep pointers.

Cut the duplicated Tips section (accession prefixes and biome-advice already appear in Key Identifiers and Biome Hierarchy) and remove the Quick Start steps that Workflow 2 repeats verbatim.

Trim general-domain explanations (what Shannon/UniFrac/PERMANOVA measure, what dysbiosis is) down to the tool-calibrated thresholds and cautions that Claude could not supply from its own knowledge.

DimensionReasoningScore

Conciseness

The Reasoning Framework explains standard concepts Claude already knows (Shannon index, Bray-Curtis/UniFrac, PERMANOVA, Firmicutes/Bacteroidetes ratio, what dysbiosis means), and there is duplication: the Tips section repeats the MGYS/MGYA/MGYG accession prefixes already stated in Key Identifiers, the 'use MGnify_list_biomes first' advice already in the Biome Hierarchy section, and Quick Start overlaps Workflow 2. Mostly efficient, but noticeable trimming is possible.

3 / 5

Actionability

All code is fully executable `tu.run_one_function` calls with real arguments and accessions, expected outputs shown inline (e.g., BacDive strain IDs, the MediaDive medium_id 1611 cross-reference, GMrepo sample counts), plus concrete parameter guidance like the ENA query format and the single-keyword MGnify timeout warning. Copy-paste ready and covering the common cases.

5 / 5

Workflow Clarity

Six clearly sequenced workflows with concrete chained calls, a data-type decision tree, and a pre-flight check ('determine which data type the user has via MGnify_get_study_detail'). Workflows are read-only lookups so the destructive-operation cap does not apply, but there are no error-recovery loops (e.g., what to do when a search returns nothing or an ID doesn't resolve), keeping it below the top anchor.

4 / 5

Progressive Disclosure

No bundle files exist, so the skill is a 320-line monolith: a 25-row tool table that is essentially an inline API reference and ~80 lines of general interpretation guidance (diversity metrics, evidence grading) that clearly belong in reference files. Section headers and navigation within the file are good, but content that should be separate is inline and no references are used at all.

3 / 5

Total

15

/

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 description: concrete capabilities, named sources with roles, explicit 'Use for' triggers including quoted natural-language questions, and an explicit boundary against a sibling analysis skill. The only gap is missing common domain trigger synonyms such as 'metagenomics' or '16S'.

Suggestions

Add high-frequency natural trigger terms such as 'metagenomics', '16S/amplicon', or 'gut flora' to the 'Use for' clause, since users often phrase microbiome questions with those words.

Optionally include example tool names users might already know they want (e.g., 'search MGnify studies') to catch queries phrased as tool requests.

DimensionReasoningScore

Specificity

The description lists six concrete action types ("study discovery, taxonomic profiling, host-microbe interaction analysis, biome-by-condition queries, strain culturing requirements, and phenotype/disease prevalence lookups") plus eight named data sources each with its role (e.g., "BacDive (strain phenotypes)", "GMrepo (gut microbiome disease-association counts)"). This is comprehensive coverage of concrete actions, matching the top anchor rather than the 'minor gaps' anchor below it.

5 / 5

Completeness

Explicitly answers 'what' (the 'Covers...' sentence enumerating capabilities and sources) and 'when' with concrete trigger phrases ("Use for microbiome study selection, organism-environment associations..."), matching the top anchor exactly. Voice is third-person imperative style consistent with the reference good examples.

5 / 5

Trigger Term Quality

Includes genuinely natural user phrases like "how do I grow this organism", "how prevalent is this species in condition X", "microbiome study selection", and "clinical-microbiome literature review". However, the most common natural terms for this domain — "metagenomics", "16S", "amplicon", "gut flora" — are absent (metagenomics appears only in the pointer to the sibling skill), so coverage is good but not comprehensive.

4 / 5

Distinctiveness Conflict Risk

The closing line "Distinct from analytical workflow (use tooluniverse-metagenomics-analysis for that)" explicitly disambiguates against the most likely competing skill, and the research/lookup framing (culturing, prevalence, literature) forms a clear niche with minimal overlap risk.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

mims-harvard/ToolUniverse

Path

plugin/skills/tooluniverse-microbiome-research/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.