skill-routerlisted

Route non-trivial Codex tasks to the right local execution lane and capability set. Use when Codex needs to decide between direct execution, a local skill, an enabled plugin, or an MCP/tool surface; when the user asks which skill or workflow to use; when you want to inspect the local Codex inventory; or when a task needs a compact lane + capability + verification recommendation before work begins.
hussi9/skill-router · ★ 9 · AI & Automation · score 79

Install: claude install-skill hussi9/skill-router

# Skill Router Use this skill to make Codex routing environment-aware instead of guess-based. ## Quick Start 1. Classify the task into a lane: - `direct` - `broken` - `build` - `operate` - `review` - `plan` 2. Run `scripts/scan_codex_inventory.py` to inspect local skills, plugins, and MCP servers. 3. Match the task against the most specific local capability first. 4. Return a compact recommendation using the routing contract in `references/routing-contract.md`. ## Lane Selection | Lane | Examples | Default Reasoning | Default Thinking | |------|----------|-------------------|------------------| | `direct` | trivial read, one command, factual answer | fast | none | | `broken` | bug, regression, crash, failing test, broken build | standard | think | | `build` | new feature, component, integration, workflow | standard | think | | `operate` | refactor, automate, configure, document, deploy | standard | none | | `review` | code review, risk review, security review | standard | think-hard | | `plan` | broad, ambiguous, multi-stage, scope decisions | frontier | **ultrathink** | Escalate to `frontier` reasoning + `ultrathink` for: production incidents, auth/permissions changes, architecture decisions where rollback is expensive. If a task spans multiple lanes, choose the first critical lane and note the downstream chain. ## Capability Resolution Prefer, in order: 1. repo instructions already in force 2. local Codex skills 3. enabled plugins 4. configured M