thinking-model-router
The right thinking skill is unclear and you would otherwise guess or stack tools.
Going through the checklist
What it does
Core rule: Prefer NONE or one primary skill. Route by mechanism fit, not habit. Combine only when roles are distinct and necessary.
What it can touch
No script files in its folder
Its folder holds text, not programs. It changes how your AI works; it does not bring code of its own.
How we know
Listed the one file in the skill’s folder on GitHub; none is a script or program.
No known risk pattern found
Launch7’s automated check read all 1 text files in this skill and matched none of its risk patterns. This is not a guarantee: a check like this can miss new or disguised tricks, and the author can change the files after the check.
How we know
Read 2026-10-05, commit 7b8fece by pipeline/trust/analyze.py — 40+ patterns for hidden text, prompt injection, downloads that run, credential access and more. It reads; it never runs the skill.
Recently maintained
Its repository has had changes recently.
How we know
Last push to tjboudreaux/cc-thinking-skills: 2026-08-07 (59 days before the scan).
Read automatically from the skill’s own files on GitHub on 5 Oct 2026. Launch7 does not run or manually review skills: this lists what the check saw, and nothing here means “safe”. How we check
Add it to your AI
Supported. Upload it once in Claude’s settings. Works on every plan, including Free.
Built in your browser from the SKILL.md on GitHub — nothing passes through Launch7.
In Claude, open Customize → Skills, press +, then Create skill → Upload a skill, and choose the .zip.
Make sure code execution is switched on (Settings → Capabilities). Skills need it.
Start a new chat and ask for the job in your own words — Claude picks the skill up when it fits.
How Claude does this: support.claude.com · checked 28 Sep 2026 · “Supported” means documented by the vendor; Launch7 has not run it end to end
More from tjboudreaux
All from this publisher →- thinking-effectuation
The market, technology, or problem is novel enough that outcome probabilities are not trustworthy.
- thinking-first-principles
A constraint is treated as fixed ("too expensive," "impossible," "always done this way") without independent support.
- thinking-five-whys-plus
A fault is already localized to a component, path, or subsystem.
- thinking-jobs-to-be-done
Choosing what to build, cut, or prioritize when user need is unclear - Explaining low adoption of a shipped feature - Mapping competition…
- thinking-kepner-tregoe
Core rule: Diagnose deviations by testing causes against both IS and IS-NOT.
