Thinking Model Router
When unsure which thinking skill fits, map domain and problem type, then return NONE or...
Install
npx skills add tjboudreaux/cc-thinking-skills --skill thinking-model-router -g -a claude-code -y- Repository
- tjboudreaux/cc-thinking-skills1.7k
- Category
- Engineering
- Updated
- 3mo ago
- License
- MIT
- Context cost
- Lightabout 1,463 tokens
- Runs scripts
- No, instructions only
What it does
When unsure which thinking skill fits, map domain and problem type, then return NONE or one primary skill by default (at most three complementary).
Model Router
Core rule: Prefer NONE or one primary skill. Route by mechanism fit, not habit. Combine only when roles are distinct and necessary.
When to Use
- The right thinking skill is unclear and you would otherwise guess or stack tools.
- Several catalog skills seem plausible and you need a single primary (or explicit NONE).
- High-stakes work where a wrong frame is costly and a quick domain×type match helps.
When NOT to Use
- The match is already known or obvious ("where's the bottleneck?" → theory-of-constraints), invoke that skill directly; do not route for show.
- The task is routine implementation with no analytical unknown, reason directly (NONE).
- You are mid-execution of an agreed plan and only need the next concrete step.
- The ask is outside this catalog (pure coding syntax, tool ops with no judgment call), NONE.
Invoking a Model (Skill IDs)
The router outputs bare slugs (e.g. id: five-whys-plus). Invoke a routed skill with the Skill tool using the exact ID thinking-skills:thinking-<slug>, never invent a slug not cited in Procedure. NONE means no invocation.
