route

# /route Return the one skill that owns a request, the reason, and a confidence. Or return `none` — that is a real answer, not a failure. This skill routes and stops. It never performs the routed work. **Insight:** a flat list of skill names in context is a catalog, not a router. The agent still has to guess, and it guesses from its own narrative of what it is doing — which is wrong exactly when the routing matters. Routing on the **object** being touched is more robust than routing on the **activity**, because the object survives a mistaken self-narrative and the activity does not. **The failure mode this exists to prevent:** hand-rolling a discipline from first principles while the skill that owns it sits unused in the same repo. It happens because the request did not use the skill's vocabulary, so nothing matched, so the agent proceeded — producing a worse version of something already built and tested. ## Modes | Trigger phrases | Mode | Entry point | |---|---|---| | "which skill covers this", "route this" | route one request | the procedure below | | "is there a skill for X" | existence check | the catalog query below | | "why did that route there" | explain a routing | restate the matched layer and the runner-up | ## Inputs Required: the request to route, in the caller's own words. Do not paraphrase it into skill vocabulary first — the paraphrase is where the routing error enters. Optional: the object being touched (path, artifact, external system). **Non-goals....