smart-model-routing

Solid

Dynamic model selection based on task complexity scoring. Replaces static model mappings with a weighted signal system that picks Opus, Sonnet, or Haiku-class speed per task. Works with agent-assignment-matrix.md.

AI & Automation 552 stars 45 forks Updated 6 days ago MIT

Install

View on GitHub

Quality Score: 91/100

Stars 20%
91
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Smart Model Routing Dynamic model selection based on task complexity. Never use a sledgehammer where a scalpel will do — and never use a scalpel where you need a sledgehammer. ## Core Philosophy Static model assignments ("always use Sonnet for code") waste money on trivial tasks and produce poor results on complex ones. This skill scores every task across three signal categories and routes it to the appropriate model tier automatically. **Default rule: inherit parent model.** Only override when the score clearly warrants a different tier. Never specify a model without a scoring reason. --- ## Signal Categories Three weighted categories are evaluated. Their scores combine into a single complexity score (0-20 typical range, can exceed). ### Category 1: Lexical Signals (weight: 0.3) Analyze the raw text of the request. #### Architecture Keywords (+3 each) Trigger words that indicate high-stakes design work: - "redesign", "overhaul", "new system", "migrate", "refactor entire", "rewrite" - "architecture", "from scratch", "greenfield", "new service", "platform" Example: "Redesign the authentication system" → +3 #### Risk Keywords (+2 each) Domains where mistakes are expensive or irreversible: - "production", "security", "auth", "authentication", "authorization" - "payment", "billing", "database migration", "data loss", "rollback" - "GDPR", "compliance", "PII", "encryption", "secrets", "credentials" Example: "Update the payment processing logic" → +2 #### Simple Keyw...

Details

Author
vibeeval
Repository
vibeeval/vibecosystem
Created
8 months ago
Last Updated
6 days ago
Language
C#
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

model-routing

Complexity-based routing of tasks across four model tiers — frontier (T3), strong workhorse (T2), fast executor (T1), cheapest recon (T0). Use when planning any multi-step work, when deciding which subagent should execute a task, when writing a dispatch brief, or when an executor fails and escalation is needed.

1 Updated 1 weeks ago
alebgl77
AI & Automation Listed

model-complexity-router

Use this skill proactively whenever the user hands over any substantial task to execute — not just when they ask about models. Use this skill when a concrete work item is handed over by silently scoring it and emitting one compact line noting the current model, the score, the recommended tier, and the potential savings, without blocking or delaying the task itself. Also fires on direct questions like "which model should I use", "is this an Opus task", "route this to the right model", "am I overpaying for this", "should I use Haiku or Sonnet for this" — those get the full scored breakdown instead of the compact line. Fires once per distinct task, not on every follow-up message within that same task. Do NOT fire on pure knowledge questions, vendor comparisons, hypotheticals with no concrete work item, or repeatedly while a task is still in progress.

9 Updated 3 weeks ago
Abhillashjadhav
AI & Automation Listed

model-complexity-router

Build-stage skill: scores a concrete task on a four-axis complexity rubric and recommends the right Claude tier (Haiku/Sonnet/Opus). Use when the user asks which model a task needs — 'which model should I use', 'is this an Opus task', 'am I overpaying for this', 'route this to the right model' — giving the full scored breakdown; also use proactively on any substantial task handoff, emitting one compact line without delaying the task. Fires once per distinct task. Do NOT use for vendor comparisons, knowledge questions, pricing lookups with no task, or repeatedly on follow-up messages about an already-scored task.

2 Updated 3 weeks ago
Abhillashjadhav