plugin/skills/tooluniverse-ecology-biodiversity/SKILL.md
Ecology, biodiversity, and conservation biology research — species identification (GBIF, NCBI Taxonomy), invasive species impact, ecosystem dynamics, conservation status (IUCN), niche ecology. Use for biodiversity questions, species comparison, invasion biology, conservation prioritization, and ecology-related literature search.
npx skillsauth add mims-harvard/tooluniverse tooluniverse-ecology-biodiversityInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
When a question involves identifying or comparing species:
GBIF_search_species to get taxonomy, WoRMS_search_species for marine organismsPubMed_search_articles or EuropePMC_search_articles to find studies on specific ecological impactsReasoning framework — when comparing invasive species impacts:
Reasoning framework for pollination questions:
Reasoning framework for population ecology questions:
| Tool | Use For |
|------|---------|
| IUCN_get_conservation_status | Red List conservation status (CR/EN/VU/NT/LC) by scientific name — the authoritative extinction-risk source (needs a free IUCN_API_KEY) |
| GBIF_search_species | Species taxonomy, occurrence data, distribution |
| GBIF_search_occurrences | Where has a species been observed? |
| GBIF_get_taxon_parents | Walk UP the GBIF Backbone tree — ranked ancestor lineage (kingdom→genus) for a taxonKey |
| GBIF_get_taxon_children | Walk DOWN the tree — direct child taxa (e.g. species in a genus) for a taxonKey |
| GBIF_get_taxon_synonyms | Alternative / historical scientific names for an accepted taxonKey |
| GBIF_get_vernacular_names | Common names (with language code) for a taxonKey; optional language filter |
| GBIF_parse_name | Parse messy/authored name strings into canonical name + genus/epithet/author/year |
| iDigBio_search_records | Search 130M+ digitized museum/herbarium specimen records (Darwin Core) by genus/scientificname/locality — use to complement GBIF with physical-specimen provenance |
| iDigBio_get_record | Full Darwin Core detail for one specimen by uuid (from iDigBio_search_records) |
| WoRMS_search_species | Marine species taxonomy |
| ensembl_get_taxonomy | Taxonomic classification |
| NCBIDatasets_get_taxonomy | NCBI taxonomy lookup |
| PubMed_search_articles | Literature on ecology topics |
| EuropePMC_search_articles | European literature including ecology |
Resolve a name to a GBIF usageKey once, then navigate the Backbone tree:
key = tu.run_tool("GBIF_match_name", {"name": "Panthera leo"})["data"]["usageKey"] # 5219404
tu.run_tool("GBIF_get_taxon_parents", {"taxon_key": key}) # Animalia→...→Felidae→Panthera
tu.run_tool("GBIF_get_taxon_synonyms", {"taxon_key": key}) # Felis leo Linnaeus, 1758, ...
tu.run_tool("GBIF_get_vernacular_names", {"taxon_key": key, "language": "eng"}) # Lion, African Lion
# Walk down from a genus key (Panthera = 2435194) to its species:
tu.run_tool("GBIF_get_taxon_children", {"taxon_key": 2435194, "limit": 8})
# Normalize an authored name string without a key:
tu.run_tool("GBIF_parse_name", {"name": "Quercus robur L."}) # canonicalName 'Quercus robur'
All five tools hit the public GBIF API with no key. Get the starting taxon_key
from GBIF_match_name or GBIF_search_species.
Ecology questions often have counter-intuitive answers. For example:
Always search the literature before answering ecology questions. Use PubMed_search_articles with specific terms like "[species] invasive impact [region]" or "[organism] [ecological process]".
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.
tools
Generate the success criteria for a task or question, then review work against them. Given a task, goal, or open-ended question, decompose it into scenarios, evaluation perspectives, and fine-grained weighted YES/NO criteria using the Recursive Expansion Tree (RET) method; if work is supplied, score it criterion-by-criterion and surface what is missing or could be better. Use when asked to self-review or check your own work, judge whether a task is done well or completely, build a definition-of-done or completeness checklist, create an evaluation rubric or grading criteria, score or grade answers to a question, set up an LLM-as-judge rubric, or when the user mentions self-review, completeness check, success criteria, evaluation criteria, scoring rubric, Qworld, or the RET algorithm.
tools
Find the real protein target(s) of a peptide from its sequence — peptide target deorphanization / off-target identification, for ANY target class (GPCR, ion channel, protease, cytokine/growth-factor receptor, enzyme, integrin), not only GPCRs. Use when a peptide has a phenotype but does not bind its hypothesized target, when a peptide binds a target in one species or assay but not another, or to screen candidate targets for an orphan peptide. A target-class router steers a multi-route keyless pipeline (PROSITE/ELM motif, BLAST homology, HGNC/InterPro/GPCRdb/GtoPdb target-family enumeration, OpenTargets phenotype anchor, EnsemblCompara/Alliance cross-species reconciliation) plus optional NVIDIA-NIM co-folding (Boltz2, AlphaFold2-Multimer, OpenFold3) for structural confirmation.
tools
Install or update ToolUniverse in Claude Science — create the conda env, install the tooluniverse pip package, and (re)build the tooluniverse-research skill by fetching the current workflow library from GitHub. Use for first-time setup, upgrading the ToolUniverse version, refreshing the bundled workflows after an upstream release, or reinstalling on a new machine.
tools
Install, set up, verify, update, pin, uninstall, or troubleshoot the ToolUniverse plugin on OpenAI Codex. ALWAYS consult this skill for any of those — don't answer from memory, because the exact marketplace name (mims-harvard/ToolUniverse), the "codex plugin marketplace add" then "codex plugin add -m tooluniverse" flow, Codex's startup auto-upgrade behavior, the uvx tooluniverse MCP server, and the API-key env vars are easy to get wrong. Use it whenever someone wants to get ToolUniverse (or "the 1000+ scientific tools" / "the harvard tools") working on Codex, says the Codex plugin or its tools/skills won't load, hits a uvx or MCP-server startup error, asks how Codex updates it, wants to pin or remove it, or finds it running an old tool version — even if they never say the word "plugin". Not for the Claude Code plugin (use tooluniverse-claude-code-plugin), for running research with the tools, or for authoring new tools or skills.