What problem does it solve? Ontology lookups vary by source and date — OLS, Gemma, and OntoBee can disagree on which relations are shown and which terms are included, making results hard to reproduce. This Skill standardizes ontology term operations across four sources and stamps every output with provenance (source URL, ontology version, sha256 hashes) so downstream analyses can be reconstructed. ## Core Features & Use Cases - Four operations: immediate parents, immediate children, definition plus synonyms, and free-text search, accepting both compact IDs (GO:0006915) and full OBO URIs. - Four sources with explicit semantics: OLS at EBI (immediate relations, version-pinned), Gemma annotations API (transitive relations, strong search), direct OBO file parsing (audit-grade reproducibility), and OntoBee SPARQL (cross-ontology flexibility). - Provenance-stamped outputs: every TSV ships with a sidecar .meta.json recording source URL, ontology version, and sha256 of both the raw upstream response and the output file. - Use Case: A reviewer asks which GO release was used to claim that apoptotic process (GO:0006915) is a child of a given parent term — point them at the .meta.json with the ontology version and source hash. ## Quick Start Ask the assistant to find the immediate parents of GO:0006915 using the ontology-terms skill, optionally specifying a source such as OLS or Gemma.