skill-graph-ontology

Name: skill-graph-ontology
Availability: InStock
Author: jacob-balslev

Define canonical entities, identity criteria, and lifecycle axioms for the skill-graph protocol.

Updated May 14, 2026

Search Tags:#ontology #audit #protocol #drift #schema-version #entity-model #comprehension-eval

Ready to run

npx skills add https://github.com/jacob-balslev/skills --skill skill-graph-ontology

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: skill-graph-ontology
Source: https://github.com/jacob-balslev/skills/tree/main/skill-graph-ontology
Command: npx skills add https://github.com/jacob-balslev/skills --skill skill-graph-ontology

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The ontological commitments of the skill-graph protocol are documented here to provide a single, authoritative reference for what entities exist, how they are identified, and how they evolve, enabling consistent tool behavior and governance across upgrades.

Core Features & Use Cases

Defines first-class entities (Skill, ConceptCard, Eval, ComprehensionEval, Relation, Manifest, Audit, Run, Verdict, DriftBaseline, TruthSource) and their identity criteria.
Specifies lifecycle axioms and invariants (for example, monotonic schema_version, and the Verdict tier ordering) to guide tool behavior and schema migrations.
Provides concrete use cases for designing migrations, debugging cross-entity inconsistencies, and aligning lint/manifest/audit tooling with a shared model.

Quick Start

Review this ontology scaffold and align your protocol tooling to its canonical entity model.

Frequently Asked Questions about skill-graph-ontology

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

FAQPage Schema

What is an ontology in the skill-graph protocol and why do I need it for schema evolution?▼

An ontology in the skill-graph protocol defines canonical entities, identity criteria, and lifecycle axioms to provide a single source of truth for protocol semantics. You need it to ensure consistent tool behavior and governance across schema migrations and upgrades.

How do I design a schema migration that respects protocol lifecycle axioms?▼

To design a schema migration respecting lifecycle axioms, review the ontology scaffold for invariants like monotonic schema_version and Verdict tier ordering. Align your migration logic with these defined identity criteria to satisfy governance checks.

What first-class entities does the skill-graph protocol ontology define?▼

The skill-graph protocol ontology defines first-class entities including Skill, ConceptCard, Eval, ComprehensionEval, Relation, Manifest, Audit, Run, Verdict, DriftBaseline, and TruthSource, each with specific identity criteria for cross-tool consistency.

Can I use this ontology to debug cross-entity inconsistencies across different protocol tools?▼

Yes, you can use this ontology to debug cross-entity inconsistencies by referencing its canonical entity model. It provides a shared model to align lint, manifest, and audit tooling, ensuring all tools interpret protocol semantics consistently.

What are the limitations of relying on a single source of truth for protocol semantics?▼

A limitation of relying on a single source of truth for protocol semantics is that any changes must strictly respect defined identity criteria and lifecycle rules. Tools diverging from this ontology scaffold risk breaking cross-tool consistency and failing governance checks.