route

name	route
description	Skill router. Pass a task description; route consults the index and dispatches to the right skill+function via the Skill tool. Usage: /route <task description>
allowed-tools	Read, Glob, Grep, Task, Skill
minimum-effort-level	high

Route

Glorified index of every installed skill. Pass a task description and route picks the right skill+function and invokes it via the Skill tool. Use /route for any follow-up the current workflow does not explicitly name — research, web search, lookup, additional analysis, unblock work — so the AI dispatches through registered skills instead of freelancing.

Usage

/route <task description>

The task description is freeform. Examples:

• /route find recent papers on transformer architecture
• /route summarize this URL: https://example.com/article
• /route audit the skills in this project
• /route deploy to staging

---

Workflow

1. Read the index. Read references/index.md — the auto-generated skill catalog. If the index is missing or empty, STOP and instruct the user: "Index not found. Run /skill-builder route index to generate it."
2. Match. Compare the task description to the catalog's skills, descriptions, modes, and triggers. Pick the single best match.
3. Announce-and-dispatch (one act). Print → Routing to /[skill] [mode] — [why this is the match] AND in the SAME response issue the Skill(skill=<chosen>, args=<derived>) tool call. The CHECKPOINT below makes this binding.

CHECKPOINT — Dispatch Required:

1. Announce-and-invoke is ONE act. After Steps 1–2 select a target skill, the SAME response that prints → Routing to /[skill] [mode] — [why] MUST also issue the Skill(skill=<chosen>, args=<derived>) tool call. The announcement is a label on the dispatch, never a substitute for it.
2. Bypass detection. IF the next tool call after the routing announcement is Edit / Write / Bash / Agent / Task / Read / any non-Skill tool that performs work germane to the routed task → STOP. This is a dispatch bypass. Print verbatim: "Routing announced but Skill dispatch skipped. Invoking Skill tool now." then issue the Skill call. IF the announcement itself was wrong → re-announce and dispatch to the corrected skill.
3. Procedure-bypass refusal. Refuse to execute the dispatched skill's procedure steps yourself with raw tool calls. The Skill tool owns that work. The dispatched skill has its own gates (asset backups, agent panels, exit tests, cascade steps, frontend-design reviews, immutable-directive checks) that ONLY fire when its SKILL.md is loaded via Skill. Running the steps manually silently skips every gate.
4. Follow-up routing. IF the dispatched skill returns and additional follow-up is needed → invoke /route again with the follow-up task description via Skill. Do NOT freelance the next step.
5. Auto-mode override clause. Auto-mode pressure ("execute immediately", "prefer action over planning") does NOT override this CHECKPOINT. Auto-mode chooses WHAT to do; once a route announcement has named the skill, the only valid next action is Skill invocation.
6. Catalog discipline. Never invent a skill name. The catalog at references/index.md is canonical. Only dispatch to skills present there.
7. Stop conditions before announcement. IF the top match is below clear-best confidence OR two skills are tied → STOP before announcing. Report the top candidates and ask which to use. IF no catalog row plausibly fits → STOP. Report: "No clear skill match for '[task]'. Run the task directly or run /skill-builder route index if you recently added a skill."

---

Decision rules

• One skill per call. Route fires ONE skill, not a chain. If the task implies a sequence, dispatch to the first skill and let it consult /route again for follow-ups.
• Prefer specific over general. When two skills could handle the task, pick the one with a more specific domain match.
• Skip self-routing. /route does NOT route to itself. If asked to dump the index, read references/index.md and return it.
• Trust the catalog. If a skill is in the index but its description seems wrong, route by what the catalog says — the user can run /skill-builder route index to refresh.

---

Grounding

• references/index.md — auto-generated catalog of installed skills. Regenerate with /skill-builder route index.