ontology

Manage typed knowledge graphs with entity CRUD, relations, and schema validation.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/sangtd05/gitops-repo --skill ontology-sangtd05
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ontology
Source: https://github.com/sangtd05/gitops-repo/tree/main/resources/openclaw/skills/ontology
Command: npx skills add https://github.com/sangtd05/gitops-repo --skill ontology-sangtd05

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Typed knowledge graphs enable structured agent memory, cross-skill data sharing, and constraint-driven planning by storing entities, relations, and schemas.

Core Features & Use Cases

  • CRUD for typed entities (Person, Project, Task, Event, Document) and their relations.
  • Enforce constraints and support planning via graph transformations.
  • Use across skills to share state and coordinate multi-step actions.

Quick Start

Create a Person named Alice and then query all Person entities to verify.

Frequently Asked Questions about ontology

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

FAQPage Schema
How do I build a typed knowledge graph for agent memory?

Build a typed knowledge graph by creating entities, defining their types, and establishing relations. This skill provides CRUD operations and schema validation to structure agent memory and enable cross-skill data sharing.

How do I enforce graph constraints for multi-step planning tasks?

Enforce graph constraints by applying schema validation and graph transformations. This ensures typed entities and relations follow defined rules, supporting reliable planning for multi-step actions across tasks.

Can I use a knowledge graph to share state across different skills?

Yes, a typed knowledge graph can share state across skills. By storing entities and relations in an append-only storage system, different skills query and update the shared graph to coordinate actions.

What is the best way to manage CRUD operations for entities and relations in a knowledge graph?

Manage CRUD operations for entities and relations using a schema-validated graph structure. This skill allows you to create, read, update, and delete typed nodes like Person or Project while maintaining relation integrity.

Does this knowledge graph implementation support append-only storage?

Yes, the implementation supports append-only storage for entities and relations. This ensures data immutability for memory tracking while allowing schema validation and graph-based querying.