Skill Infrastructure

Concept of the skill

What it is: Skill infrastructure is the deterministic health-tooling layer for a skill library: schema validation, sidecar integrity, manifest freshness, routing checks, drift detection, eval-artifact honesty, export parity, and release gates.

Mental model: Treat the skill corpus like a database. SKILL.md files are authored records, audit-state.json files are sidecar state, manifests and exports are materialized views, relations are foreign keys, and each checker owns one narrow invariant.

Why it exists: Skill libraries decay silently. A stale truth-source hash, vague routing contract, missing eval artifact, or drifted export will not crash the agent, but it can make the loaded skill misleading. The infrastructure turns that quiet drift into explicit findings.

What it is NOT: It is not the authoring guide for one new skill, the graph-audit skill for this repo's conformance run, a generic lint-rule catalog, or a code-review process for health-tooling changes.

Common misconception: A green linter is not a healthy library. Lint proves only the structural invariant it owns; drift, routing, application-eval shape, audit-manifest honesty, export parity, and relation integrity need their own receipts.

Coverage