Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问许可证需确认审计通过

do-think确实认为

Agent Skill

do-think 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

259

周安装

11

GitHub Stars

5

下载量

91
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:do-think(确实认为)
来源仓库:https://github.com/yigitkonur/skills-by-yigitkonur
仓库路径:skills/do-think
安装命令:
npx skills add https://github.com/yigitkonur/skills-by-yigitkonur --skill do-think
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/yigitkonur/skills-by-yigitkonur --skill do-think

简介

do-think 提供深度思考模式,适用于高风险或高代价变更前的审慎决策场景。

  • 支持单人推理与交互式脑暴两种模式,前者独立分析后者邀请用户参与。
  • 核心在于延迟行动冲动,通过结构化六步法穷尽可能性与权衡利弊。
  • 特别适合架构重构、协议变更或影响范围广泛的复杂问题处理。
  • do-think 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Do Think

The deep-thinking skill. Use it when acting on the first plausible answer is risky.

Two operating modes:

  • Solo deep-think (default) — agent reasons alone, then acts.
  • Interactive brainstorm — user in the loop, 5 forks, 6-step structured session.

One core loop applies to both. Pick the mode FIRST, then run the loop.

Trigger boundary

Use this skill when:

  • the problem is underspecified
  • the root cause is unknown
  • multiple approaches are viable and tradeoffs matter
  • a refactor could change behavior, boundaries, or workflow
  • the codebase or domain is unfamiliar
  • the change is expensive to reverse
  • the task is likely to derail if you stop after the first obstacle
  • the user explicitly asked to brainstorm, walk through, or think together

Do NOT use this skill when:

  • the task is trivial, mechanical, or fully specified
  • the user gave exact steps and the main risk is execution, not reasoning
  • you are only summarizing, translating, or relaying already-known facts
  • the task is a runtime bug with a reproducible failure → use do-debug instead
  • the task is verifying what's actually done vs. claimed → use check-completion

Pick a mode FIRST (Iron Law #0)

Default: Solo. Switch to Interactive when any of:

  • The user said "help me think", "walk through", "brainstorm", "let's figure out", "let's explore"
  • The user is present AND the decision is high-stakes / hard-to-reverse
  • ≥2 viable options have no obvious winner AND the user is reachable
  • Solo's Phase C2 stress-test killed all three options (escalation gate)
  • The decision requires the user's domain knowledge or stakeholder context

Cross-runtime note: Interactive needs an ask-user tool. See references/cross-runtime.md for the runtime → tool lookup and the prose fallback. Do not silently degrade Interactive into Solo — surface the limitation if the runtime can't support forks.

The opening contract (Iron Law #1)

The first line of every response is a single machine-checkable contract:

Mode: <Solo|Interactive>   Op: <op>   Cynefin: <Clear|Complicated|Complex|Chaotic|Disorder>   Tier: <Low|Medium|High>

Where Op is one of: SenseMaking | Extraction | Composition | Reshape | GroundedQA | WatchTrigger | Orchestration | SelfVerify.

This line is non-skippable. It declares mode (no silent default-to-Solo), proves Phase A1 ran (no skipping the Cynefin classifier), proves Phase A2 ran (no defaulting to Sense-Making for everything), and locks the effort tier (no scope creep). The user can correct any of four things in one re-prompt. Re-emit if any field changes mid-session.

Non-negotiable rules

  1. Iron Laws #0 + #1 are mandatory. Mode picked, opening contract emitted (with Op + Cynefin + Tier), on the first response.
  2. Ground before hypothesis.
  3. Match effort to Tierreferences/foundations/effort-calibration.md governs reading depth and stress-test strictness.
  4. Match thinking tools to Opreferences/foundations/operation-classification.md governs which Phase C1/C2 tools fit. The stress-test trio fits Sense-Making; other operations have their own stress-test focus.
  5. Keep ≥3 live options through Phase C *only when Op = SenseMaking*. Other operations have operation-specific C1 outputs (filled schemas for Extraction, outlines for Composition, retrieved evidence for GroundedQA, etc.).
  6. Stress-test before commit at Tier Medium or High. The trio is for SenseMaking; see operation-classification.md for the per-op stress-test focus.
  7. Separate observations, mechanisms, and judgments at every phase.
  8. Numbered, stepwise progress instead of mental jumps.
  9. Prefer the smallest next move that changes your certainty.
  10. End every session with a concrete next move + verification check (shape varies by Op).
  11. Foundations are self-sufficient. frameworks/ is library — accessed only via the master routing table at the bottom of this file or by modes/interactive-brainstorm.md. Do not cross-link from foundations to frameworks.

The universal core loop — 4 phases

Phase A — Frame      A1 classify domain   ·   A2 classify operation   ·   A3 reframe (if needed)
Phase B — Calibrate  B1 effort tier       ·   B2 minimum grounding (op-aware)
Phase C — Compare    C1 op-specific output ·  C2 op-specific stress-test
Phase D — Commit     D1 choose / produce  ·   D2 verify (op-specific)

Phase A — Frame

  • A1. Classify the domain (Cynefin) → references/foundations/domain-classification.md. Write the domain in the opening contract.
  • A2. Classify the operation (8 cognitive operations) → references/foundations/operation-classification.md. Write the operation in the opening contract. This is what selects the rest of Phase B and all of Phase C.
  • A3. Reframe the real question. Default: skip. Reframe only if A1 returned Disorder, OR the user's framing fails the why-up test → references/foundations/reframing.md (Abstraction Laddering).

Phase A exit: opening contract written (4 fields); reframe done if needed.

Phase B — Calibrate

  • B1. Effort tier (Hard Choice × Confidence-vs-Quality) → references/foundations/effort-calibration.md. Output: Low / Medium / High in the opening contract.
  • B2. Gather the minimum grounding set — shape varies by Op (see operation-classification.md):

- SenseMaking: direct observation + primary docs (evidence ladder) - Extraction: schema spec + sample inputs (≥3 covering edges) - Composition: form examples + voice spec + factual context + audience - Reshape: invariants + scope of change - GroundedQA: corpus boundary + retrieved passages - WatchTrigger: trigger conditions + signal definition + history baseline - Orchestration: system contracts + idempotency keys + error modes - SelfVerify: oracle definition + iteration budget + convergence criterion

Phase B exit: tier set; minimum evidence (op-shaped) collected.

Phase C — Compare

C1 and C2 are operation-specific. The 4-phase loop is universal; what each phase produces depends on the operation. Run the workflow for the classified Op.

  • C1. Op-specific output (NOT always "≥3 options"):

- SenseMaking → ≥3 candidate verdicts with falsifiers - Extraction → filled schema + completeness flag + ambiguity log - Composition → outline + assumption list (≥3 outline variants only when structural choice matters) - Reshape → transformation plan + invariant proofs - GroundedQA → retrieved evidence + scope confirmation - WatchTrigger → trigger spec + alert payload + escalation rules - Orchestration → sequence + idempotency markers + error handlers - SelfVerify → first attempt + first oracle reading

  • C2. Op-specific stress-test (mandatory at Tier Medium/High):

- SenseMaking → Inversion + Ladder of Inference + Second-Order (the trio) → references/foundations/stress-test-trio.md - Extraction → coverage + edge case + schema-fit - Composition → form-substance match + voice fit + audience appropriateness - Reshape → behavior preservation + scope-creep check - GroundedQA → hallucination scan + citation completeness + out-of-scope flag - WatchTrigger → false-positive scan + missed-signal scan + signal/noise - Orchestration → partial-failure scan + transaction boundary check + retry safety - SelfVerify → loop bound + oracle accuracy + escape condition

Phase C exit criterion: op-specific C1 output written AND op-specific C2 stress-test written. Outputs are written, not implied.

Escalation gate: if C2 kills all options/candidates/attempts, switch Mode to Interactive — do not silently pick the least-bad option.

Phase D — Commit

  • D1. Choose the next move (op-shaped): implement / produce / probe / ask one clarifying question / stop.
  • D2. Verify or revise — every chosen path needs a verification check + a revision trigger. Shape varies by Op (verdict observation for SenseMaking; schema validator pass for Extraction; audience decision for Composition; oracle pass for SelfVerify; etc.).

Phase D exit: chosen path stated; verification check (op-shaped) written.

Solo mode — fast routing

Read the smallest set that fits the situation. Files listed are the *minimum*; add foundations as Tier escalates.

Situation (by Op)Read this set
Generic Sense-Making (research, judgment, evaluation)references/modes/solo-deep-think.md, references/foundations/operation-classification.md, references/workflows/sense-making.md, references/foundations/stress-test-trio.md
Bug or regression (Sense-Making, bug variant)references/workflows/bug-tracing.md, references/foundations/evidence-and-falsification.md
Recurring / "we already fixed this" (Sense-Making, systemic)references/workflows/recurring-issue.md
Structured Extraction (mess → schema)references/workflows/structured-extraction.md
Generative Composition (artifact production, code feature, doc)references/workflows/generative-composition.md
Reshape & Repurpose — codereferences/workflows/refactor-thinking.md
Reshape & Repurpose — text/datareferences/foundations/operation-classification.md (Op 4 inline section)
Grounded Q&A (corpus answer with citations)references/workflows/grounded-qa.md
Watch & Trigger (design the trigger conditions)references/foundations/operation-classification.md (Op 6 inline section)
Cross-System Orchestration (design the sequence)references/foundations/operation-classification.md (Op 7 inline section)
Iterative Self-Verification (write → test → fix loop with oracle)references/workflows/iterative-self-verification.md
Planning a complex task (any Op)references/workflows/task-planning.md, references/foundations/stepwise-reasoning.md
Staying autonomous through blockers (any Op)references/workflows/continuous-execution.md
Especially high-stakes / hard-to-reverse (any Op)+ references/foundations/ultrathinking.md

Interactive mode — 6-step session, 5 forks

Full spec at references/modes/interactive-brainstorm.md. The 4-phase loop maps to a 6-step session with 5 forks:

StepPhaseWhat runsFork
1 — ClassifyA1Cynefin classifier (3 questions to user)Fork 1: domain correct?
2 — DecomposeA2 (extended)frameworks/decomposition-tools.md or foundations/reframing.mdFork 2: decomposition captures the problem?
3 — ExploreC1frameworks/six-thinking-hats.md / first-principles.md / zwicky-box.md / systems-tools.mdFork 3: options resonate?
4 — EvaluateB2 (op-specific grounding) + scoringHard Choice classifier → frameworks/decision-matrix.md (Tier was set in Step 1 alongside Op + Cynefin so the opening contract emits all four fields)Fork 4: factors + weights right?
5 — Stress-testC2Op-specific stress-test from references/foundations/operation-classification.md (use foundations/stress-test-trio.md only when Op: SenseMaking)Fork 5: blind spots change the pick?
6 — CommunicateDfoundations/output-contract.md (10-section deliverable)(no fork)

Skip-fork policy and one-question-at-a-time discipline live in references/interaction-patterns.md.

Output contract

  • Solo mode — Minto Pyramid:

- First sentence = chosen path - Body = 3-5 evidence-backed key arguments - Last sentence = verification check - Fast-fail: missing first sentence OR last sentence = output incomplete

  • Interactive mode — 10-section contract: Approach / Problem shape / Decomposition / Options explored / Evaluation / Assumptions / Blind spots / Second-order effects / Ranked summary / Recommended next step

Full spec: references/foundations/output-contract.md.

Anti-patterns

  • Acting on the first plausible explanation
  • Skipping Phase A1 (Cynefin) because the prompt feels straightforward
  • Skipping Phase A2 (Op classification) and defaulting to Sense-Making for everything
  • Running the Sense-Making stress-test trio on a non-Sense-Making operation
  • Forcing ≥3 options on a task that isn't Sense-Making (Extraction wants completeness, Composition wants outline-fit)
  • Letting one attractive option kill comparison too early (in Sense-Making)
  • Treating Phase C2 stress-test as ceremonial when it's load-bearing
  • Stopping after the first obstacle when better local moves still exist
  • Claiming success before stating the (op-shaped) verification result
  • Silently degrading Interactive into Solo
  • Reading frameworks/* without being routed there from this master table or from modes/interactive-brainstorm.md
  • Asking the user a clarifying question mid-Solo (you've hit an escalation trigger — switch to Interactive instead)

Anti-rationalization table

RationalizationCounter
"Cynefin is overkill for this."30 seconds saves rerouting a 15-minute analysis. Run it.
"Op classification is obvious — skip it."The most common upstream failure is op-mismatch. 30 seconds of classification saves a wrong-tools session. Write it in the contract.
"I already know which option wins."Then write what would falsify it. Can't? You don't know. (Sense-Making only — other ops don't have "options.")
"Stress-test feels formulaic — skip."Skipping is exactly when the formulaic check catches the blind spot the intuition missed.
"Three options is artificial; only two are real."Force a third. The third is usually "do nothing" or "ask the user." Both are real. (Sense-Making only.)
"Solo because the user said 'just figure it out'."Solo is the choice; "just figure it out" doesn't say it's reversible. Confirm reversibility before committing solo.
"Verification step is obvious — skip writing it."Unwritten = skipped under pressure. Write it.
"The trio (Inversion + Ladder + Second-Order) applies to every Op."No. The trio is for Sense-Making. Other ops have their own stress-test focus — see operation-classification.md.

Voice discipline

Required forms (use these literally in output):

  • Mode: <Solo|Interactive>
  • Op: <SenseMaking|Extraction|Composition|Reshape|GroundedQA|WatchTrigger|Orchestration|SelfVerify>
  • Cynefin: <domain>
  • Tier: <Low|Medium|High>
  • Live options: 1) … 2) … 3) … (in C1, *only* when Op = SenseMaking)
  • Filled schema: / Outline: / Retrieved evidence: / Trigger spec: / Sequence: / Oracle reading: (in C1, op-specific)
  • Pre-mortem failure mode: … (in C2, *only* when Op = SenseMaking)
  • Coverage: … / Form-substance match: … / Hallucination scan: … / etc. (in C2, op-specific)
  • Verification check: … (in D2)

Forbidden phrases:

  • "I think the best option is…" (without three named options)
  • "this is straightforward" (without a Cynefin check)
  • "let me know if you want me to dig deeper" (false abdication)
  • "Thanks for the great discussion" / "Hope this helps" / "Please feel free to" / "You're absolutely right" (shared with the pack's review skills)

Escalation gates

  • Solo → Interactive when: 3 candidate options die in stress-test
  • Interactive → Solo never silently — only on explicit user request
  • Out to do-debug when: the task is a runtime bug with a reproducible failure
  • Out to check-completion when: declared "done" but unsure what's actually verified
  • Do NOT recommend do-think as the next-step (no infinite regress). If more thinking is needed, name the sub-topic and explicitly hand off.

Reference routing — master table

Foundations are self-sufficient (read directly when the loop says so). frameworks/ is library — accessed only via the rows below or via modes/interactive-brainstorm.md. Do not cross-link foundations into frameworks.

Foundations (load-bearing primitives, used by every session)

FileRead when
references/foundations/core-loop.mdAlways — the 4-phase loop with opening contract
references/foundations/domain-classification.mdPhase A1 — Cynefin classifier
references/foundations/operation-classification.mdPhase A2 — the 8 cognitive operations + per-op routing
references/foundations/reframing.mdPhase A3 — Abstraction Laddering when framing is wrong or A1 returned Disorder
references/foundations/effort-calibration.mdPhase B1 — Hard Choice × Confidence-vs-Quality
references/foundations/evidence-and-falsification.mdPhase B2 + Phase C2 — evidence ladder, falsification, Ladder of Inference rebuild
references/foundations/stepwise-reasoning.mdWhen tempted to leap from symptom to cause
references/foundations/stress-test-trio.mdPhase C2 *for SenseMaking* — Inversion + Ladder + Second-Order (other ops use op-specific stress-test from operation-classification.md)
references/foundations/ultrathinking.mdTier High — irreversible / one-shot / broad blast radius
references/foundations/output-contract.mdAlways — Minto for Solo, 10-section for Interactive (op-shaped variations inside)

Modes (how the skill operates)

FileRead when
references/modes/solo-deep-think.mdMode = Solo — autonomous loop, anti-stall, escalation triggers
references/modes/interactive-brainstorm.mdMode = Interactive — 6-step + 5-fork mechanics

Workflows (operation-specific recipes)

FileOpRead when
references/workflows/sense-making.mdSenseMakingGeneric research / judgment / evaluation (non-bug, non-systemic)
references/workflows/bug-tracing.mdSenseMaking (bug variant)A specific bug with a known symptom
references/workflows/recurring-issue.mdSenseMaking (systemic variant)"We already fixed this and it's back" — Iceberg + Connection Circles
references/workflows/structured-extraction.mdExtractionMess → schema (transcript → todos, invoice → ledger, email → CRM)
references/workflows/generative-composition.mdCompositionContext + form → artifact (cover letter, RFP, deck, code feature)
references/workflows/refactor-thinking.mdReshape (code variant)A refactor where invariants must survive
references/workflows/grounded-qa.mdGroundedQAQuestion + corpus → cited answer (HR Q&A, codebase Q&A, support FAQ)
references/workflows/iterative-self-verification.mdSelfVerifyWrite → test → fix loop with deterministic oracle
references/workflows/task-planning.md(universal)A large or fuzzy task that needs slicing
references/workflows/continuous-execution.md(universal)Need to keep moving without frequent human checkpoint

Frameworks (library — accessed only from this table or from Interactive Steps 2-5)

FileRead when
references/frameworks/six-thinking-hats.mdPhase C1 needs perspective rotation; Interactive Step 3
references/frameworks/zwicky-box.mdPhase C1 generator is dry — combinatorial generation across dimensions
references/frameworks/first-principles.mdAnalogies are failing; suspect inherited assumptions
references/frameworks/decomposition-tools.mdIssue Trees / Ishikawa for problem decomposition
references/frameworks/decision-matrix.mdPhase C2 with ≥3 options + multiple weighted factors; Hard Choice classifier
references/frameworks/systems-tools.mdConnection Circles + Reinforcing/Balancing Loops — feedback dynamics
references/frameworks/productive-thinking-drive.mdDefining success criteria with the DRIVE check
references/frameworks/interpersonal-tools.mdSBI for feedback content; Conflict Resolution Diagram for stakeholder conflict

Cross-cutting (Interactive mode infrastructure)

FileRead when
references/interaction-patterns.mdInteractive mode — fork discipline, one-question-at-a-time, YAGNI, pushback
references/cross-runtime.mdInteractive on a non-Claude runtime — ask-user tool lookup + prose fallback

Final test

Before you act, ask:

*Do I know enough to make the next move safer and clearer than acting immediately would be?*

If yes, act. If no, gather the smallest missing evidence first.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

36.31%
按下载量换算33

Claude

29.37%
按下载量换算27

Cursor

18.95%
按下载量换算17

Gemini CLI

9.24%
按下载量换算8

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills