ontology

Manage structured agent memory with a typed ontology graph via Python CLI.

52|3|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/Zhow01/SkillAttack --skill ontology-zhow01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ontology
Source: https://github.com/Zhow01/SkillAttack/tree/main/data/hot100skills/002_oswalpalash_ontology
Command: npx skills add https://github.com/Zhow01/SkillAttack --skill ontology-zhow01

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Typed knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, Document), linking related objects, enforcing constraints, planning multi-step actions as graph transformations, or when skills need to share state.

Core Features & Use Cases

  • Typed vocabulary and constraint system for representing knowledge as a verifiable graph.
  • Create, query, relate, and validate entities and relations with an append-only JSONL storage.
  • Planning as graph transformation: model sequences of operations to achieve complex goals and ensure consistency across skills.
  • Use cases include cross-skill data sharing, project/task management, and knowledge management across an agent ecosystem.

Quick Start

Create a Person named Alice in memory/ontology and list all Person entities.

Frequently Asked Questions about ontology

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

FAQPage Schema
How do I create and query typed entities in a knowledge graph for agent memory?

You can create and query typed entities in a knowledge graph for agent memory using a Python CLI to manage structured data, validate constraints against a YAML schema, and store records in an append-only JSONL log.

What is the best way to share state and link related objects across multiple agent skills?

Sharing state and linking related objects across multiple agent skills is managed through a typed ontology graph that enables cross-skill data sharing, enforces constraints, and models multi-step planning as graph transformations.

How does schema validation work when mutating entities and relations in a graph memory?

Schema validation for mutating entities and relations in graph memory works by reading an optional YAML schema definition and enforcing type and constraint rules before applying runtime operations and appending data to the JSONL log.

Can I use a Python CLI to manage and validate entities like Person, Project, and Task?

Yes, you can use a Python CLI to create, list, update, delete, and validate typed entities like Person, Project, and Task, ensuring all operations conform to a defined YAML schema and are tracked in an append-only log.

Do I need YAML to define constraints for a typed ontology graph?

Yes, YAML is required as a dependency to define and enforce the typed vocabulary and constraint system that validates entities and relations within the ontology graph memory.

Why use an append-only JSONL log for storing knowledge graph entities and relations?

An append-only JSONL log stores knowledge graph entities and relations to preserve a verifiable history of mutations, ensuring data consistency and constraint validation across composable agent skills.