Skill Router

Coverage

• Routing by keyword pattern: matching inbound query terms to skill keywords arrays to identify the best candidate
• Routing by trigger label: matching explicit skill-router labels (triggers field) to eliminate ambiguity when the intent is declared
• Routing by file path: matching touched or mentioned file paths against skill paths arrays for file-activated skills
• Fallback ordering: how to rank skills when multiple candidates score equally, including scope and type tiebreakers
• Coverage gaps: detecting when no skill matches a request and how to surface that gap as an authoring signal

Philosophy

Routing is adversarial against convenience. The tempting move — "if nothing matches exactly, just pick the closest skill and activate it" — is the one that silently degrades every agent that depends on the router. A wrong skill that activates confidently is worse than a coverage gap that surfaces loudly, because silent wrongness has no signal for anyone to fix. The router's job is to produce either a certain winner or an explicit non-answer, never a confident guess.

Four principles follow from that stance: