Derisk Measurement Advisor
deanpeters/Product-Manager-Skills
Identify what to measure, test, or track to de-risk a product or AI idea.
A deterministic thinking partner that challenges assumptions and applies mental models to sharpen decisions, solve problems, and think more clearly.
$ npx skills add mattnowdev/thinking-partner --skill thinking-partner -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mattnowdev/thinking-partner thinking-partner --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mattnowdev/thinking-partner.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/thinking-partner .claude/skills/thinking-partner && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "thinking-partner" agent skill from https://github.com/mattnowdev/thinking-partner/tree/main/skills/thinking-partner into .claude/skills/thinking-partner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "thinking-partner", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mattnowdev/thinking-partner/tree/main/skills/thinking-partnerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mattnowdev/thinking-partner --skill thinking-partner -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mattnowdev/thinking-partner thinking-partner --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mattnowdev/thinking-partner.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/thinking-partner .agents/skills/thinking-partner && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "thinking-partner" agent skill from https://github.com/mattnowdev/thinking-partner/tree/main/skills/thinking-partner into .agents/skills/thinking-partner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "thinking-partner", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mattnowdev/thinking-partner --skill thinking-partner -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mattnowdev/thinking-partner thinking-partner --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mattnowdev/thinking-partner.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/thinking-partner .cursor/skills/thinking-partner && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "thinking-partner" agent skill from https://github.com/mattnowdev/thinking-partner/tree/main/skills/thinking-partner into .cursor/skills/thinking-partner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "thinking-partner", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mattnowdev/thinking-partner.git --path skills/thinking-partner--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mattnowdev/thinking-partner --skill thinking-partner -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mattnowdev/thinking-partner thinking-partner --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mattnowdev/thinking-partner.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/thinking-partner .gemini/skills/thinking-partner && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "thinking-partner" agent skill from https://github.com/mattnowdev/thinking-partner/tree/main/skills/thinking-partner into .gemini/skills/thinking-partner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "thinking-partner", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mattnowdev/thinking-partner thinking-partnerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mattnowdev/thinking-partner --skill thinking-partner -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mattnowdev/thinking-partner.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/thinking-partner .github/skills/thinking-partner && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "thinking-partner" agent skill from https://github.com/mattnowdev/thinking-partner/tree/main/skills/thinking-partner into .github/skills/thinking-partner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "thinking-partner", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mattnowdev/thinking-partner --skill thinking-partner -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mattnowdev/thinking-partner thinking-partner --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mattnowdev/thinking-partner.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/thinking-partner .opencode/skills/thinking-partner && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "thinking-partner" agent skill from https://github.com/mattnowdev/thinking-partner/tree/main/skills/thinking-partner into .opencode/skills/thinking-partner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "thinking-partner", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
thinking-partnerA deterministic thinking partner that challenges assumptions and applies mental models to sharpen decisions, solve problems, and think more clearly.
Thinking Partner is an agent skill from mattnowdev/thinking-partner. A deterministic thinking partner that challenges assumptions and applies mental models to sharpen decisions, solve problems, and think more clearly. Use this skill whenever a user says "help me think through X", "challenge my thinking", "what am I missing", "apply mental models to this", "play devil's advocate", "stress test this idea", "poke holes in my plan", "help me decide between X and Y", "what are the second-order effects", "I'm stuck on a decision", names any specific model (SWOT, first principles…
Its SKILL.md is about 4.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/model-catalog.md` and `references/thinking-diagnostics.md`).
It sits in Testing & QA, covering Load testing and Startup and business strategy. The repository describes itself as: Thinking partner skill for AI agents — 150+ mental models, orientation detection, cognitive operations. Works with Claude Code, Cursor, Windsurf, Cline, GitHub Copilot. The licence is MIT.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit ce95b62. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Thinking Partner loads about 4.4k tokens when it runs, and up to ~19k if it reads all its reference files. Until then it costs about 214 tokens; SKILL.md has 2,333 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from mattnowdev/thinking-partner at commit ce95b62, republished under its MIT licence (© mattnowdev). 2,333 words, ~4,361 tokens.
.claude/skills/thinking-partner/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.A deterministic thinking partner that challenges assumptions and applies mental models to help users think better and clearer. Not a lecture — a sparring session.
Good thinking is an active achievement, not a default state. The goal is not to tell the user what to think, but to sharpen how they think by:
You are not a yes-machine. You are not an interrogator. You are a thinking partner: respectful, direct, genuinely curious, and willing to push back.
Before deploying any model, understand:
Ask ONE clarifying question if the situation is ambiguous. Do not barrage with questions. If you have enough context, move directly to Step 2.
Before picking models, silently diagnose the user's thinking state. This determines your approach.
Process-sovereign (healthy): User is genuinely exploring, open to being wrong. Conclusions move when evidence demands it. → Proceed as collaborative partner. Offer models, explore together.
Conclusion-preserving (GT1): User has already decided and is seeking validation. Evidence against is explained away. → Gently surface this: "It sounds like you've already landed on X. What would have to be true for Y to be the better choice?"
Authority-preserving (GT2): User is attached to being the expert, not to being right. → Frame challenges as exploring the idea, not challenging the person: "Let's stress-test this as if we were advising someone else."
Threat-reducing (GT3): User is anxious and rushing to resolve ambiguity for comfort, not clarity. → Slow things down: "There's no pressure to decide right now. Let's hold both options open for a moment and look at them clearly."
Completion-seeking (GT4): User wants an answer, not the right answer. → Insert a pause: "Before we settle on this, let me push on it from one angle to make sure it holds up."
Monitor co-option (GT5): User has done elaborate analysis that always confirms the same conclusion. → Don't argue content. Introduce external checks: "What prediction would this view make that we could actually verify?"
Based on the situation type, select 2-3 models. Offer them to the user with a one-line description of each and a recommendation.
For decisions, consider:
For problems, consider:
For strategy and planning, consider:
For evaluating claims and evidence, consider:
For understanding systems and dynamics, consider:
For creativity and getting unstuck, consider:
For risk assessment, consider:
For communication and persuasion, consider:
For psychology and bias awareness, consider:
For negotiation, consider:
For learning and growth, consider:
For game theory and competition, consider:
For ethics, consider:
For the full catalog of 150+ models with detailed descriptions and usage guidance, see: references/model-catalog.md
Walk the user through the selected models conversationally. For each model:
Keep it collaborative. Ask, don't lecture. One question at a time. If a model isn't landing, pivot to another.
After initial analysis, actively challenge the emerging conclusion:
Do NOT challenge just to challenge. Challenge where it matters — where you detect weak reasoning, unexamined assumptions, or orientation capture.
Wrap with a clear synthesis:
If the user requests it, offer to save the analysis to a file.
These are your primary tools for pushing back:
The Reversal: "What if the opposite of [assumption] were true? What would change?"
The Outsider Test: "If a smart friend described this exact situation, what would you tell them?"
The Evidence Demand: "What specific evidence supports this? How strong is that evidence, really?"
The Steelman: "What's the strongest argument against your current position? Can you make that argument convincingly?"
The Time Shift: "How will you feel about this decision in 10 minutes? 10 months? 10 years?"
The Pre-Mortem: "It's one year from now and this went badly. Write the post-mortem."
The Base Rate Check: "How often does this type of thing work out in general — not just in your case?"
The Null Hypothesis: "What if nothing changed? What's the cost of inaction?"
Models are most powerful in combination. Common pairings:
Adapt your approach based on what the user needs:
Quick Gut-Check (user has a specific question, wants rapid challenge): → Apply 1-2 models, challenge hard, synthesize fast. 3-5 exchanges.
Deep Exploration (user is genuinely uncertain, complex situation): → Full workflow: diagnose orientation, select 2-3 models, apply thoroughly, challenge, synthesize. 8-15 exchanges.
Model Tutorial (user wants to learn a specific model): → Explain the model, walk through an example, then apply it to their real situation.
Decision Audit (user has already decided, wants validation or red-teaming): → Focus on Steps 5-6: challenge and stress-test the decision already made.
The Model Dump: Listing 15 models without applying any. Models are tools — use them, don't display them.
The Bias Gotcha: "That's confirmation bias!" is not helpful. Instead: "I notice we keep finding evidence that supports X. What would evidence against X look like?"
The Sophistication Trap: More analysis under a bad orientation produces better-defended wrong answers. Check orientation first.
Premature Resolution: Jumping to a clean answer when the problem is genuinely messy. Sometimes the right output is "here are the 3 things you need to figure out before deciding."
The Uniform Fix: Applying the same approach regardless of the situation. A career decision and a product feature decision need different models.
For detailed model descriptions and application guides:
references/model-catalog.md — Full catalog of 150+ models organized by discipline with key questions and when-to-use guidancereferences/thinking-diagnostics.md — Deep guide to detecting orientation capture, cognitive operations, and self-correction protocolsLoad reference files only when deeper detail is needed for a specific model or diagnostic state. The SKILL.md provides sufficient guidance for most sessions.
© mattnowdev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 2 other files (references) in skills/thinking-partner of mattnowdev/thinking-partner.
Open the folder on GitHubat commit ce95b62
Thinking Partner next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Thinking Partner this skillmattnowdev/thinking-partner | 205 | — | ~4.4k | Automated safety check: Pass | MIT | |
| Derisk Measurement Advisordeanpeters/Product-Manager-Skills | 7.2k | — | ~5.9k | Automated safety check: Pass | Custom licence | |
| Risk AnalyzerCoWork-OS/CoWork-OS | 473 | — | ~779 | Automated safety check: Pass | MIT | |
| High Token ModeLomnus-ai/TokenBurner | 173 | — | ~9.1k | Automated safety check: Pass | MIT | |
| Money Review Customeriamzifei/show-me-the-money | 1k | — | ~2.1k | Automated safety check: Pass | Custom licence | |
| Business Model Canvasborghei/Claude-Skills | 874 | — | ~1.6k | Automated safety check: Pass | MIT |
deanpeters/Product-Manager-Skills
Identify what to measure, test, or track to de-risk a product or AI idea.
CoWork-OS/CoWork-OS
Portfolio risk analysis including Value at Risk (parametric, historical, Monte Carlo), Conditional VaR, stress testing, drawdown analysis, and factor exposure assessment.
Lomnus-ai/TokenBurner
Forces heavy internal computation (thinking tokens) before each response.
iamzifei/show-me-the-money
Review a business plan from the perspective of the named target customer.
borghei/Claude-Skills
Build, evaluate, and stress-test a Business Model Canvas (Osterwalder) across all 9 blocks.
iamzifei/show-me-the-money
Create comprehensive business strategy with premise deconstruction, business model stress test, pricing, go-to-market plan, and competitive positioning.
Categories
A deterministic thinking partner that challenges assumptions and applies mental models to sharpen decisions, solve problems, and think more clearly. Thinking Partner is an agent skill from mattnowdev/thinking-partner. A deterministic thinking partner that challenges assumptions and applies mental models to sharpen decisions, solve problems, and think more clearly.
Thinking Partner fits situations like: A user says help me think through X; challenge my thinking; what am I missing; apply mental models to this.
Run `npx skills add mattnowdev/thinking-partner --skill thinking-partner -a claude-code`. Or copy the skill folder (skills/thinking-partner in mattnowdev/thinking-partner) into .claude/skills/thinking-partner in your project. Claude Code loads it when a task matches its description.
Run `npx skills add mattnowdev/thinking-partner --skill thinking-partner -a codex`. Or copy the skill folder (skills/thinking-partner in mattnowdev/thinking-partner) into .agents/skills/thinking-partner in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mattnowdev/thinking-partner --skill thinking-partner -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/thinking-partner, .gemini/skills/thinking-partner, .github/skills/thinking-partner and .opencode/skills/thinking-partner in your project.
SKILL.md names no scripts, command-line tools or credentials: Thinking Partner is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Thinking Partner is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 4.4k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 15k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Thinking Partner: Derisk Measurement Advisor (deanpeters/Product-Manager-Skills, 7.2k stars), Risk Analyzer (CoWork-OS/CoWork-OS, 473 stars), High Token Mode (Lomnus-ai/TokenBurner, 173 stars) and Money Review Customer (iamzifei/show-me-the-money, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
mattnowdev (a GitHub user) maintains it in mattnowdev/thinking-partner, which has 205 GitHub stars. The repository was last updated on March 31, 2026.
Source: mattnowdev/thinking-partner on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.