ontology-curator

Manage ontology maintenance, evolution, and versioning with KGCL and oaklib.

68|13|Updated Aug 9, 2025
One-click install
npx skills add https://github.com/kriegcloud/beep-effect --skill ontology-curator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ontology-curator
Source: https://github.com/kriegcloud/beep-effect/tree/main/.repos/ontology-skill/.claude/skills/ontology-curator
Command: npx skills add https://github.com/kriegcloud/beep-effect --skill ontology-curator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires oaklib, robot, runoak, and includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill streamlines the complex process of maintaining, updating, and versioning ontologies, ensuring consistency and auditability of changes.

Core Features & Use Cases

  • Ontology Maintenance: Manages term deprecation, structural changes, and versioning.
  • Change Management: Handles KGCL change requests, diff generation, and release workflows.
  • Use Case: When an existing term in an ontology needs to be renamed, reparented, or deprecated, this Skill provides the tools and workflow to do so safely and systematically.

Quick Start

Use the ontology-curator skill to deprecate the term EX:0042 and add a replacement pointer to EX:0099.

Frequently Asked Questions about ontology-curator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deprecate an ontology term and add a replacement pointer?

To deprecate an ontology term, you apply a KGCL change request to obsolete the identifier and specify a replacement term. This ensures systematic structural evolution and maintains metadata consistency during knowledge graph maintenance.

What is KGCL and how does it handle ontology change requests?

KGCL is a change language for managing ontology evolution and maintenance. It standardizes structural modifications like term deprecation, reparenting, and renaming, ensuring that knowledge graph updates are systematic and auditable.

Do I need oaklib and robot installed to manage ontology versioning?

Yes, oaklib and robot are required dependencies for executing ontology maintenance operations. These tools provide the underlying command-line functionality needed to process KGCL requests and generate structural diffs for release workflows.

What's the best way to generate diffs for ontology release workflows?

Generating ontology diffs is handled by applying structural change commands via runoak and robot. This workflow tracks term modifications and deprecations, producing an auditable version history for systematic knowledge graph releases.

Can I use this approach to manage structural changes like reparenting terms in a knowledge graph?

Yes, reparenting terms within a knowledge graph is a core structural change supported by KGCL. The workflow safely modifies hierarchy relationships and validates the ontology structure using oaklib to ensure consistency.

Why should I use a KGCL workflow instead of manually editing ontology files?

Using a KGCL workflow ensures ontology changes are auditable and systematically versioned. Manual edits risk breaking structural consistency, whereas this approach validates dependencies and tracks deprecations safely through automated release workflows.