audit-skill-conflicts — Pack coherence, not product QA

Degree of freedom: MIXED — Phases 0–1 [HIGH freedom]; Phase 2 routing dry-run [LOW freedom] — skip explicitly if the harness cannot show selection. Never write audit-responsive-layout.

Read-only. Most other audit-* skills inspect an app or repository you ship. This one inspects the skill pack it lives in.

npm run validate:skills checks each file in isolation (name = dir, description ≤320, body <500). It cannot see two skills giving opposite advice, six descriptions all matching "audit my UI", a handoff to a renamed skill, or a greedy description that fires constantly and burns context.

A skill collection is a system. Its failure modes are between files.

Present findings. Rewrite nothing until approved. Highest-leverage first: description rewrites (routing) — they change which skill fires without changing any skill's behavior.