Token导航 LogoToken导航

Agent Skill · 研究检索

second-order-thinking(二阶思维)

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

second-order-thinking 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 30,876。

总安装 2,799周安装 119GitHub Stars 85下载 981核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/guia-matthieu/clawfu-skills --skill second-order-thinking

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

二阶思维技能用于查找、检索和筛选相关信息。适用于长期影响推演、政策后果评估或复杂系统建模支持。可在 Codex、Claude、Cursor、Gemini CLI 中调用以拓展决策深度。使用前应界定推理边界,避免过度 extrapolation 导致错误结论。

second-order-thinking 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/second-order-thinking

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/guia-matthieu/clawfu-skills --skill second-ord…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

second-order-thinking 怎么安装?

在终端执行 npx skills add https://github.com/guia-matthieu/clawfu-skills --skill second-order-thinkin…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

second-order-thinking 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

second-order-thinking 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

second-order-thinking 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

second-order-thinking 用的人多吗?

公开数据是累计安装 2,799 次,近一周安装 119 次,下载 981 次,GitHub 85 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

second-order-thinking 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
second-order-thinking

二阶思维 · 本页

2,79985需要联网未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Second-Order Thinking

Think beyond immediate consequences to understand the chain reactions of decisions. Master Howard Marks' investment framework for seeing what others miss.

When to Use This Skill

  • Strategic decisions where long-term consequences matter
  • Policy/rule changes that will trigger behavioral responses
  • Competitive moves to anticipate market reactions
  • Product decisions where user behavior may shift
  • Investment analysis to see past obvious conclusions
  • Avoiding unintended consequences in any decision

Methodology Foundation

AspectDetails
SourceHoward Marks - "The Most Important Thing" (2011), Charlie Munger
Core Principle"First-level thinking says, 'This is a good company, let's buy.' Second-level thinking says, 'This is a good company, but everyone thinks it's great so it's overpriced. Sell.'"
Why This MattersMost people only consider immediate effects. Second-order thinkers anticipate the cascading consequences—and see opportunities and risks others miss.

What Claude Does vs What You Decide

Claude DoesYou Decide
Structures content frameworksFinal messaging
Suggests persuasion techniquesBrand voice
Creates draft variationsVersion selection
Identifies optimization opportunitiesPublication timing
Analyzes competitor approachesStrategic direction

What This Skill Does

  1. Maps consequence chains - Identifies 2nd, 3rd, nth order effects
  2. Reveals hidden risks - Finds dangers not obvious from first look
  3. Surfaces opportunities - Discovers advantages in counterintuitive moves
  4. Anticipates competitor responses - Predicts how others will react
  5. Avoids common traps - Stops decisions that seem good but backfire
  6. Improves long-term outcomes - Optimizes for total consequence, not just immediate

How to Use

Analyze a Decision with Second-Order Thinking

Apply second-order thinking to this decision: [decision]
What are the first, second, and third-order consequences?
What might we be missing?

Anticipate Competitive Response

If we [action], what will competitors/market do in response?
Map the chain reaction and help me see if this is still smart.

Evaluate a Policy Change

We're considering [policy/rule change].
Apply second-order thinking to identify unintended consequences.

Instructions

Step 1: Understand the Levels

## First vs. Second-Order Thinking

### First-Order Thinking (What Most People Do)
- Considers only immediate, obvious effects
- Answers: "What happens next?"
- Linear and direct
- Often leads to crowded positions

**Example:** "Raising prices will increase revenue."

### Second-Order Thinking (What Few Do)
- Considers consequences of consequences
- Answers: "And then what?"
- Nonlinear and systemic
- Often reveals counterintuitive truths

**Example:** "Raising prices will increase revenue... but then
some customers will churn, competitors will undercut, and
remaining customers will seek alternatives. Net effect unclear."

### The Marks Formula

"For every action, ask: And then what?
And then what after that?
And then what after that?"

Continue until you've mapped the plausible chain.

Step 2: Map Consequence Chains

## Consequence Chain Framework

### Step-by-Step Process

**1. State the Decision/Action**
"We decide to [X]."

**2. First-Order Effects (Immediate)**
"Directly and immediately, this causes [A, B, C]."

**3. Second-Order Effects (Responses)**
"In response to [A, B, C], people/markets will [D, E, F]."

**4. Third-Order Effects (Adaptations)**
"As [D, E, F] play out, we'll see [G, H, I]."

**5. Net Assessment**
"Considering all levels, is this decision still optimal?"

### Template

Second-Order Analysis: [Decision]

The Decision

[What we're considering]

First-Order Effects (Immediate)

EffectWho/What AffectedProbability
High/Med/Low
High/Med/Low

Second-Order Effects (Responses)

First EffectLikely ResponseProbability
High/Med/Low
High/Med/Low

Third-Order Effects (Cascades)

Second EffectFurther ConsequenceProbability
High/Med/Low
High/Med/Low

Key Players & Their Responses

PlayerFirst-OrderThey Will...Because...
Customers
Competitors
Employees
Regulators
Market

Net Assessment

  • Positive cascade: [list]
  • Negative cascade: [list]
  • Verdict: [Proceed / Reconsider / Modify]

Step 3: Apply Key Mental Models

## Second-Order Thinking Patterns

### 1. The Adaptation Response
**Pattern:** When you change something, people adapt.

Example: Company offers unlimited PTO.
- First-order: Employees take more vacation, happier
- Second-order: Employees feel guilty, take LESS vacation
- Third-order: Burnout increases, opposite of intended effect

**Lesson:** Anticipate how people will adapt to incentives.

### 2. The Competitive Response
**Pattern:** Your move triggers counter-moves.

Example: You cut prices 20%.
- First-order: More customers, higher volume
- Second-order: Competitors match price, your advantage disappears
- Third-order: Price war erodes margins industry-wide
- Fourth-order: Weaker players exit, consolidation

**Lesson:** Think about the game, not just your turn.

### 3. The Capacity Constraint
**Pattern:** Good things attract crowding.

Example: You discover underserved market.
- First-order: High margins, rapid growth
- Second-order: Competitors notice, enter market
- Third-order: Market becomes competitive, margins compress
- Fourth-order: Shakeout, only strong players survive

**Lesson:** Sustainable advantage requires defensibility.

### 4. The Unintended Consequence
**Pattern:** Rules/policies create new behaviors.

Example: School pays teachers based on test scores.
- First-order: Teachers focus on test prep, scores rise
- Second-order: Teaching narrows to tested material only
- Third-order: Student learning actually decreases in unmeasured areas
- Fourth-order: Best teachers leave, game-players stay

**Lesson:** Incentives shape behavior in unexpected ways.

### 5. The Reversion Tendency
**Pattern:** Extremes don't persist.

Example: Stock price triples on hype.
- First-order: Holders feel rich, buy more
- Second-order: Valuation attracts skeptics, shorts
- Third-order: Narrative shifts, selling pressure
- Fourth-order: Price reverts toward fair value

**Lesson:** Ask what happens when things normalize.

Step 4: Common Second-Order Traps

## Traps to Avoid

### Trap 1: "It Worked Before"
**First-order:** Strategy X worked for Company Y.
**Second-order:** But now everyone knows about X. It's priced in. The conditions that made it work have changed. Copycats dilute the advantage.

### Trap 2: "More is Better"
**First-order:** Adding feature Y will attract more users.
**Second-order:** But Y adds complexity, slowing onboarding. It confuses positioning. Support costs rise. Power users love it, new users bounce.

### Trap 3: "Cut Costs"
**First-order:** Reducing spending improves margins.
**Second-order:** But cutting R&D slows product. Cutting sales delays growth. Cutting quality increases churn. Best employees leave for competitors.

### Trap 4: "Lower Prices"
**First-order:** Lower prices attract more customers.
**Second-order:** But it signals low quality. Attracts price-sensitive customers who churn. Competitors match, nullifying advantage. Margins squeeze, can't invest in product.

### Trap 5: "Growth at All Costs"
**First-order:** Aggressive growth captures market.
**Second-order:** But unsustainable spending creates fragility. Unit economics don't work. When funding dries up, company collapses.

### The Antidote
For every "obvious" good idea, force yourself to ask:
"What could go wrong?"
"How might this backfire?"
"What will others do in response?"

Step 5: Decision Framework

## Second-Order Decision Framework

### Pre-Decision Checklist

□ Have I mapped at least 2 levels of consequences?
□ Have I considered how each key player will respond?
□ Have I identified potential unintended effects?
□ Have I considered reversion to mean/normalization?
□ Have I thought about what happens when competitors react?
□ Have I considered what happens if this "works" (success brings its own problems)?

### Decision Matrix

| Factor | First-Order | Second-Order | Net |
|--------|-------------|--------------|-----|
| Revenue | +/- | +/- | ? |
| Costs | +/- | +/- | ? |
| Competitive position | +/- | +/- | ? |
| Team/culture | +/- | +/- | ? |
| Optionality | +/- | +/- | ? |

### Final Assessment Questions

1. "If everyone did this, would it still work?"
2. "What do I believe that the market doesn't?"
3. "What would have to be true for this to backfire?"
4. "Am I thinking about this decision the same way everyone else is?"

### Marks' Test

"First-level thinking says: 'This looks good. Let's do it.'
Second-level thinking says: 'This looks good, but so does everyone think that?
What am I seeing that others don't? What are they seeing that I'm missing?'"

Examples

Example 1: Startup Strategy

Input:

"We're considering launching a freemium tier to grow faster. Apply second-order thinking."

Output:

Second-Order Analysis: Freemium Tier

The Decision

Launch a free tier of our SaaS product to accelerate user acquisition.

First-Order Effects (Immediate)

EffectImpactProbability
More signupsSignificantly increasedHigh
Marketing costs decreaseReduced CACHigh
Server costs increaseMore users, more infraHigh
Team focuses on conversion funnelShift from direct salesMedium

First-order conclusion: This looks great! More users, lower CAC.

Second-Order Effects (Responses)

First EffectLikely ResponseProbability
More signupsFree users demand supportHigh
More signupsFree users request featuresHigh
Lower CACCompetitors copy freemiumMedium
Team shiftSales team resists/leavesMedium
More usersProduct positioned as "cheap"Medium

Third-Order Effects (Cascades)

Second EffectFurther ConsequenceProbability
Free users demand supportSupport overwhelmed, paid users sufferMedium
Free users request featuresProduct roadmap shifts to free user needsMedium
Competitors copy freemiumPrice pressure on paid tiersMedium
"Cheap" positioningEnterprise reluctant to buyHigh
Sales team leavesLose relationships, deals slowMedium

Deep Analysis

Positive Cascade: ✅ Viral growth if product is shareable ✅ Large user base creates network effects ✅ Free tier = marketing channel ✅ Data/learnings from more users

Negative Cascade: ⚠️ Free users!= target customers ⚠️ Conversion rate likely low (2-5% typical) ⚠️ Resources shift from paying customers ⚠️ Harder to raise prices later ⚠️ Enterprise sales become harder ("Why pay when there's free?")

Key Question

"What does freemium optimize for?"

  • First-order: Volume
  • Second-order: Conversion rate becomes the constraint

The math:

  • Current: 1,000 paid users × $100 = $100K MRR
  • Freemium: 50,000 free + 2,500 paid × $50 = $125K MRR
  • But: Support costs up, team larger, margins down

Is 25% more revenue worth 50x more users and compressed pricing?

Recommendation

Before launching freemium, validate:

  1. What's realistic conversion rate for your market?
  2. Can you segment features so free doesn't cannibalize paid?
  3. Do you have infrastructure to support 10-50x users?
  4. Will free users actually convert, or just use free forever?
  5. How will competitors respond?

Alternative second-order moves:

  • Free trial (not free forever) → tests without commitment risk
  • Freemium for specific segment (students, side projects)
  • Community tier with limited features, not hobbled product

Example 2: Competitive Response

Input:

"Our main competitor just cut prices 30%. Should we match?"

Output:

Second-Order Analysis: Competitor Price Cut

The Situation

Competitor cut prices 30%. Immediate pressure to respond.

First-Order Thinking (Obvious)

"They cut prices. We must match or lose customers."

Second-Order Analysis

Why did they cut prices?

  • Possibility A: Gaining market share aggressively (funded)
  • Possibility B: Desperate (losing customers, need volume)
  • Possibility C: Segment focus (lowering to win a specific tier)

What happens if we match?

If We MatchFirst-OrderSecond-OrderThird-Order
Our prices drop 30%Revenue drops ~30% short-termMargins compress, layoffs?Innovation slows, service degrades
Customers stayRetention maintainedBut at lower valueCustomers now expect low prices
Competitor responseThey match again?Price war escalatesSomeone goes out of business

What happens if we DON'T match?

If We Don't MatchFirst-OrderSecond-OrderThird-Order
Some customers leaveLost revenueRemaining customers are less price-sensitiveHigher quality customer base
We look premiumPerceived as expensiveForced to differentiateOpportunity to add value, justify
Competitor gains shareThey growBut at lower marginsTheir growth may be unprofitable

The Non-Obvious Insight

"Matching their price assumes their strategy is correct."

What if their price cut is a sign of weakness, not strength? What if the customers who leave for 30% savings are your worst customers? What if this forces you to differentiate in ways that ultimately strengthen you?

Strategic Options

OptionSecond-Order Consequences
Match the pricePrice war, margin compression, race to bottom
Don't match, differentiateLose some customers, force value innovation
Don't match, segmentKeep enterprise pricing, let them have SMB
Don't match, add valueBundle services, increase perceived value
Temporary matchSignal willingness to fight, then raise

Recommendation

Don't immediately match. Instead:

  1. Analyze who's churning - If it's your least profitable customers, let them go
  2. Double down on differentiation - What do you do better? Emphasize it
  3. Segment your response - Maybe match for one tier, not all
  4. Consider value-add - Instead of cutting price, add something worth 30%
  5. Wait and see - They may not sustain this; watch for 2 quarters

The second-order winner: The company that doesn't match and instead uses this pressure to get better often wins long-term.


Example 3: Policy Change

Input:

"We're considering implementing a 4-day work week. Apply second-order thinking."

Output:

Second-Order Analysis: 4-Day Work Week

The Decision

Implement 4-day work week (32 hours) at full pay.

First-Order Effects (Obvious)

EffectExpectedProbability
Employee satisfaction increasesHappier teamHigh
Recruiting advantageMore applicantsHigh
Productivity per hour increasesFocused workMedium
Costs same, days worked fewerSeems efficientHigh

First-order conclusion: Seems like a clear win!

Second-Order Effects

First EffectResponse/ConsequenceProbability
Happier teamExpectations reset—5 days now feels punishingHigh
More applicantsAttracted to perk, not missionMedium
Productivity upSome roles can't compress (support, sales)High
Costs sameCustomer coverage issues M-FMedium

Third-Order Effects

Second EffectFurther CascadeProbability
5 days feels punishingIf you need surge capacity, resentmentHigh
Wrong applicantsCulture dilution, mission disconnectMedium
Some roles don't fitTwo-tier system, internal conflictHigh
Coverage gapsCustomer complaints, competitive disadvantageMedium

Deep Analysis

Who benefits?

  • Roles where output > hours (engineering, creative)
  • People with outside responsibilities (parents, caregivers)

Who doesn't benefit?

  • Customer-facing roles that need 5-day coverage
  • Time-sensitive functions (sales, support)
  • Leaders who work across time zones

Hidden consequences:

  1. Two-tier culture: If some teams work 4 days and others can't, resentment builds
  2. Expectation reset: Once given, very hard to take back
  3. Hiring bar drops: People come for the perk, not the mission
  4. Surge capacity lost: When crunch time comes, you've lost a norm
  5. Communication friction: If everyone's off Friday, what about Thursday EOD issues?

The "And Then What" Chain

  1. You implement 4-day week →
  2. Team loves it, productivity steady →
  3. Competitors don't match, you attract their talent →
  4. But: competitors now work 25% more hours →
  5. Over time, competitive edge erodes →
  6. You need to work more, but can't take back the perk →
  7. You hire more people to cover, costs rise →
  8. Or you lose ground to more intense competitors

Questions to Answer

  1. Is your business one where hours correlate with output? (If no, 4-day makes sense)
  2. Can ALL roles work 4 days, or will you create classes?
  3. What happens during crunch times?
  4. How will customers respond to Friday absence?
  5. What signal does this send about intensity/ambition?

Recommendation

Instead of blanket 4-day week:

  1. Offer flexible time - Let people choose when to work 32-40 hours
  2. Pilot first - Try with one team for 3 months, measure
  3. Measure carefully - Output per person, customer sat, not just hours
  4. Set expectations - Crunch periods still happen
  5. Communicate why - It's about productivity, not laziness

The second-order winning move: Find the specific benefit you want (reduced burnout, better talent) and solve it more directly without the blanket policy.


Checklists & Templates

Second-Order Thinking Checklist

## Before Any Major Decision

□ Have I stated the first-order effects?
□ Have I asked "And then what?" at least twice?
□ Have I considered how each stakeholder will respond?
□ Have I identified potential unintended consequences?
□ Have I thought about competitive response?
□ Have I considered what happens if this succeeds? (success problems)
□ Have I considered reversion to mean?
□ Am I thinking differently than the average person?

Consequence Chain Template

## Second-Order Analysis: [Decision]

### The Decision
[What we're considering]

### Stakeholder Responses
| Stakeholder | First Reaction | Second Response |
|-------------|----------------|-----------------|
| Customers | | |
| Competitors | | |
| Employees | | |
| Investors | | |
| Regulators | | |

### Consequence Chain
| Level | Effect | Probability | Severity |
|-------|--------|-------------|----------|
| First | | | |
| Second | | | |
| Third | | | |

### Success Scenario Cascade
If this works perfectly, what problems does success create?

### Failure Scenario Cascade
If this fails, what cascades from that?

### Net Assessment
Given all levels, should we proceed?

Skill Boundaries

What This Skill Does Well

  • Structuring persuasive content
  • Applying copywriting frameworks
  • Creating draft variations
  • Analyzing competitor approaches

What This Skill Cannot Do

  • Guarantee conversion rates
  • Replace brand voice development
  • Know your specific audience
  • Make final approval decisions

References

  • Marks, Howard. "The Most Important Thing" (2011) - Second-level thinking
  • Munger, Charlie. "Poor Charlie's Almanack" - Mental models
  • Taleb, Nassim. "Antifragile" (2012) - Unintended consequences
  • Kahneman, Daniel. "Thinking, Fast and Slow" - Cognitive biases
  • Meadows, Donella. "Thinking in Systems" - Systems dynamics

Related Skills


Skill Metadata

  • Mode: cyborg
name: second-order-thinking
category: thinking
subcategory: decision-making
version: 1.0
author: MKTG Skills
source_expert: Howard Marks, Charlie Munger
source_work: The Most Important Thing
difficulty: intermediate
estimated_value: $3,000 strategic consulting session
tags: [thinking, decisions, strategy, consequences, Howard-Marks, mental-models]
created: 2026-01-25
updated: 2026-01-25

平台分布

Codex

35.26%
按下载量换算346

Claude

28.6%
按下载量换算281

Cursor

17.51%
按下载量换算172

Gemini CLI

9.38%
按下载量换算92

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

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

继续浏览同类 Skills