ontology

Store and validate typed entity graphs with relations using JSONL and YAML constraints.

Updated May 17, 2026
One-click install
npx skills add https://github.com/tiankong0101-byte/skills-registry --skill ontology-tiankong0101-byte
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ontology
Source: https://github.com/tiankong0101-byte/skills-registry/tree/main/skills/ontology
Command: npx skills add https://github.com/tiankong0101-byte/skills-registry --skill ontology-tiankong0101-byte

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps you store, connect, query, and validate structured knowledge when simple notes are not enough. It is useful for tracking people, projects, tasks, events, documents, and the relationships between them in a consistent way.

Core Features & Use Cases

  • Entity management: Create, update, delete, and retrieve typed entities such as Person, Project, Task, Event, and Document.
  • Graph relationships: Link entities with relations like ownership, assignment, dependencies, membership, and event attendance.
  • Validation and constraints: Check required fields, enums, forbidden properties, relation types, cardinality, acyclic dependencies, and event date order.
  • Use case: A team lead can record a project, link tasks and owners, then validate the graph to catch missing fields or circular blockers before planning work.

Quick Start

Ask the ontology skill to create a Task entity for a project, link it to the owner, and validate the graph for constraint violations.

Frequently Asked Questions about ontology

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

FAQPage Schema
How do I model task dependencies as a verifiable graph?

To model task dependencies as a verifiable graph, this Skill stores typed entities and relations in JSONL format, applying YAML schema constraints to validate required fields, cardinality, and acyclic dependencies before you plan work.

How do I validate entity relationships in a knowledge graph?

Validating entity relationships in a knowledge graph involves applying YAML schema constraints to check required fields, forbidden properties, relation types, and event date order, catching missing fields or circular blockers using Python-based operations.

Can I use YAML schemas to constrain knowledge graph entities and relations?

Yes, you can use YAML schemas to constrain knowledge graph entities and relations. The Skill requires YAML schema constraints to enforce required fields, enums, relation types, and cardinality against your JSONL graph storage.

What's the best way to track project ownership and event attendance in structured memory?

The best way to track project ownership and event attendance in structured memory is creating typed entities like Person, Project, and Event, then linking them with graph relationships such as ownership, assignment, and event attendance.

Does structured memory support cross-skill state sharing for task tracking?

Yes, structured memory supports cross-skill state sharing for task tracking. The Skill stores connected knowledge as a typed graph with entities and relations, enabling consistent project tracking, task dependencies, and document linking across workflows.

How do I check for circular blockers and acyclic dependencies in project tracking?

To check for circular blockers and acyclic dependencies in project tracking, you validate the graph for constraint violations, ensuring task dependencies remain acyclic and event date order is maintained before planning work.