ontology-term-resolution

Editorial and source context

What this Skill does

Ontology Term Resolution is a source-indexed Agent Skill for data, research & analysis work. Based on the SKILL.md description, it focuses on resolve free-text scientific labels to ontology term ids and validate existing curies against the ebi…. Use the linked GitHub file to confirm scope and prerequisites before enabling it.

What the author says

Resolve free-text scientific labels to ontology term IDs and validate existing CURIEs against the EBI Ontology Lookup Service (OLS4). Use whenever an ontology identifier must be produced or checked - annotating tissue, cell type, disease, phenotype, assay, chemical, organism, sex, or developmental stage fields; preparing metadata for GEO, ENA, BioSamples, CELLxGENE, HCA, or ISA-Tab submission; auditing a metadata table of term IDs; checking whether a term is obsolete and what replaced it; or mapping between ontologies. Triggers include "ontology term", "ontology ID", "CURIE", "controlled vocabulary", "UBERON", "CL:", "MONDO", "HPO", "EFO", "ChEBI", "NCBITaxon", "GO term", "PATO", "annotate this tissue/cell type/disease", and any request to emit or verify an identifier shaped like PREFIX:0001234.

Compatibility and requirements

• Use an agent runtime that supports Agent Skills and the linked SKILL.md format.
• Confirm the source repository's tools, SDKs, and platform prerequisites for security and compliance work.

How to install or import it

• Open the linked GitHub SKILL.md and review its scope and setup instructions.
• Install or import the skill using the agent runtime's documented workflow.
• Run a small, non-sensitive test and verify the output before broader use.

Permissions and risks

• Review every command, file path, network request, dependency, and credential scope before enabling it.
• GitHub stars indicate popularity, not safety or correctness; validate the source and test with non-sensitive data.

Example workflows

• Ask an AI agent to apply Ontology Term Resolution to security and compliance work described in the source record.
• Have the agent state assumptions, required tools, and expected output before using this data, research & analysis skill.
• Compare the result with the linked GitHub SKILL.md and verify it against your project requirements.