skills/thinking-tools/SKILL.md
Use when facing a decision, unclear or recurring problem, system behavior question, communication challenge, or when generating novel solutions — loads structured thinking frameworks
npx skillsauth add athal7/dotfiles thinking-toolsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Given a situation, identify the right framework category, read the relevant file, and apply it.
| Category | When to use | File |
|----------|-------------|------|
| Problem framing & root cause | Problem is unclear, recurring, or needs reframing | frameworks/problem.md |
| Decision making | Choosing between options, calibrating effort, prioritizing | frameworks/decisions.md |
| Systems thinking | Understanding why a system behaves the way it does | frameworks/systems.md |
| Communication | Writing clearly, giving feedback, resolving conflict | frameworks/communication.md |
| Creative problem solving | Generating novel solutions, exhausted obvious approaches | frameworks/creative.md |
Read the user's situation and pick the best-fit category. If a problem spans two categories (e.g. a decision about a system), read both files.
If the user names a specific framework (e.g. "use inversion" or "cynefin"), go straight to the relevant file — don't re-route.
Use the Read tool on the relevant file path:
~/.agents/skills/thinking-tools/frameworks/problem.md~/.agents/skills/thinking-tools/frameworks/decisions.md~/.agents/skills/thinking-tools/frameworks/systems.md~/.agents/skills/thinking-tools/frameworks/communication.md~/.agents/skills/thinking-tools/frameworks/creative.mdEach file contains multiple frameworks. Pick the most relevant one and apply it. If two frameworks complement each other (noted in "Related Tools"), apply both.
development
Zoom meeting captions — file locations and format
tools
macOS dictation custom vocabulary — sync knowledge base names and terms to the system spelling dictionary
testing
Look up people, projects, products, and decisions locally first: contact info (email, Slack ID, GitHub handle), titles and teams, project/product status, who works on what, and past decisions. Check before searching Slack, email, calendar, or GitHub — this is the first stop for any contact detail, project context, or decision-history question.
testing
Communication style, audience awareness, and AI-authorship markers for human-facing prose — load when composing chat messages, review comments, merge request descriptions, emails, doc bodies, or ticket descriptions