agent-routerlisted

# Agent Router A meta-router. Given a task, it inventories every skill and subagent available in this session, scores them against the task, and routes to the best one. ## When to use - The user is unsure which of the many installed skills/agents fits their task. - The user explicitly asks to "route", "pick the best agent", or "find a skill for X". - Before starting a non-trivial task, to confirm a specialist exists instead of doing it generically. ## Procedure **Locate the scripts once.** Throughout, `<scripts>` is the agent-router scripts directory. Resolve it to the first that exists: `~/.claude/agent-router/scripts/` (npx install) · `./scripts/` (this repo) · the installed plugin's own `scripts/` dir. Use that prefix for every `node <scripts>/*.js` below. **Mode check (first).** If the invocation is `feedback <bad|ok|good|excellent> [note]`, skip routing and go straight to step 7 (rate the last route). Otherwise run steps 0-6 to route a task. ### 0. Update check (one line, non-blocking) Run `node <scripts>/update-check.js` and, if it prints anything, surface that single line. It's daily-cached and silent when you're current or offline — never let it block routing. ### 1. Capture the task Restate the user's task in one sentence. Note the domain (code review, research, testing, design, security, infra, data, etc.) and any constraints (language, framework, speed vs. depth). ### 2. Inventory via the retrieval index (do NOT read every skill) You may have **thousands**