ontology

Model and store typed knowledge graphs with schema constraints and append-only logging.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/syahravi/openclaw --skill ontology-syahravi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ontology
Source: https://github.com/syahravi/openclaw/tree/main/skills/ontology
Command: npx skills add https://github.com/syahravi/openclaw --skill ontology-syahravi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Many agent workflows suffer from fragmented, inconsistent, or unstructured memory that makes linking people, projects, tasks, events, and documents difficult to query or validate. The ontology skill provides a typed knowledge graph with relations and constraints so agents and skills can reliably store, discover, and reason about shared state.

Core Features & Use Cases

  • Typed entities and relations (Person, Project, Task, Event, Document, Credential, etc.) with property schemas and validation.
  • Append-only graph storage for immutable history and safe merges, plus schema-append utilities to evolve types without overwriting past data.
  • CLI-driven CRUD, relation creation, graph queries, traversal utilities, and a programmatic API for integration with other skills.
  • Constraint enforcement including required/forbidden properties, enums, relation cardinality, and acyclicity checks to prevent circular dependencies.
  • Planning as graph transformations: model multi-step plans as validated create/relate operations and integrate cross-skill communication patterns.

Quick Start

Create a Person named Alice and a Project called Website Redesign, then relate the project to Alice as its owner using the ontology CLI.

Frequently Asked Questions about ontology

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

FAQPage Schema
How do I store structured agent memory with a queryable knowledge graph?

Structured agent memory is stored by modeling typed entities and relations in a local knowledge graph, enforcing schema constraints and append-only mutation logging to ensure data consistency and safe merges.

How does a typed knowledge graph validate relations and prevent circular dependencies?

A typed knowledge graph validates relations by enforcing schema constraints, required properties, enums, and relation cardinality, plus acyclicity checks to prevent circular dependencies during entity linking and CRUD operations.

What is the best way to model multi-step planning as graph transformations?

Multi-step planning is modeled as graph transformations by creating validated create and relate operations for entities, integrating cross-skill communication patterns for shared state within local workspace workflows.

Can I evolve entity types and merge schemas without overwriting past graph data?

You can evolve entity types using schema-append utilities that merge new properties without overwriting past data, maintaining immutable history through append-only graph storage for safe migrations.

How do I create entities and link them using a CLI for knowledge graph validation?

Entities are created and linked using a CLI-driven CRUD interface that supports relation creation, graph queries, traversal utilities, and a programmatic API for integration with other skills.

When do I need a typed knowledge graph for cross-skill shared state management?

A typed knowledge graph is needed when workflows suffer from fragmented memory, requiring reliable storage, discovery, and reasoning about shared state across people, projects, tasks, events, and documents.