360 Secure SkillHub
360 安全技能中心

thinking-model-combination

用于单一思维模型无法覆盖多领域或高风险问题的场景:先明确决策问题与盲区,再选 2–3 个角色互异的模型,预先声明组合模式与冲突裁决规则,逐一应用后一次性综合出可决策建议,并给出停止理由。

tjboudreaux
tjboudreaux
热度 10.83
最近更新 2026-08-05 07:52:15
分类:知识依赖:纯提示词应用场景:概念解释 / 研究 / 工作流

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add thinking-model-combination
Metadata
name
thinking-model-combination
description
When one mental model leaves a material blind spot on a multi-domain or high-stakes problem, sequence complementary models with named roles and a conflict rule.
disable-model-invocation
true

Model Combination

Core rule: Combine only when each model answers a different named question. Cap at three, name the conflict rule before applying, then synthesize once.

When to Use

  • One model already applied (or clearly primary) still leaves a material blind spot that another mechanism covers.
  • Problem spans domains (e.g. risk + choice + system structure) and stakes justify multi-lens work.
  • You need independent checks, not confirmation of the same conclusion.
  • You can name a distinct role per model before running them.

When NOT to Use

  • A single catalog skill fully answers the unknown — apply that skill alone.
  • Routine, local, or fully reversible work where multi-lens cost exceeds upside.
  • You cannot state what unique question each extra model answers (checkbox / model soup).
  • Near-duplicate mechanisms (two diagnosis skills that ask the same causal question).
  • Time budget cannot support genuine synthesis — prefer one honest model over contradictory partials.

Procedure

  1. State the unknown and the gap. Write the decision question. If one model already covers it, stop and use that model alone. Otherwise name the specific blind spot (e.g. "failure modes unexamined", "displaced alternative unknown").
  2. Pick 2–3 models with distinct roles. For each, record: model id, role (narrow / decide / stress / cost / …), and the unique question it answers. Drop any model that only rephrases another. Prefer sequential pipeline (narrow → stress → decide) over parallel unless independent concurrent checks are required.
  3. Lock the relation and conflict rule before applying. Choose pattern: sequential, parallel, nested (macro→meso→micro), or adversarial (for/against). Predeclare the tiebreaker (e.g. reversibility class, evidence strength, ruin constraint, primary decision owner). Incompatible worldviews run sequential or adversarial — never blended.
  4. Apply each model fully for its role only. Capture one key insight per model plus what only that model revealed. Do not re-run a model that adds no new insight.
  5. Synthesize once. Record convergence, divergence, how the conflict rule resolves divergence, and a single combined recommendation with residual uncertainty. Stop when the recommendation is decision-ready or when further models would only reconfirm.

Output

problem: <decision question>
gap: <named blind spot justifying combination>
pattern: sequential | parallel | nested | adversarial
models:
  - id: <skill>
    role: <named job>
    unique_question: <what only this answers>
    insight: <key finding>
conflict_rule: <predeclared tiebreaker>
convergence: <where models agree>
divergence: <where they conflict + resolution>
recommendation: <single decision-ready answer>
stop_reason: gap_closed | single_model_suffices | budget

Verification

  • Falsify / stop: Remove a model only when it changes none of the recommendation, supporting evidence, confidence, residual risks, or mitigations; then re-synthesize with fewer. If no predeclared conflict rule exists and models disagree, do not average — pick one primary model or stop and re-route.
  • Over-application guard: Never exceed three models. Never add a model for thoroughness theater. If the first adequate single model already closes the gap, combination is wrong for this task.