route
Manually route a query to the optimal Claude model (Haiku/Sonnet/Opus)
What this skill does
# 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 in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.