This skill records the formal ontological commitments of the skill-graph protocol — what entities exist (Skill, ConceptCard, Eval, ComprehensionEval, Relation, Manifest, Audit, Run, Verdict, DriftBaseline, TruthSource), what identity criteria distinguish them, and what axioms govern their state and relationships (e.g., a Skill has exactly one schemaversion; a Verdict tier ordering is APPLICABLE > PROVISIONAL > UNVERIFIED; a ComprehensionEval must carry a dimension tag from the 7 canonical dimensions). Use when proposing a new field or entity in the protocol, designing a schema migration, debating whether a new concept deserves its own protocol entity vs. an attribute on an existing one, or debugging cross-entity inconsistencies in the audit pipeline.
Install with
Claude CodeCodexCursorGitHub CopilotGemini CLI
Supported by the Atlas install prompt. Skill-specific requirements vary.
Skill stats
Skills1CategoryEngineeringStars0
About this skill
This skill records the formal ontological commitments of the skill-graph protocol — what entities exist (Skill, ConceptCard, Eval, ComprehensionEval, Relation, Manifest, Audit, Run, Verdict, DriftBaseline, TruthSource), what identity criteria distinguish them, and what axioms govern their state and relationships (e.g., a Skill has exactly one schemaversion; a Verdict tier ordering is APPLICABLE > PROVISIONAL > UNVERIFIED; a ComprehensionEval must carry a dimension tag from the 7 canonical dimensions). Use when proposing a new field or entity in the protocol, designing a schema migration, debating whether a new concept deserves its own protocol entity vs. an attribute on an existing one, or debugging cross-entity inconsistencies in the audit pipeline.
Quick start
Copy the install prompt. Use the green button above this README.
Send it to your agent. Paste it into your coding agent’s chat and send.
Review the setup. Your agent checks the skill’s instructions, requirements, and installation scope.
This skill records the formal ontological commitments of the skill-graph protocol — what entities exist (Skill, ConceptCard, Eval, ComprehensionEval, Relation, Manifest, Audit, Run, Verdict, DriftBaseline, TruthSource), what identity criteria distinguish them, and what axioms govern their state and relationships (e.g., a Skill has exactly one schema_version; a Verdict tier ordering is APPLICABLE > PROVISIONAL > UNVERIFIED; a ComprehensionEval must carry a dimension tag from the 7 canonical dimensions). Use when proposing a new field or entity in the protocol, designing a schema migration, debating whether a new concept deserves its own protocol entity vs. an attribute on an existing one, or debugging cross-entity inconsistencies in the audit pipeline.
About this listing
Category
Engineering
Reported license
CC-BY-4.0
Listing language (estimated)
English
Review status
Not individually reviewed
Agent compatibility
Atlas installation supports Claude Code, Codex, and Cursor. Skill-specific dependencies and features are checked during setup.