What it does
Thinking partner skill for AI agents — 150+ mental models, orientation detection, cognitive operations. Works with Claude Code, Cursor, Windsurf, Cline, GitHub Copilot.
- Connects Instruction files the AI reads
- Account or key Not confirmed yet (README not read yet)
- Category Coding
For makers: add a badge to your README
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/skills/mattnowdev-thinking-partner)Use together with
MCP servers that connect the AI to services for the same work
Fallow
Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.
Desktop Commander
MCP server for terminal commands, file operations, and process management
Similar Skills
Same kind of work, ordered like the Skills list
| This one thinking-partner | rea | andrej-karpathy-skills | graphify | MoneyPrinterTurbo | |
|---|---|---|---|---|---|
| Maker | mattnowdev | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skills | 1 | 1 | 1 | 1 | 1 |
| GitHub stars | 229 | 463,670 | 233,682 | 148,887 | 143,987 |
| Last code change | Apr 1, 2026 | Nov 17, 2026 | Apr 20, 2026 | Nov 17, 2026 | Nov 16, 2026 |
| License | MIT | MIT | – | Apache-2.0 | MIT |
1 skills (instruction sets) by mattnowdev that an AI reads and follows · not an MCP server
How a Skill differs from MCP
MCP = the hands
Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.
Skill = the manual
A text file that teaches the AI how to do a task. It connects to nothing.
Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.
Works with
Claude CodeCursorGitHub CopilotWindsurf
From the maker’s README and the folders in the repo
Install
Is it safe?
- Who made it
GitHub account mattnowdev (person), 12 years old
- Use and upkeep
★ 229 stars, few users so far · code last changed Apr 1, 2026
- Any scripts?
No, plain text files the AI reads and follows
- Uses the internet?
No scripts, so it does not go online by itself
- Changes machine-wide settings?
No hooks or writes to machine settings found
Checked automatically from the repo files at commit ce95b62 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
First: which AI do you use?
Pick your app and this page shows only how to install it there
Option 1Upload to claude.ai (web and app)
Uploading to claude.ai would fail: the description is over 200 characters (837). Use "Let the AI install it" instead
Option 1Let Claude Code install it
Copy this sentence and paste it into a Claude Code chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Restart Claude Code, then type /thinking-partner or ask for a matching task and Claude picks it up
Checked against official docs Nov 12, 2026 · Source: code.claude.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
The maker’s recommended way
Install Node.js (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
node -v- A version number such as v26.13.1 = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Checking the commands · copy buttons appear once they pass
Copied from the maker’s README; it downloads and runs the maker’s code
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.claude/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
Checking the commands · copy buttons appear once they pass
Restart Claude Code, then type /thinking-partner or ask for a matching task and Claude picks it up
ChatGPT desktop app
The ChatGPT desktop app has Codex built in, and Codex reads skills from ~/.agents/skills
Option 1Let ChatGPT install it
Open Codex in the ChatGPT desktop app and paste this sentence into the chat
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Option 2Put the folder there yourself
Put the thinking-partner folder at ~/.agents/skills/thinking-partner
~ is your home folder ($HOME)
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.agents/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
Checking the commands · copy buttons appear once they pass
After installing
- ChatGPT desktop app: open Skills in the sidebar to see that the skill is there
- To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
- Codex picks up newly installed skills by itself; if one does not show up, restart Codex
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
ChatGPT on the web and mobile
Skills you install yourself do not work here; only skills that come with a plugin from the directory
To use this skill with ChatGPT, use the ChatGPT desktop app as above
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
Option 1Let Codex install it
Copy this sentence and paste it into a Codex chat · Works in Codex inside the ChatGPT desktop app, Codex CLI and the IDE extension
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex picks up newly installed skills by itself; if one does not show up, restart Codex · To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.agents/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
Checking the commands · copy buttons appear once they pass
Restart Codex, then ask for a matching task; Codex lists the skill
Option 1Let Cursor install it
Copy this sentence and paste it into a Cursor chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
In Cursor’s Agent chat, type / and pick thinking-partner
Checked against official docs Nov 12, 2026 · Source: cursor.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.cursor/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
Checking the commands · copy buttons appear once they pass
In Cursor’s Agent chat, type / and pick thinking-partner
Option 1Let the AI install it
For other apps that read skills. The sentence gives the paths for Claude Code, Codex and Cursor so the AI picks the one for your app · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs Nov 12, 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com
For Terminal users
Other apps that support Agent Skills (such as Gemini CLI or GitHub Copilot) use different folders. Check that app’s guide, then copy the folder with the SKILL.md there.
Skill folders checked against the official Claude Code, Codex and Cursor guides on Nov 11, 2026
View the original SKILL.md
The text below comes from the maker’s repo, not from PopNx MCP
Showing the first 8,000 characters · Open the full file on GitHub
---
name: thinking-partner
description: >
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, inversion, pre-mortem, etc.), or asks for structured reasoning on any ambiguous, high-stakes, or complex problem. Also trigger when the user seems uncertain, is rationalizing, or is asking "am I thinking about this right?" Even casual phrases like "what do you think about..." on non-trivial topics should trigger this skill.
---
# Thinking Partner
A deterministic thinking partner that challenges assumptions and applies mental models to help users think better and clearer. Not a lecture — a sparring session.
## Core Philosophy
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:
1. **Challenging assumptions** — Surface hidden beliefs the user is treating as facts
2. **Applying mental models** — Select and deploy the right thinking frameworks for the situation
3. **Detecting orientation capture** — Notice when thinking serves comfort instead of truth
4. **Maintaining productive tension** — Hold complexity open long enough to find real insight
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.
## When This Triggers
- "Help me think through X"
- "Challenge my thinking / assumptions"
- "What am I missing?"
- "Apply [any model name] to this"
- "Play devil's advocate"
- "Stress test this idea / plan"
- "Help me decide between X and Y"
- "What are the second-order effects?"
- "Am I thinking about this right?"
- "I'm stuck on a decision"
- Any named model: SWOT, first principles, inversion, pre-mortem, 5 Whys, etc.
- Situations where user seems stuck, rationalizing, or facing genuine complexity
## Workflow
### Step 1: Understand the Situation
Before deploying any model, understand:
- **What is the user actually trying to decide, solve, or understand?**
- **What is at stake?** (career, money, relationships, identity, time)
- **What is the time horizon?** (today, this quarter, 10 years)
- **What constraints exist?** (resources, information, reversibility)
Ask ONE clarifying question if the situation is ambiguous. Do not barrage with questions. If you have enough context, move directly to Step 2.
### Step 2: Detect Thinking Orientation
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?"
### Step 3: Select Mental Models
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:
- Inversion ("What would guarantee the wrong choice?")
- Second-Order Thinking ("And then what?")
- Opportunity Cost ("What are you giving up?")
- Regret Minimization ("Which choice minimizes regret at 80?")
- Reversibility Test ("Is this a one-way or two-way door?")
- Decision Matrix (weighted criteria comparison)
- Pre-Mortem ("It's a year later and this failed — why?")
- Preserving Optionality ("Does this close doors I may want open?")
- Asymmetric Risk / Convexity ("Capped downside, uncapped upside?")
- 10/10/10 Rule ("How will I feel in 10 minutes, 10 months, 10 years?")
- Circle of Concern vs Influence ("Can I actually affect this?")
- Skin in the Game ("Does the advisor bear consequences?")
- Satisficing vs Maximizing ("Is good enough better than optimal here?")
**For problems**, consider:
- First Principles ("What do we know to be fundamentally true?")
- Root Cause / 5 Whys ("Why? → Why? → Why? → Why? → Why?")
- Fishbone / Ishikawa (categorize causes systematically)
- Constraint Analysis / Theory of Constraints ("What's the real bottleneck?")
- Reframing ("What if this isn't the problem at all?")
- MECE Decomposition ("Are my categories gap-free and non-overlapping?")
- Hypothesis-Driven Solving ("What's the fastest test to confirm or kill this?")
- Bright Spots Analysis ("Where is this already working?")
- Local vs Global Optima ("Am I stuck on a local peak?")
**For strategy and planning**, consider:
- Scenario Planning ("What are 3 plausible futures?")
- SWOT Analysis (Strengths, Weaknesses, Opportunities, Threats)
- Porter's Five Forces (competitive landscape)
- Red Team Analysis ("How would an adversary defeat this plan?")
- Margin of Safety ("What buffer exists if assumptions are wrong?")
- The Map is Not the Territory ("Where might our model diverge from reality?")
- Chesterton's Fence ("Do I understand why this exists before removing it?")
- Lindy Effect ("How long has this survived? That predicts its future.")
- Tragedy of the Commons ("Who owns the downside of this shared resource?")
- Principal-Agent Problem ("Are the agent's incentives aligned with mine?")
- Winner-Take-All / Power Laws ("Do small advantages compound into dominance?")
- Switching Costs / Lock-in ("How painful is it to leave?")
**For evaluating claims and evidence**, consider:
- Bayesian Updating ("How should this evidence shift our confidence?")
- Falsifiability ("What evidence would disprove this?")
- Base Rate Neglect ("What's the prior probability before this specific case?")
- Survivorship Bias ("Are we only looking at winners?")
- Correlation vs Causation ("Is there a causal mechanism, or just co-occurrence?")
- Selection Bias ("Who's missing from this dataset?")
- Gambler's Fallacy ("Are these events actually dependent?")
- Thinking in Bets ("Was the process sound, regardless of outcome?")
- Counterfactual Thinking ("What if this one variable had been different?")
**For understanding systems and dynamics**, consider:
- Feedback Loops ("Is this self-reinforcing or self-correcting?")
- Emergence ("What behavior arises from the interaction of parts?")
- Leverage Points ("Where does a small change produce a large effect?")
- The Red Queen Effect ("Are we running just to stay in place?")
- Ecosystems Thinking ("Who else is affected and how do they respond?")
- Stocks and Flows ("What is accumulating or depleting, and at what rate?")
- Delays ("How long before this action's effect becomes visible?")
- Critical Mass / Tipping Points ("Is there a threshold that flips the system?")
- Hysteresis / Path Dependence ("Can we actualDiscussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
From GitHub
- GitHub stars
- 229
- Maker
- mattnowdev
- License
- MIT
- Last code change
- Apr 1, 2026
- SKILL.md files in the repo (including translated copies and templates)
- 1
- Topics
- agent-skills, claude-code, critical-thinking, cursor, decision-making, mental-models, thinking