model-complexity-routerlisted

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.
Abhillashjadhav/AI-PM-essential-skills · ★ 2 · AI & Automation · score 58

Install: claude install-skill Abhillashjadhav/AI-PM-essential-skills

# Model Complexity Router Classify a concrete task, recommend the right Claude model tier, and optionally delegate execution to a subagent pinned to that tier. ## Why this exists The main session's model cannot be programmatically switched — no hook, skill, or API changes it mid-session. What IS possible: (a) a documented recommendation the user acts on via `/model`, or (b) delegation to a subagent whose frontmatter pins a model. This skill does both and says so honestly. ## Step 1 — Detect the trigger mode Every time the user hands over a substantial task — a concrete thing to build, fix, write, or execute — this fires silently in the background, in parallel with doing the task. It never blocks or delays the response. Two modes: - **Direct ask** ("which model should I use", "is this an Opus task", etc.) → full scored breakdown (Step 3a). - **Task handoff** (any other substantial task, proactively) → silent score, one compact line (Step 3b). If the user gave no concrete task at all (e.g., "which model is best generally?"), stop and ask for the specific task — never classify hypotheticals. Fire once per distinct task: once a line or block has been shown for a task, do not re-emit on every subsequent message about that same task — only when a new, distinct task is handed over. ## Step 2 — Score against the rubric Score the task on four dimensions, each 0–2: | Dimension | 0 | 1 | 2 | |---|---|---|---| | **Scope** | Single file/artifact, cosmetic | One feature, few file