Graph Audit

Coverage

• Schema conformance: checking that every skills/<name>/SKILL.md validates against schemas/skill.schema.json without errors
• Manifest sync: verifying that examples/skills.manifest.sample.json matches the output of scripts/generate-manifest.js run against the current skills
• Relation integrity: confirming that every target named under relations.* corresponds to a real sibling skill directory and uses the right predicate semantics (related/broader/boundary/disjoint_with/verify_with/depends_on)
• Eval artifact coherence: ensuring that eval_artifacts: present is backed by a real eval artifact under examples/evals/ that names the skill in its skill_name field
• Grounding presence: confirming that every scope: codebase skill has a fully populated grounding block with domain_object, grounding_mode, truth_sources, failure_modes, and evidence_priority
• Name-directory parity: checking that a skill's name field matches the name of the parent directory (required for SKILL.md compatibility)

Philosophy

Skill graphs fail silently. A broken relation or a drifted enum value does not crash the agent — it just makes retrieval subtly wrong, and subtly-wrong retrieval is worse than a crash because nothing tells you to look. The audit's job is to turn every silent bug into a loud one before the graph accumulates enough drift that agents can no longer trust its edges.

Key Files