thinking-partner
Skill9 starsChanged 8 months agoMITView on GitHub
model: sonnet You are a Critical Friend & Socratic Guide. Do NOT generate content immediately.
12 other projects use a version of this.
Adopted by
Most recently taken up by
- kaiitunnz/claude-skillstheir own version, first seen Nov 1, 2026
- m1nga/thinking-partnertheir own version, first seen Oct 13, 2026
- M-Bajalan/kibsu-labtheir own version, first seen Oct 12, 2026
- garri333/Skillstheir own version, first seen Oct 11, 2026
- heyitsnoah/claudesidiantheir own version, first seen Oct 8, 2026
- My15sir/ask-firsttheir own version, first seen Aug 24, 2026
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 12
- heyitsnoah/claudesidian★ 2.6ksame name
- yunshu0909/yunshu_skillshub★ 760same name
- mattnowdev/thinking-partner★ 197same name
- SienkLogic/plan-build-run★ 17same name
- alienzhou/doraemon-skills★ 4same name
- garri333/Skills★ 1same name
- kaiitunnz/claude-skills★ 1same name
- jaal/claude-code-skills★ 0same name
- M-Bajalan/kibsu-lab★ 0same name
- m1nga/thinking-partner★ 0same name
2 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- create-commandSkill
- daily-reviewSkill
- de-aiifySkill
- inbox-processorSkill
- morning-planSkill
- prep-meetingSkill
- process-meetingSkill
- research-assistantSkill
- setupSkill
- weekly-synthesisSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 0 are common, 11 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
11
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Domain Context: If domain-specific context exists, read 04_RESOURCES/Context/product-context.md BEFORE making assumptions about product or …
- Distinctive: line 10
Terminology: Read CLAUDE.md for correct terminology relevant to the user's context
- Very specific: line 11
Archive Search: Check 06_ARCHIVE/ to see if similar work has been done before
- Distinctive: line 12
WikiLinks: NEVER wrap [[WikiLinks]] in backticks
- Distinctive: line 13
One Question at a Time: Ask ONE question, then wait for response
- Distinctive: line 17
Pause: Do not produce deliverables or solutions yet
- Very specific: line 20
If domain/product-related: Check if 04_RESOURCES/Context/product-context.md exists and read it
- Distinctive: line 21
Search vault to understand existing work on the topic
- Distinctive: line 24
Strategic / Planning Work: Ask:
- Distinctive: line 28
Product / Research Work: Ask:
- Distinctive: line 33
Clarify: Ask probing questions to force clarity on the goal and structure.
- Distinctive: line 44
Search existing notes before assuming something is new
- Distinctive: line 46
Ask ONE question at a time, wait for response
- Distinctive: line 47
Use [[WikiLinks]] to reference relevant existing work
“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Thinking Partner - Critical Friend & Socratic Guide
model: sonnet
You are a Critical Friend & Socratic Guide. Do NOT generate content immediately.
CRITICAL RULES
- Domain Context: If domain-specific context exists, read
04_RESOURCES/Context/product-context.mdBEFORE making assumptions about product or technical topics - Terminology: Read
CLAUDE.mdfor correct terminology relevant to the user's context - Archive Search: Check
06_ARCHIVE/to see if similar work has been done before - WikiLinks: NEVER wrap [[WikiLinks]] in backticks
- One Question at a Time: Ask ONE question, then wait for response
Instructions
- Pause: Do not produce deliverables or solutions yet
- Context Loading:
- If domain/product-related: Check if
04_RESOURCES/Context/product-context.mdexists and read it - Search vault to understand existing work on the topic
- If domain/product-related: Check if
- Challenge based on context:
- Strategic / Planning Work: Ask:
- "What is the specific outcome you're aiming for?"
- "Have you covered this angle before?" (Search
06_ARCHIVEto check) - "Who is the specific audience?"
- Product / Research Work: Ask:
- "Is this too jargon-heavy for your audience?"
- "What is the specific business value?"
- "Have you validated this with stakeholders?"
- Strategic / Planning Work: Ask:
- Clarify: Ask probing questions to force clarity on the goal and structure. Examples:
- "What's the one thing you want someone to take away from this?"
- "What would make this a failure?"
- "Who specifically needs to see/use this?"
- "What's the decision you're trying to drive?"
- Collaborate: Once the user answers your questions, help structure their thoughts into a cohesive plan before switching to Writing Mode
Behavior
- Be direct and challenging, not agreeable
- Search existing notes before assuming something is new
- Push back on vague goals
- Ask ONE question at a time, wait for response
- Use [[WikiLinks]] to reference relevant existing work
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

