General
tooluniverse-metagenomics-analysis - Claude MCP Skill
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.
SEO Guide: Enhance your AI agent with the tooluniverse-metagenomics-analysis tool. This Model Context Protocol (MCP) server allows Claude Desktop and other LLMs to microbiome and metagenomics analysis using mgnify, gtdb taxonomy, ena sequencing data, and europepmc... Download and configure this skill to unlock new capabilities for your AI workflow.
Documentation
SKILL.md# Metagenomics & Microbiome Analysis Integrated pipeline for exploring microbiome studies, classifying taxa, assessing genome quality, linking microbial composition to clinical phenotypes, and interpreting findings through pathway analysis and literature context. **Guiding principles**: 1. **Study context first** -- understand biome, sequencing method, and metadata before diving into taxa 2. **Taxonomic consistency** -- GTDB taxonomy as reference standard; reconcile NCBI where needed 3. **Genome quality matters** -- CheckM completeness/contamination thresholds determine trustworthy MAGs 4. **Interpretation over enumeration** -- explain what taxa mean for the biological question 5. **English-first queries** -- use English terms in tool calls ## LOOK UP, DON'T GUESS When uncertain about any scientific fact, SEARCH databases first rather than reasoning from memory. --- ## COMPUTE, DON'T DESCRIBE When analysis requires computation (statistics, data processing, scoring, enrichment), write and run Python code via Bash. Don't describe what you would do — execute it and report actual results. Use ToolUniverse tools to retrieve data, then Python (pandas, scipy, statsmodels, matplotlib) to analyze it. ## Core Databases | Database | Best For | |----------|---------| | **MGnify** | Processed metagenomics studies, taxonomic/functional results | | **GTDB** | Standardized bacterial/archaeal taxonomy, species-level resolution | | **GMrepo** | Gut species-to-human-health phenotype associations | | **ENA** | Raw sequencing datasets and study metadata | | **KEGG** | Pathway mapping for microbial functional annotations | | **PubMed/EuropePMC** | Published microbiome-disease studies | | **CTD** | Chemical-microbiome-disease relationships | --- ## Workflow ``` Phase 0: Parse query → organism, biome, phenotype, or accession Phase 1: Study Discovery → MGnify_search_studies, ENAPortal_search_studies Phase 2: Taxonomic Classification → GTDB_search_genomes, GTDB_get_species, GTDB_search_taxon Phase 3: Genome Quality → MGnify_search_genomes, MGnify_get_genome (CheckM metrics) Phase 4: Functional Annotation → MGnify GO terms + KEGG pathway mapping Phase 5: Clinical Associations → GMrepo species-phenotype links Phase 6: Literature → PubMed/EuropePMC + CTD gene-disease Phase 7: Interpretation & Report Synthesis ``` --- ## Key Phase Notes **Phase 1**: ENA requires structured queries (e.g., `study_title="*IBD*"`), not free text. If ENA fails, fall back to MGnify. **Phase 2**: GTDB uses its own naming (e.g., `s__Bacteroides_A fragilis` vs NCBI `Bacteroides fragilis`). Always note discrepancies. Use `GTDB_search_taxon(operation="search_taxon", query=name)`. **Phase 3 - Quality tiers** (MIMAG): - **High**: >= 90% complete, <= 5% contamination, rRNA + >= 18 tRNAs - **Medium**: >= 50% complete, <= 10% contamination - **Low**: below medium -- flag but don't exclude **Phase 4 - Functional interpretation**: Don't just list GO terms. Connect to biology: | Functional Category | Key KEGG Pathways | Significance | |---|---|---| | SCFA production | map00650, map00640 | Gut barrier, anti-inflammatory | | LPS biosynthesis | map00540 | Pro-inflammatory, endotoxemia | | Bile acid metabolism | map00120 | Fat absorption, FXR signaling | | Tryptophan metabolism | map00380 | Serotonin, AhR, immune | | Vitamin biosynthesis | map00730/740/760 | Host nutritional contribution | Use `kegg_search_pathway(keyword=...)` (NOT `query`). Pathway IDs need organism prefix (`hsa`, `ko`, `eco`), NOT bare `map`. **Phase 5**: GMrepo uses MeSH terms: "Crohn Disease" not "IBD", "Colitis, Ulcerative" not "UC", "Colorectal Neoplasms" not "colorectal cancer". Try NCBI taxon IDs if species name fails. **Phase 6 - Evidence grading**: - **Strong**: Meta-analysis or >5 studies, consistent direction - **Moderate**: 2-5 studies consistent, or 1 large cohort - **Preliminary**: Single study or conflicting - **Mechanistic only**: In vitro/animal, no human epidemiology **Phase 7 - Report**: Executive summary, study landscape, GTDB taxonomy, functional interpretation (not GO term lists), clinical relevance with evidence grades, mechanistic model, genome catalog with quality tiers, data gaps. --- ## Edge Cases & Fallbacks - **Taxon not in GTDB**: Try partial search or fall back to MGnify (NCBI taxonomy) - **No GMrepo data**: Normal for non-gut organisms; use literature - **GMrepo 0 results**: Use formal MeSH terms or NCBI taxon IDs - **No KEGG match**: Check MetaCyc or literature ## Limitations - **GMrepo**: Gut-only - **GTDB**: Bacteria/Archaea only - **ENA**: Raw data only, strict query syntax - **No sequence analysis**: Queries databases, not raw FASTQ/FASTA
Signals
Information
- Repository
- mims-harvard/ToolUniverse
- Author
- mims-harvard
- Last Sync
- 9/5/2026
- Repo Updated
- 9/5/2026
- Created
- 3/26/2026
Reviews (0)
No reviews yet. Be the first to review this skill!
Related Skills
cursorrules
CrewAI Development Rules
firecrawl-build-search
Integrate Firecrawl `/search` into product code and agent workflows. Use when an app needs discovery before extraction, when the feature starts with a query instead of a URL, or when the system should search the web and optionally hydrate result content.
firecrawl-build-onboarding
Get Firecrawl credentials and SDK setup into a project. Use when an application needs `FIRECRAWL_API_KEY`, when an agent should add Firecrawl to `.env`, when the user wants to authenticate Firecrawl for app code, or when choosing the first SDK and docs for a new Firecrawl integration. This skill includes its own browser auth flow, so it does not depend on the website onboarding skill.
firecrawl-build
Integrate Firecrawl into application code whenever a product, agent, or workflow needs web data inside the app — web search, live search results, page scraping, structured extraction, or browser interaction. Use when building any feature that needs data from the web in code, even if the user does not mention Firecrawl explicitly and only describes wanting web data, website content, search, scraping, or interaction in an application. Trigger for Firecrawl requests, "fire girl" shorthand, and generic app-level web-data needs that should map to `/scrape`, `/search`, or `/interact`. Do not use this skill for one-off terminal-only web tasks during the current session; use `firecrawl/cli` for those.
Related Guides
Python Django Best Practices: A Comprehensive Guide to the Claude Skill
Learn how to use the python django best practices Claude skill. Complete guide with installation instructions and examples.
Mastering Python and TypeScript Development with the Claude Skill Guide
Learn how to use the python typescript guide Claude skill. Complete guide with installation instructions and examples.
Optimize Rell Blockchain Code: A Comprehensive Guide to the Claude Skill
Learn how to use the optimize rell blockchain code Claude skill. Complete guide with installation instructions and examples.