SkillAgentSearch skills...

thinking-model-router

When unsure which thinking skill fits, map domain and problem type, then return NONE or one primary skill by default (at most three complementary).

Install / Use

npx skills add tjboudreaux/cc-thinking-skills --skill thinking-model-router

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

82/100

Supported Platforms

Universal

Tags

Our assessment of thinking-model-router

thinking-model-router scores 82/100 on our quality scale, 3372nd of 4,698 Development & Engineering skills we index.

Its SKILL.md is 5.9 KB long, split into 7 sections with 1 code example: a thorough specification that gives an agent plenty to work with.

With 1,325 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
29/30
Structure
15/20
Description
15/15
Adoption
13/20
Freshness
11/15

Maintenance, license and trust

  • The repository was last updated about 3 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.
  • Our last check on 2026-11-07 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 98/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

thinking-model-router compared with similar skills

All 4 of these similar skills score higher than thinking-model-router; compare them before choosing.

SkillScoreStarsUpdatedFormat
thinking-model-router (this skill)by tjboudreaux821.3k3mo agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md
claude-howtoby luongnv8910047.3k2d agoCLAUDE.md
lobehubby lobehub10085.6ktodayMCP Server

Frequently asked questions

How do I install thinking-model-router?
Run npx skills add tjboudreaux/cc-thinking-skills --skill thinking-model-router. The install tabs above show the steps for each supported agent.
Which AI agents does thinking-model-router work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is thinking-model-router safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 98/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is thinking-model-router still maintained?
The repository was last updated about 3 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.

name: thinking-model-router description: When unsure which thinking skill fits, map domain and problem type, then return NONE or one primary skill by default (at most three complementary). disable-model-invocation: true

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.

Procedure

  1. Short-circuit. If one skill clearly fits by mechanism, return that skill alone. If no skill clearly improves the work, return NONE and reason directly. Stop.
  2. Characterize. Record domain (coding, architecture, product, strategy, personal, abstract, risk, innovation) and problem type (diagnose, decide, understand, create, evaluate, predict, optimize). Note constraints: time, information, stakes, reversibility, complexity.
  3. Candidate by type defaults (override when constraints demand). Keep only active catalog skills:
    • Diagnose → five-whys-plus or scientific-method (kepner-tregoe if IS/IS-NOT matrix needed)
    • Decide → reversibility first; then opportunity-cost or probabilistic
    • Understand → systems (map-territory if model-vs-reality gap; cynefin if approach domain unclear)
    • Create → first-principles (triz for contradictions; effectuation for means-driven; via-negativa for remove-first)
    • Evaluate → steel-manning (socratic if assumptions/definitions are the unknown)
    • Predict → probabilistic
    • Optimize → theory-of-constraints (ooda under time pressure; bounded-rationality for search stop)
    • Risk / "what fails?" → pre-mortem or red-team; margin-of-safety for buffers
    • Product "what to build?" → jobs-to-be-done
    • Competence / durability → circle-of-competence, lindy-effect
    • Controlled hypothetical → thought-experiment
    • Multi-lens only after one primary fails a blind-spot check → model-combination
  4. Select with criteria (satisficing). Score only if 2+ candidates remain or stakes make a forced default unsafe. Rate each criterion 1–5 (1 = absent/wrong fit; 3 = usable with gaps; 5 = direct fit): problem fit (30%), available inputs (20%), time to apply (15%), stakeholder usability (15%), competence to apply correctly (20%). A route must score problem fit ≥4 and weighted total ≥3.5; otherwise return NONE. For totals within 0.25, prefer fewer inputs and shorter execution; if still tied, choose NONE unless the skills answer distinct complementary questions.
  5. Multi-skill only as exception. Add a second or third skill only when each has a distinct complementary role the primary leaves open. Cap at three. Prefer sequential over parallel. Near-neighbors and synonyms do not stack. For composition patterns, hand off to model-combination after naming the primary.
  6. Exit. State abandon signals (forced fit, ignored factors, no insight ~15 minutes). On mismatch, re-route once or fall back to NONE — never force a frame.

Domain cheat-map (primary first; still default to one or NONE):

| Domain signal | Prefer | |---------------|--------| | Bug / root cause / flaky | five-whys-plus, scientific-method, systems | | Architecture / tech choice | reversibility, systems, lindy-effect, opportunity-cost | | Feature / roadmap / engagement | jobs-to-be-done, opportunity-cost, theory-of-constraints | | Strategy / competition / growth | cynefin, systems, red-team, second-order | | Personal / career commitment | opportunity-cost, reversibility, circle-of-competence, pre-mortem | | Argument / belief update | steel-manning, probabilistic, socratic, first-principles | | Security / disaster / ruin | pre-mortem, red-team, margin-of-safety, via-negativa | | Innovation / contradiction / simplify | first-principles, triz, effectuation, via-negativa |

Output

outcome: NONE | one | multi
routes:
  - id: <primary skill id or NONE>
    role: <job this skill performs>
    unique_question: <question only this route answers>
  - id: <secondary skill id, only for multi>
    role: <distinct complementary job>
    unique_question: <distinct open question>
  - id: <tertiary skill id, only for multi>
    role: <distinct complementary job>
    unique_question: <distinct open question>
domain: <domain>
problem_type: <type>
constraints: <time/info/stakes/reversibility>
rationale: <mechanism fit in one sentence>
blind_spots: <what primary still ignores, if any>
exit: <when to abandon or re-route>

Default fill: outcome: NONE with one id: NONE route, or outcome: one with one route. Use multi only when every listed skill has a distinct role and unique question.

Verification

  • Falsify / stop: If the route is habit or familiarity rather than mechanism fit, discard and re-score or return NONE. If multi-skill entries lack distinct roles, collapse to the single best primary. If no candidate clearly helps, NONE is correct — do not invent a route.
  • Over-application guard: Do not route when the skill is already obvious. Do not return more than three skills. Do not cite deleted or non-catalog names. Do not treat the router as a prerequisite for leaf skills invoked directly.

Related Skills

View on GitHub
GitHub Stars1.3k
CategoryDevelopment
Updated3mo ago
Forks160

Languages

JavaScript

Trust signals

98/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 info