REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Thinking partner skill for AI agents — 150+ mental models, orientation detection, cognitive operations. Works with Claude Code, Cursor, Windsurf, Cline, GitHub Copilot.
제작자라면 이 코드를 README에 붙여 넣으세요. 배지는 이 페이지로 연결됩니다.
[](https://mcp.popnx.com/en/skills/mattnowdev-thinking-partner)같은 작업에서 AI를 서비스에 연결하는 MCP
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.
MCP server for terminal commands, file operations, and process management
같은 종류의 작업, Skill 목록과 같은 순서
| 이 항목 thinking-partner | rea | andrej-karpathy-skills | graphify | MoneyPrinterTurbo | |
|---|---|---|---|---|---|
| 제작자 | mattnowdev | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skill 수 | 1 | 1 | 1 | 1 | 1 |
| GitHub 별 | 229 | 463,670 | 233,682 | 148,887 | 143,987 |
| 마지막 코드 변경 | 2026년 4월 1일 | 2026년 11월 17일 | 2026년 4월 20일 | 2026년 11월 17일 | 2026년 11월 16일 |
| 라이선스 | MIT | MIT | – | Apache-2.0 | MIT |
mattnowdev의 Skill(지시 묶음) 1개, AI가 읽고 그대로 일해요 · MCP server가 아니에요
MCP = 손
AI를 외부 서비스나 데이터에 연결합니다(예: Notion 읽기, 청구서 만들기). 프로그램이나 서버가 실행 중이어야 합니다.
Skill = 안내서
작업 방법을 AI에게 가르치는 텍스트 파일. 어떤 서비스에도 연결되지 않습니다.
겹치는 경우도 있습니다. 도구를 부르는 스크립트가 있는 Skill도, 지식만 보내는 MCP도 있습니다. 하려는 작업을 기준으로 고르세요.
Claude CodeCursorGitHub CopilotWindsurf
제작자 README와 repo 폴더 기준
GitHub account mattnowdev (person), 12 years old
★ 229 stars, few users so far · code last changed 2026년 4월 1일
No, plain text files the AI reads and follows
No scripts, so it does not go online by itself
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
먼저: 어떤 AI를 쓰시나요
쓰는 앱을 고르면 그 앱의 설치 방법만 보여 드립니다
Uploading to claude.ai would fail: the description is over 200 characters (837). Use "Let the AI install it" instead
이 문장을 복사해 Claude Code 채팅에 붙여 넣으세요
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
Claude Code를 다시 열고 /thinking-partner를 입력하거나 관련 작업을 요청하면 Claude가 알아서 써요
Checked against official docs 2026년 11월 12일 · Source: code.claude.com
Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
이미 설치했나요? 먼저 확인 · 터미널을 열고 이 명령을 입력한 뒤 Enter
node -vMac: ⌘ + Space를 누르고 Terminal 입력 후 Enter
Windows: 시작 메뉴를 열고 Windows PowerShell 입력 후 "열기"
아직 설치하지 않았다면: 공식 다운로드 페이지에서 LTS 버전과 클릭형 설치 파일을 고르세요: Mac은 .pkg · Windows는 .msi. 더블클릭 후 끝까지 진행하면 됩니다. curl 명령은 필요 없습니다
설치가 끝나면 터미널을 닫았다가 다시 열고 같은 명령을 실행하세요. 버전 번호가 나와야 합니다: node -v
한 번 설치하면 Node.js가 필요한 모든 도구에서 쓸 수 있습니다
명령을 확인하는 중 · 확인을 통과하면 복사 버튼이 나타나요
제작자 README에서 가져온 명령으로, 제작자 코드를 내려받아 실행해요
Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요
repo를 임시 폴더에 내려받고 SKILL.md가 있는 폴더만 복사해요
명령을 확인하는 중 · 확인을 통과하면 복사 버튼이 나타나요
ChatGPT 데스크톱 앱에는 Codex가 들어 있고, Codex는 ~/.agents/skills 폴더에서 Skill을 읽습니다
ChatGPT 데스크톱 앱에서 Codex를 열고 이 문장을 채팅에 붙여 넣으세요
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
thinking-partner 폴더를 ~/.agents/skills/thinking-partner에 넣으세요
~는 홈 폴더($HOME)입니다
Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요
repo를 임시 폴더에 내려받고 SKILL.md가 있는 폴더만 복사해요
명령을 확인하는 중 · 확인을 통과하면 복사 버튼이 나타나요
Checked against official docs 2026년 11월 15일 · Source: learn.chatgpt.com
직접 설치한 Skill은 쓸 수 없고, 디렉터리의 플러그인에 들어 있는 Skill만 쓸 수 있습니다
이 Skill을 ChatGPT에서 쓰려면 위 방법대로 ChatGPT 데스크톱 앱을 쓰세요
Checked against official docs 2026년 11월 15일 · Source: learn.chatgpt.com
이 문장을 복사해 Codex 채팅에 붙여 넣으세요 · ChatGPT 데스크톱 앱 안의 Codex, Codex CLI, IDE 확장 프로그램에서 모두 쓸 수 있습니다
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는 새로 설치한 Skill을 스스로 찾습니다. 보이지 않으면 Codex를 다시 시작하세요 · 쓰는 법: ChatGPT에서는 @를 입력하고 Skill을 고르세요 · Codex CLI나 IDE 확장 프로그램에서는 /skills를 실행하거나 $ 뒤에 Skill 이름을 입력하세요
Checked against official docs 2026년 11월 15일 · Source: learn.chatgpt.com
Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요
repo를 임시 폴더에 내려받고 SKILL.md가 있는 폴더만 복사해요
명령을 확인하는 중 · 확인을 통과하면 복사 버튼이 나타나요
이 문장을 복사해 Cursor 채팅에 붙여 넣으세요
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
Cursor Agent 채팅에서 /를 입력하고 thinking-partner 선택
Checked against official docs 2026년 11월 12일 · Source: cursor.com
Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요
repo를 임시 폴더에 내려받고 SKILL.md가 있는 폴더만 복사해요
명령을 확인하는 중 · 확인을 통과하면 복사 버튼이 나타나요
Skill을 읽을 수 있는 다른 앱용입니다. 이 문장에는 Claude Code, Codex, Cursor 경로가 들어 있어 AI가 쓰는 앱에 맞게 고릅니다 · 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 2026년 11월 12일 · Source: code.claude.com, learn.chatgpt.com, cursor.com
Gemini CLI, GitHub Copilot 같은 다른 Agent Skills 지원 앱은 폴더가 달라요. 그 앱 안내를 보고 SKILL.md가 있는 폴더를 복사하세요.
2026년 11월 11일에 Claude Code, Codex, Cursor 공식 안내로 skill 폴더 확인
아래 글은 제작자 repo에서 온 것이며 PopNx MCP의 지시가 아니에요
처음 8,000자 표시 · 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 actual질문하고, 팁을 나누고, 안 되는 점을 알려 주세요. "도움이 됨"이 많은 순서예요.