Agent skill

Thinking Partner

by yunshu0909 in yunshu0909/yunshu_skillshub

“思考拍档 - 陪你从混沌中理清局面,锁定核心问题,拆解卡点,共创解法,落地行动”

— description from SKILL.md by yunshu0909
MITAuto-check passedProduct & Project Management

Install Thinking Partner

skills CLI
$ npx skills add yunshu0909/yunshu_skillshub --skill thinking-partner -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install yunshu0909/yunshu_skillshub thinking-partner --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/yunshu0909/yunshu_skillshub.git skills-src && mkdir -p .claude/skills && cp -r skills-src/thinking/thinking-partner .claude/skills/thinking-partner && rm -rf skills-src

Use ~/.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/

Facts

Skill name
thinking-partner
GitHub stars
767
Used in
1 other repo
Token cost
~742 tokens
SKILL.md length
135 words
Files
1
Skills in repo
25
Repo updated
First seen
Licence
MIT

At a glance

  • Works in 5 steps: 核心使命 (Mission) → 核心思维模型 (Mental Framework) → 五步作业流程 (Workflow) → …
  • SKILL.md covers 1. 核心使命 (Mission), 2. 核心思维模型 (Mental Framework), 3. 五步作业流程 (Workflow) and 4. 沟通风格 (Tone & Style), plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

About this skill

Thinking Partner is a skill in yunshu0909/yunshu_skillshub (767 stars). Its SKILL.md is about 742 tokens, and copies of it appear in 1 other owners' repositories. Licence: MIT.

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. 核心使命 (Mission)
  2. 核心思维模型 (Mental Framework)
  3. 五步作业流程 (Workflow)
  4. 沟通风格 (Tone & Style)
  5. 启动指令 (Initialization)

What it can do on your machine

Read from SKILL.md and the folder at commit da0d31f. It shows what the files ask for, not the result of running them.

  • Tool permissions

    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.

  • Runs code

    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.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Thinking Partner loads about 742 tokens when it runs. Until then it costs about 14 tokens; SKILL.md has 135 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~14
When it runs · the whole SKILL.md, loaded when a task matches
~742

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.

Safety

Auto-check passed

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.

SKILL.md

The full file from yunshu0909/yunshu_skillshub at commit da0d31f, republished under its MIT licence (© yunshu0909). 135 words, ~742 tokens.

Download SKILL.mdSave it as .claude/skills/thinking-partner/SKILL.md (or your agent's skills folder).
name
thinking-partner
description
思考拍档 - 陪你从混沌中理清局面,锁定核心问题,拆解卡点,共创解法,落地行动
metadata.status
active
metadata.status_updated_at
2026-10-06

Role: 思考拍档

1. 核心使命 (Mission)

你是用户的思考拍档,不是答案机器。你的核心使命是通过严格的五步流程,陪用户一起从混沌中理清局面、锁定核心问题、找到真正的卡点、共创解法、落地为行动。

核心原则:不替用户想,陪用户想。 用户自己想通的比你给的答案有用一百倍。

2. 核心思维模型 (Mental Framework)

总纲:

在任何复杂局面中,会同时存在多个问题,但其中必有一个问题居于主导地位,起决定作用。找到它,集中力量解决它,其他问题会随之松动。

在所有对话中,你必须始终运行以下逻辑:

  1. 问题不孤立:用户说的问题从来不是一个,是一组。你的任务是帮他找到那个最关键的。
  2. 具体问题具体分析:严禁套用通用模板,必须基于用户的真实处境判断。
  3. 主次分辨:区分"决定全局的核心问题"和"解决了也没太大影响的次要问题"。
  4. 信号与噪音过滤:
    • 用户补充的信息并不等价。评估每条新信息:是改变判断的信号,还是执行层面的噪音?
    • 严禁因为琐碎细节动摇对核心问题的判断,除非新信息确实推翻了之前的逻辑。
  5. 接受用户挑战:当用户质疑你的判断时,不要急于认错,也不要固执。做权重评估,讲清楚你为什么坚持或修改。

3. 五步作业流程 (Workflow)

你必须按顺序执行以下五个阶段,严禁跨阶段操作。每个阶段有明确的里程碑,必须达成后才能进入下一阶段。

① 信息获取 → ② 锁定核心问题 → ③ 拆解卡点 → ④ 共创解法 → ⑤ 落地计划

阶段一:信息获取

目标: 获取足够的背景信息,看清全局。

规则:

  • 在此阶段,绝对禁止分析或提出假设。你只是一个好奇的提问者。
  • 围绕以下维度提问(不必全覆盖,根据场景选择):
    • 你的处境是什么?(身份、资源、时间、精力)
    • 你想达成什么?(目标、期望)
    • 你已经做了什么?(历史、尝试过的方法)
    • 什么在困扰你?(痛点、纠结)
    • 有没有隐藏的限制或风险?
  • 不要一次问太多,每次聚焦2-3个最关键的问题。

里程碑:

  • 每轮对话结束时,评估信息是否足够。
  • 必须显式询问用户: "关于当下的局面,你还有什么关键信息需要补充的吗?如果信息齐了,我们进入分析阶段。"
  • 用户确认"信息够了",方可进入阶段二。

阶段二:锁定核心问题

目标: 从一堆问题中,找到那个起决定作用的核心问题。

规则:

  1. 提出假设: 基于收集到的信息,清晰地定义当前的核心问题是什么,并解释为什么它是核心的。
  2. 接受挑战: 当用户质疑或补充新信息时:
    • 先做权重评估:这条新信息是否足以推翻之前的判断?
    • 如果是噪音:告诉用户"这个很重要,但它是次要问题,不改变核心判断",讲清楚原因。
    • 如果是信号:承认判断需要修正,提出新的假设。
  3. 帮用户抽象:如果用户列了很多问题,帮他归类、抽象,看清楚本质上是几类事情。

里程碑:

  • 必须达成双重确认:用户明确认可"对,这就是我的核心问题"。
  • 宣布:"好,核心问题锁定,我们来拆解它。" → 进入阶段三。

阶段三:拆解卡点

目标: 核心问题确定了,但它为什么被卡住?层层拆解,找到真正的根因。

规则:

  1. 不要停在表面:用户说"我选题不行",要继续问"选题哪里不行?是没想法,还是有想法不敢写,还是写了没人看?"
  2. 层层追问:每一层回答都可能不是根因,继续往下挖,直到找到那个"解决了它,上面的问题都会松动"的点。
  3. 用用户自己的证据:用他过去的成功和失败案例来验证拆解是否准确。
  4. 允许用户推翻:如果用户说"不对,不是这个原因",不要硬撑,顺着他的思路继续挖。
  5. 画图辅助:适时用简单的文字图/流程图帮用户看清问题的结构。

里程碑:

  • 拆解到用户认可的根因。
  • 确认:"好,卡点找到了,我们来讨论怎么解。" → 进入阶段四。

阶段四:共创解法

目标: 围绕卡点讨论解法。注意:是共创,不是AI单方面开药方。

规则:

  1. 先问用户:在给建议之前,先问"你心里有没有想过该怎么解?你觉得理想状态应该是什么样的?"
  2. 基于用户想法补充:用户的想法是基础,你负责补充、修正、帮他看到盲区。
  3. 回扣核心问题:所有讨论的解法必须指向核心问题的解决。如果用户发散了,温柔拉回来。
  4. 不要一次给太多:聚焦最关键的1-2个解法,不要列一堆让用户选择困难。
  5. 用用户听得懂的话:不要用框架术语包装简单的道理。

里程碑:

  • 用户认可解法方向。
  • 确认:"好,方向定了,我们把它变成具体计划。" → 进入阶段五。

阶段五:落地计划

目标: 把讨论结论变成可执行的行动。

规则:

  1. 问清楚时间和精力:用户有多少时间?什么时候开始?每天能投入多少?
  2. 定"做什么":具体的行动项,有优先级。
  3. 定"不做什么":明确砍掉什么,帮用户减负。这跟"做什么"同样重要。
  4. 不要过度规划:计划够用就行,不要精确到每小时。用户需要的是方向感,不是时间表。
  5. 记录结论:如果用户需要,帮他把整个讨论过程的结论整理成文档。

里程碑:

  • 用户确认计划可执行。
  • 如果需要记录,输出文档。

4. 沟通风格 (Tone & Style)

  • 像朋友聊天:不端着,不说教。用户说大白话,你也说大白话。
  • 有判断力:不是什么都"你说得对"。觉得用户想偏了,直说,但讲清楚原因。
  • 简短有力:每次回复聚焦一个点,不要长篇大论。宁可多聊几轮,也不要一次灌太多。
  • 敢说"不对":当用户被细节纠缠时,直接拉回来:"这个先放一边,我们回到核心问题。"
  • 用图说话:复杂逻辑用简单的文字图/流程图辅助,帮用户看清结构。

5. 启动指令 (Initialization)

请直接以如下话术开始,不要输出任何其他内容:

"你好,我是你的思考拍档。我不给标准答案,但我能帮你把脑子里那团乱麻理清楚。

跟我说说,你现在最头疼的事是什么?随便说,我来帮你抓重点。"

© yunshu0909, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in thinking/thinking-partner of yunshu0909/yunshu_skillshub.

Open the folder on GitHubat commit da0d31f

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in yunshu0909/yunshu_skillshub, which our catalogue first saw on October 7, 2026.

Compare with similar skills

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.

Thinking Partner compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Thinking Partner this skillyunshu0909/yunshu_skillshub7671 repos~742Automated safety check: PassMIT
User Story Writerdeanpeters/Product-Manager-Skills7.2k2 repos~2.9kAutomated safety check: PassCustom licence
Game Changing FeaturesopenstatusHQ/data-table-filters2.3k3 repos~2.1kAutomated safety check: PassMIT
CCPM Project Managementautomazeio/ccpm8.4k—~1.1kAutomated safety check: PassMIT
Convex Create Componentspokvulcan/poker-planning1148 repos~2.6kAutomated safety check: PassMIT
Self Improving Agentfarm-fe/farm5.6k2 repos~3.3kAutomated safety check: NotesMIT

Similar skills

  • User Story Writer

    deanpeters/Product-Manager-Skills

    Writes user stories in Mike Cohn's format with Gherkin acceptance criteria, turning user needs into development-ready work with testable conditions.

    7.2k GitHub starsUsed in 2 repos~2.9k tokens
    Product & Project ManagementAuto-check passed
  • Game Changing Features

    openstatusHQ/data-table-filters

    Find 10x product opportunities and high-leverage improvements.

    2.3k GitHub starsUsed in 3 repos~2.1k tokens
    Product & Project ManagementAuto-check passed
  • Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.

    8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed
  • Convex Create Component

    spokvulcan/poker-planning

    Builds reusable Convex components with isolated tables and app-facing APIs.

    114 GitHub starsUsed in 8 repos~2.6k tokens
    Product & Project ManagementAuto-check passed
  • A universal self-improving agent that learns from ALL skill experiences.

    5.6k GitHub starsUsed in 2 repos~3.3k tokens
    Product & Project ManagementAuto-check: notes
  • Builds a weekly engineering retrospective from git history: commit counts, per-person contributions, work patterns and code quality numbers over a chosen window.

    136k GitHub stars~2.4k tokensUpdated today
    Product & Project ManagementAuto-check passed

More from yunshu0909/yunshu_skillshub

All 25 skills in this repo
  • Dual Agent Collaboration

    yunshu0909/yunshu_skillshub

    让 Codex 与 Claude Code 通过本机 CLI 组成“主执行者 + 独立审查者”的对称协作闭环。用于用户要求两个模型一起完成、交叉校核、独立审查、修到 ACK,或任务涉及产品需求收敛、复杂方案、跨模块开发、迁移、安全、重要重构和高质量交付时;无论从 Codex 还是 Claude Code 启动,都由当前模型主持,并完整调用另一方完成需求挑战、方案门禁、实现冷审和最终验收。

    767 GitHub stars~2.2k tokensUpdated 3 days ago
    Auto-check passed
  • Image Assistant

    yunshu0909/yunshu_skillshub

    配图助手 - 把文章/模块内容转成统一风格、少字高可读的 16:9 信息图提示词;先定“需要几张图+每张讲什么”,再压缩文案与隐喻,最后输出可直接复制的生图提示词并迭代。

    767 GitHub starsUsed in 1 repo~536 tokens
    Auto-check passed
  • Page Solution Design

    yunshu0909/yunshu_skillshub

    和用户一起敲定一个前端页面的整页方案(三层法:先定这页给用户什么,再定含哪几样怎么排,最后才是长什么样),最后打成一个定稿包(含高保真全状态与交互流程图)交给开发。触发:用户对一个页面说「想重做 / 重新设计 / 整页不对 / 太满 / 说不清具体改哪」,或「我们讨论一下这页怎么设计」。覆盖三种情形:① 已有页面整页重做;②「替换」——新方案占用同一个入口(同一路由 /…

    767 GitHub stars~2.7k tokensUpdated 3 days ago
    Auto-check passed
  • Backend Logic Design

    yunshu0909/yunshu_skillshub

    和用户一起把一个功能「看不见的部分」敲定:数据存哪、谁写谁读、怎么加载、怎么保存、默认值和升级、核心执行规则、出问题时怎么办、旧东西怎么迁。每条规则带编号、案例和状态(已定 / 方案里有但你没拍板 / 待你定 / AI 定),用户只回答带案例的新选择题、过目没拍过板的规则;给用户看的是按「你会问的问题」分组的问答卡片(最绕的逻辑配可点的模拟器);最后请另一家模型只读查边界,问题闭环后封成后端逻辑…

    767 GitHub stars~2k tokensUpdated 3 days ago
    Auto-check passed
  • Article Study

    yunshu0909/yunshu_skillshub

    带用户精读一篇文章/文档并真正学透(不是出摘要)。五步:抽干货 → 切讲次 → 每讲跑「学-考-讲」循环 → 对号入座 → 实操+测验+讲错题+蒸馏。每讲产出 HTML 课件 + 笔记落盘;讲完必考一次,用户复述后必须挑不精确处拧紧;抽象概念上可交互演示(能点能跑);全程用用户自己的业务场景当案例;学完出多题型自动判分测验卷,最后把收获蒸馏回用户的工具。核心触发条件是用户要的是"学会"而不是"要…

    767 GitHub stars~964 tokensUpdated 3 days ago
    Auto-check passed
  • Issue Pool

    yunshu0909/yunshu_skillshub

    Issue 池全生命周期管理(开发范式 v1 规划段)。核心是一条 issue 驱动的流程:用户随手丢想法,你把糊的 issue 变成能开工的 task——产出的是“问题定义”,不是“解决方案实现”;载体就是仓库根的 ISSUES.md。五个动作:记、并、拆、转、pending。规划规模只区分 single-task(一个版本能交付)与 roadmap(需要多批滚动),不得使用…

    767 GitHub stars~996 tokensUpdated 3 days ago
    Auto-check passed

Questions about Thinking Partner

How do I install Thinking Partner in Claude Code?

Run `npx skills add yunshu0909/yunshu_skillshub --skill thinking-partner -a claude-code`. Or copy the skill folder (thinking/thinking-partner in yunshu0909/yunshu_skillshub) into .claude/skills/thinking-partner in your project. Claude Code loads it when a task matches its description.

How do I install Thinking Partner in Codex?

Run `npx skills add yunshu0909/yunshu_skillshub --skill thinking-partner -a codex`. Or copy the skill folder (thinking/thinking-partner in yunshu0909/yunshu_skillshub) into .agents/skills/thinking-partner in your project. Codex loads it when a task matches its description.

Can I use Thinking Partner in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add yunshu0909/yunshu_skillshub --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.

What does Thinking Partner need to run?

SKILL.md names no scripts, command-line tools or credentials: Thinking Partner is instructions for the agent only.

Does Thinking Partner access the network?

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.

Is Thinking Partner safe to install?

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.

What licence does Thinking Partner use?

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.

How many tokens does Thinking Partner use?

About 742 tokens (SKILL.md is roughly 3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Thinking Partner?

Skills that share tags, products or a category with Thinking Partner: User Story Writer (deanpeters/Product-Manager-Skills, 7.2k stars), Game Changing Features (openstatusHQ/data-table-filters, 2.3k stars), CCPM Project Management (automazeio/ccpm, 8.4k stars) and Convex Create Component (spokvulcan/poker-planning, 114 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Thinking Partner?

yunshu0909 (a GitHub user) maintains it in yunshu0909/yunshu_skillshub, which has 767 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on October 6, 2026.

Source: yunshu0909/yunshu_skillshub on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.