skill-router

Use when routing an agent request across multiple Skills, building or auditing a routing table, detecting routing coverage gaps, or answering questions like "which Skill handles this?", "who routes X?", or "why did Skill A activate instead of B?". Covers trigger-label matching, file-path matching, keyword matching, description-based semantic matching, scope/type tiebreakers, and coverage-gap detection. Do NOT use when the target Skill is already known (load it directly), when authoring a new Skill (use `skill-metadata-template` instead), or when evaluating a SINGLE Skill's quality (use `graph-audit`).