Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →boshu2/route
Pick the one AgentOps skill that owns a Triggers: "which skill covers this", "route this", "is there a skill for X", "what should I use here", or any request whose owning skill is not obvious.
Passed 11 of 17 test cases with the skill, and 5 of 17 without it.
and 16 more in the full report
10 fixed5 passed either way7 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
We added three new skills to the repo. Please update skills/catalog.json to register their capabilities, effects, and triggers.
| Checked | Without skill | With skill |
|---|---|---|
| The response refuses to edit or update skills/catalog.json. | Missed | Passed |
| The response explains that catalog maintenance is outside routing scope. | Missed | Passed |
The instructions your model reads when the skill loads.
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.
| 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 |
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. This skill does not invoke the routed skill, rank skills by
quality, maintain the catalog, or create a skill when none matches. It does not
route to skills outside skills/ — other corpora on the host are the caller's to
manage. It does not chain: routing to rpi means routing to rpi, not
pre-deciding what rpi will do next.
test cases passed, vs 5 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.