route
Scannednpx machina-cli add skill aiskillstore/marketplace/route --openclawManual Model Router
Override automatic model selection and force a specific Claude model for your query.
Usage
/route <model> <query>
Where <model> is one of:
haikuorfast- Use Haiku for simple, quick taskssonnetorstandard- Use Sonnet for typical coding tasksopusordeep- Use Opus for complex analysis
Instructions
Parse $ARGUMENTS to extract the model and query:
- Extract model - The first word should be the model name (haiku/fast, sonnet/standard, opus/deep)
- Extract query - Everything after the model name is the query to execute
- Validate - If no valid model is specified, show usage help
- Route - Use the Task tool to spawn the appropriate subagent:
- haiku/fast -> spawn "fast-executor" subagent with model: haiku
- sonnet/standard -> spawn "standard-executor" subagent with model: sonnet
- opus/deep -> spawn "deep-executor" subagent with model: opus
- Return - Prefix the response with the model override info
Model Mapping
| Argument | Executor | Model |
|---|---|---|
haiku or fast | fast-executor | Haiku |
sonnet or standard | standard-executor | Sonnet |
opus or deep | deep-executor | Opus |
Examples
Force Opus for a simple question
/route opus What's the syntax for a TypeScript interface?
Result: Routes to Opus (deep-executor) regardless of query complexity.
Force Haiku for any task
/route haiku Fix the authentication bug in login.ts
Result: Routes to Haiku (fast-executor) for cost savings.
Force Sonnet explicitly
/route sonnet Design a caching system
Result: Routes to Sonnet (standard-executor).
Error Handling
If the user doesn't provide a valid model, respond with:
Usage: /route <model> <query>
Models:
haiku, fast - Quick, simple tasks (cheapest)
sonnet, standard - Typical coding tasks (default)
opus, deep - Complex analysis (most capable)
Example: /route opus Analyze the security of this authentication flow
Source
git clone https://github.com/aiskillstore/marketplace/blob/main/skills/0xrdan/route/SKILL.mdView on GitHub Overview
Manual Model Router lets you override automatic model selection by forcing a specific Claude model for a query. It routes to Haiku (fast), Sonnet (standard), or Opus (deep) by spawning the corresponding subagents. This gives you predictable performance and cost control for targeted tasks.
How This Skill Works
Parse the first word as the model name, and the rest as the query. Validate the model against haiku/fast, sonnet/standard, and opus/deep. Then spawn the matching executor: fast-executor for Haiku, standard-executor for Sonnet, or deep-executor for Opus, and prefix the response with the model override info.
When to Use It
- You know the required model for a task and want to enforce it
- Debugging or validating model routing behavior
- A task benefits from Opus for deep analysis regardless of input size
- A coding task where Sonnet is preferred for typical development work
- You need predictable latency by routing to a specific executor
Quick Start
- Step 1: Enter /route <model> <query>
- Step 2: Use one of haiku/fast, sonnet/standard, opus/deep
- Step 3: Review the prefixed response to confirm the model override
Best Practices
- Always validate the model name before routing
- Keep the model aliases up to date (haiku/fast, sonnet/standard, opus/deep)
- Include the full query after the model in the /route command
- Test routing with all three model families to verify executors
- Check the response for the model override prefix to confirm routing
Example Use Cases
- /route opus What's the syntax for a TypeScript interface?
- /route haiku Fix the authentication bug in login.ts
- /route sonnet Design a caching system
- /route haiku Fetch top 5 headlines quickly
- /route opus Analyze a multi-step data pipeline for bottlenecks
