skill-library-auditlisted

# Skill Library Audit ## Core Question Should a proposed or existing skill be added, compacted, merged, split, deferred, or rejected to keep the skill library small, routable, and low-confusion? ## When To Use Use this skill when: - reviewing a new proposed Git skill - auditing overlap between existing skills - deciding whether a workflow should be a first-class skill or a reference - checking whether a skill over-acts beyond its owner boundary - checking whether skill growth increases context bloat or routing confusion ## When Not To Use Do not use this skill when: - executing Git operations - editing skill files directly - rewriting a skill after the audit decision - reviewing project code unrelated to skill library design Route to: - implementation work routes to the repository editing workflow - Git repository state routes to `repo-state-diagnosis` - skill execution issues route to the owning skill ## Required Evidence Before action, inspect or establish: - proposed skill name and core question - existing `skills/routing.md` ownership table - existing `SKILL.md` boundaries for adjacent skills - reference/test/changelog footprint - expected frequency of use - mutation and tool-use scope - context budget impact and likely lazy-load triggers No-evidence rule: - Do not make strong claims without observed evidence. - State assumptions when proceeding under incomplete evidence. - Stop when missing evidence affects safety, correctness, user work, remote state, or