route
Manually route a query to the optimal Claude model (Haiku/Sonnet/Opus)
Best use case
route is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. Manually route a query to the optimal Claude model (Haiku/Sonnet/Opus)
Manually route a query to the optimal Claude model (Haiku/Sonnet/Opus)
Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.
Practical example
Example input
Use the "route" skill to help with this workflow task. Context: Manually route a query to the optimal Claude model (Haiku/Sonnet/Opus)
Example output
A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.
When to use this skill
- Use this skill when you want a reusable workflow rather than writing the same prompt again and again.
When not to use this skill
- Do not use this when you only need a one-off answer and do not need a reusable workflow.
- Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/route/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How route Compares
| Feature / Agent | route | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Manually route a query to the optimal Claude model (Haiku/Sonnet/Opus)
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Manual Model Router Override automatic model selection and force a specific Claude model for your query. ## Usage ``` /route <model> <query> ``` Where `<model>` is one of: - `haiku` or `fast` - Use Haiku for simple, quick tasks - `sonnet` or `standard` - Use Sonnet for typical coding tasks - `opus` or `deep` - Use Opus for complex analysis ## Instructions Parse $ARGUMENTS to extract the model and query: 1. **Extract model** - The first word should be the model name (haiku/fast, sonnet/standard, opus/deep) 2. **Extract query** - Everything after the model name is the query to execute 3. **Validate** - If no valid model is specified, show usage help 4. **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 5. **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 ```
Related Skills
routeros-qemu-chr
MikroTik RouterOS CHR (Cloud Hosted Router) with QEMU. Use when: running RouterOS in QEMU, booting CHR images, debugging CHR boot failures, setting up VirtIO devices for RouterOS, choosing between SeaBIOS and UEFI boot, configuring QEMU port forwarding for RouterOS REST API, or selecting QEMU acceleration (KVM/HVF/TCG).
routeros-netinstall
MikroTik netinstall-cli for automated RouterOS device flashing. Use when: automating netinstall, writing scripts that invoke netinstall-cli, building netinstall tooling, understanding etherboot/BOOTP/TFTP protocols, working with RouterOS package files (.npk), using modescript or configure script, or when the user mentions netinstall, etherboot, or device flashing.
routeros-fundamentals
RouterOS v7 domain knowledge for AI agents. Use when: working with MikroTik RouterOS, writing RouterOS CLI/script commands, calling RouterOS REST API, debugging why a Linux command fails on RouterOS, or when the user mentions MikroTik, RouterOS, CHR, or /ip /system /interface paths. Scope: RouterOS 7.x (long-term and newer) only — v6 is NOT covered and accuracy for v6 problems will be low.
routeros-container
RouterOS /container subsystem for running OCI containers on MikroTik devices. Use when: enabling containers on RouterOS, setting up VETH/bridge networking for containers, managing container lifecycle via CLI or REST API, building OCI images for RouterOS, configuring container environment variables, troubleshooting container issues, or when the user mentions RouterOS container, /container, VETH, device-mode container, or MikroTik Docker.
routeros-command-tree
RouterOS command tree introspection via /console/inspect API. Use when: building tools that parse RouterOS commands, generating API schemas from RouterOS, working with /console/inspect, mapping CLI commands to REST verbs, traversing the RouterOS command hierarchy, or when the user mentions inspect, command tree, RAML, or OpenAPI generation for RouterOS.
routeros-app-yaml
RouterOS /app YAML format for container applications (7.21+ builtin app, 7.22+ custom YAML creation). Use when: writing or validating RouterOS /app YAML files, working with MikroTik container apps, building docker-compose-like definitions for RouterOS, creating /app store schemas, debugging /app validation errors, or when the user mentions /app, tikapp, or RouterOS container YAML.
nextjs-app-router-patterns
Master Next.js 14+ App Router with Server Components, streaming, parallel routes, and advanced data fetching. Use when building Next.js applications, implementing SSR/SSG, or optimizing React Server Components.
fastapi-router-py
Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.
mulerouter
Generates images and videos using MuleRouter or MuleRun multimodal APIs. Text-to-Image, Image-to-Image, Text-to-Video, Image-to-Video, video editing (VACE, keyframe interpolation). Use when the user wants to generate, edit, or transform images and videos using AI models like Wan2.6 or Nano Banana.
expo-api-routes
Guidelines for creating API routes in Expo Router with EAS Hosting
route-tester
Test authenticated routes in the your project using cookie-based authentication. Use this skill when testing API endpoints, validating route functionality, or debugging authentication issues. Includes patterns for using test-auth-route.js and mock authentication.
frontend-nextjs-app-router
Use when working with Next.js App Router tasks - creating pages in /app/, setting up dynamic routes ([id]/page.tsx), implementing nested layouts/templates (layout.tsx), optimizing Server/Client components, or building ERP role-based pages (admin/teacher/student dashboards). Auto-use for all /app/ directory operations, dynamic routing, and App Router-specific features.