capabilities-map

To audit installed skills for capability coverage gaps, run a read-only scan of local manifests and per-skill frontmatter to map enabled skills against a locked taxonomy. This generates a coverage matrix that flags any tier with zero enabled coverage as an actionable gap.

A capability matrix in skill taxonomy management is a structured breakdown mapping every enabled and disabled skill against a locked 6-value taxonomy. It uses local manifests and frontmatter declarations to highlight undeclared capabilities and zero-coverage gaps across deployment scenarios.

You can generate a state snapshot from your skills manifest by analyzing inputs from skills.json, aeon.yml, skill-packs.json, and per-skill SKILL.md files. The process validates taxonomy values and outputs a snapshot alongside a human-readable article and delta-informed notification.

Yes, you need specific manifest files to map capability coverage. The process requires reading local manifests like skills.json, aeon.yml, and skill-packs.json, as well as per-skill SKILL.md frontmatter, to accurately build the capability matrix and validate the locked taxonomy values.

You need delta-based notifications for skill audits to inform governance of changes in capability coverage between scans. By comparing the current state snapshot against previous data, these notifications highlight newly undeclared capabilities or resolved coverage gaps for ongoing operational oversight.

Yes, you can validate taxonomy values against your local skills configuration. The mapping process explicitly reads your pack declarations and per-skill frontmatter to validate that all declared capabilities conform to the locked 6-value taxonomy before generating the per-tier breakdown.