メニュー
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>
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Institutional memory for your project. Commands: record, consult, review. Usage: /awareness-ledger [command] [args]
Evaluate code to prevent common AI coding mistakes — dead code, duplication, complexity hotspots, reinvented helpers, leftover scaffolding. Two functions plus a pre-write advisor. Use after writing or editing code, when asked to review code quality, clean up the codebase, find unused code, find duplicates, check complexity, or evaluate what an AI just wrote. Commands: review (post-write), sweep (full codebase).
Create, audit, optimize Claude Code skills. Commands: skills, list, new, strip, optimize, agents, hooks, verify, inline, ledger, cascade, checksums, convert, shell-safety, route, backup, restore
Evaluate text for AI-generated signatures (AI tells) — em-dash overuse, rhetorical colons, pipeline artifacts, hedging cadence, sycophancy leakage — before it ships. Use when reviewing, scrubbing, or finishing written/communication output. Commands: scan (mechanical), evaluate (judgment-class), scrub (bounded fix loop).
| 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 |
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.
/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/skill-builder route index to generate it."→ 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:
→ 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.[1m]/[200k], lowercase). IF the dominant hemisphere's preferred model ≠ the active model → /route is the ONE door allowed to ask: print this and STOP — do NOT announce or dispatch until the user replies. Format: "Lane check — this job is [creative/analytical] work (preferred: [preferred-model-id]), but this session is on [active-model-id]. Route can't switch the model itself — switch by entering /model [preferred-model-id] then type continue, or type continue to proceed as-is." /route can NEVER switch the model itself; only the human /model command can. Off-hemisphere steps inside the dispatched workflow are NOT re-asked — they delegate to lane-pinned excursion agents (the rest on the agents). This single ask covers the WHOLE endeavor: route having ASSESSED the lane this turn IS the coverage signal (whether it asked, matched silently, or was suppressed) — the dispatched skill's own Model-Lane Preflight sees route's coverage and stays silent, as do skills it chains. Headless / non-interactive → skip this clause silently and dispatch. (Route-door ask ONLY; hand-run skills stay advisory-only — the No-Switch-Prompt directive's route-dispatch clause is superseded newest-wins by the 2026-06-07 route-ask directive.)/route again with the follow-up task description via Skill. Do NOT freelance the next step.references/index.md is canonical. Only dispatch to skills present there — except per clause 9(a)'s disk-evidence fallback./skill-builder like any catalog row, under three hard rules: (a) NEVER dispatch dev — dev mode is reserved for manual, user-typed /skill-builder dev … invocations ONLY. Never synthesize the dev prefix, and never pass one through: IF the routed ask carries a dev token as a skill-builder mode (the ask begins with dev, or requests dev-mode / self-targeted maintenance work) → STOP; do NOT dispatch to skill-builder at all — not even with dev stripped (stripping silently alters the ask). Print verbatim: "Dev mode is reserved for manual invocation. Type /skill-builder dev … yourself." An ask targeting skill-builder ITSELF surfaces skill-builder's Self-Exclusion refusal verbatim; direct user-typed /skill-builder invocation is the always-legal maintenance hatch and never requires routing. (b) Risk tiering: IF the resolved work is high-risk (audit --execute, optimize, route embed, convert, reconcile --execute, strip) AND the active model is not the analytical brain → emit a one-line analytical-brain advisory (NOT clause 2's blocking ask — high-risk skill-builder maintenance never blocks) before dispatch; low-risk additive work (inline, new, skills, list, verify, checksums, lane-status) dispatches on the current model with a one-line advisory. (c) The skill-creation decision belongs to skill-builder: hand the user's VERBATIM ask through — never pre-decide modify-vs-create..claude/skills/*/SKILL.md; IF a skill file exists on disk whose frontmatter name: exactly matches a plausible candidate missing from the catalog → dispatch to it (the file on disk is the evidence; memory never is) and advise: "stale index — run /skill-builder route index".
(b) Skill-creation ask (the user wants a new capability that should be a skill, or asks to make/build/create one) → offer via AskUserQuestion: modify /[closest-match] / build a new skill / cancel — on either build choice, dispatch the VERBATIM ask to /skill-builder (its intent-router owns the modify-vs-create decision; clause 8 applies).
(c) Plain freeform work (no skill fits, nothing to create): lane-classify the TASK ITSELF — apply the signal vocabulary of .claude/skills/skill-builder/references/model-lanes.md § Advisory Lane Suggestion to the ask. Research signals or AMBIGUOUS resolve to the analytical (everything-else) brain — the default; it never prompts. ONLY clear creative signals run clause 2's ask toward the creative brain. Then proceed with the most direct manual approach and note the gap — the user may want to register a skill./route again for follow-ups./route does NOT route to itself. If asked to dump the index, read references/index.md and return it./skill-builder route index to refresh./skill-name …) is always fine — every lane-declared skill carries its own slim Model-Lane Preflight, so hand-runs stay lane-aware without the door. Direct /skill-builder invocation is the always-legal maintenance hatch; recovery from a broken index or a damaged /route never depends on routing./skill-builder route index.