agentleFS
OpenLaborOpenLabor/openlabor/skills/charlie-mental-models/SKILL.md

Charlie Munger - Mental Models

Skill5 starsChanged 3 months agoMITView on GitHub

Charlie Munger's latticework of mental models: second-order thinking, incentive superpower, Lollapalooza effect, circle of competence, and opportunity cost — from Poor Charlie's Almanack and USC Business School speech

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 10 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before applying any framework, understand the situation:

    line 21
  2. Distinctive:

    Ask the user: "What problem or decision are you wrestling with that you'd like to think through more rigorously?"

    line 23
  3. Distinctive:

    Read any relevant context — the business situation, the options being considered, the constraints, and what's already been tried.

    line 24
  4. Distinctive:

    Ask these questions ONE AT A TIME.

    line 30
  5. Distinctive:

    Run through the second-order thinking checklist:

    line 54
  6. Distinctive:

    Run the Munger Incentive Audit on the user's situation:

    line 65
  7. Distinctive:

    When multiple mental models or forces point in the same direction simultaneously, the effect is not additive — it's multiplicative and …

    line 81
  8. Distinctive:

    Never ask: "Is this a good use of resources?" Always ask: "Is this the *best* use of resources, given all alternatives?"

    line 131
  9. Distinctive:

    Always ask: "Is this the *best* use of resources, given all alternatives?"

    line 132
  10. Distinctive:

    Test any model or framework being applied:

    line 146

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Charlie Munger - Mental Models

Munger's core thesis: the person with the most useful models wins. A "latticework of mental models" from multiple disciplines outperforms expertise in any single domain.

Routes when user asks about: mental models, second-order thinking, incentives, opportunity cost, thinking frameworks, multi-disciplinary thinking, latticework, how to think better, decision making, systems thinking


Phase 1: Context Gathering

Before applying any framework, understand the situation:

  1. Ask the user: "What problem or decision are you wrestling with that you'd like to think through more rigorously?"
  2. Read any relevant context — the business situation, the options being considered, the constraints, and what's already been tried.

Phase 2: Diagnostic Questions

Ask these questions ONE AT A TIME. Wait for each answer before asking the next. Adapt based on answers — skip questions that have already been answered.

  1. "What's the decision you're facing, and what are the 2-3 options you're considering?"
  2. "If you choose the most likely option, what happens next — and then what happens after that?"
  3. "Who are the key people affected by this decision, and what are their incentives? Are those incentives aligned with the outcome you want?"
  4. "What's the best alternative use of the time, money, or attention you'd spend on this?"
  5. "On a scale of 1-10, how well do you understand this domain? What's the edge of what you know here?"

Maximum 5 questions. Stop early if you have enough to work with.


Phase 3: Analysis

Apply Munger's mental models to the user's specific situation. Select the most relevant models — not all will apply to every problem.

Second-Order Thinking

First-order thinking asks: "What happens next?" Second-order thinking asks: "What happens after what happens next?"

Apply this template to the user's situation: "If we do X, then Y will happen. But if Y happens, then Z will happen. And Z is what we actually care about."

Run through the second-order thinking checklist:

  1. What is the direct, immediate effect? (first order)
  2. What reaction will this trigger from competitors, customers, or employees? (second order)
  3. What happens in year 2-3 as a result of those reactions? (third order)
  4. Who benefits from this change that wasn't supposed to? (unintended beneficiaries)
  5. Who is harmed in ways you didn't intend? (unintended victims)

Incentive Superpower

"Never, ever, think about something else when you should be thinking about the power of incentives." — Munger

Run the Munger Incentive Audit on the user's situation:

  1. What are the formal incentives? (salary, bonus, promotion, revenue)
  2. What are the informal incentives? (social status, reputation, job security)
  3. What behavior do these incentives actually reward, vs. what behavior do we want?
  4. Where are the two misaligned?
  5. What bad outcomes will the misalignment produce?

Classic misalignment patterns to check:

  • Sales reps paid on revenue → sell to bad-fit customers → churn spikes
  • Engineers measured on velocity → ship fast but build debt → system unmaintainable
  • Consultants paid by the hour → projects take longer than necessary

Rule: "Show me the incentive and I'll show you the outcome." Before blaming people for bad behavior, audit the incentive structure. Fix the incentive, not the person.

The Lollapalooza Effect

When multiple mental models or forces point in the same direction simultaneously, the effect is not additive — it's multiplicative and extreme.

Lollapalooza Detection for the user's situation:

  • How many independent forces are pushing toward this outcome?
    • 1-2 forces: normal situation, normal analysis
    • 3-4 forces: elevated probability, higher confidence warranted
    • 5+ forces: near-certainty, act decisively

Build the Lollapalooza analysis:

Decision: [state the decision]

Forces FOR:
1. [model/force 1]
2. [model/force 2]
3. [model/force 3]

Forces AGAINST:
1. [model/force 1]
2. [model/force 2]

Lollapalooza Assessment:
- Are 3+ independent forces pointing the same direction? YES/NO
- If yes, which direction? FOR / AGAINST
- Confidence level: HIGH / MEDIUM / LOW

Circle of Competence Boundaries

"It's not a competence if you don't know the edge of it." — Munger

Rate the user's knowledge of the relevant domain on these 5 dimensions (1-10):

DimensionScoreNotes
Can explain the economics from first principles/10
Can predict how key players will behave/10
Know the historical failures and their causes/10
Can identify the key risks without a consultant/10
Have direct operating experience in this domain/10

Scoring:

  • 40-50: Core competence — act with confidence
  • 25-39: Adjacent — get input before deciding
  • Below 25: Outside circle — don't act, or hire someone who's in Zone 1

Opportunity Cost Framework

"Intelligent people make decisions based on opportunity costs." — Munger

Never ask: "Is this a good use of resources?" Always ask: "Is this the best use of resources, given all alternatives?"

Build the opportunity cost scorecard for the user's situation:

AlternativeExpected ReturnRiskFit with Strategy
Option A (current choice)
Option B (best alternative)
Option C (do nothing)

Decision rule: Only proceed with Option A if it clearly dominates B and C.

Physics Envy and Model Appropriateness

Test any model or framework being applied:

  1. Is the underlying system simple or complex?
  2. Does the model account for human behavior and its irrationality?
  3. What does the model get wrong by design?
  4. What does the model ignore that could matter most?

Big Ideas From Big Disciplines

Identify which disciplines are most relevant to the user's problem and apply the key models:

DisciplineKey Models to Consider
MathematicsCompound interest, probability, regression to mean
PhysicsCritical mass, feedback loops, equilibrium
BiologyEvolution, natural selection, adaptation, ecosystem thinking
PsychologyThe 25 biases, loss aversion, social proof
EconomicsSupply/demand, comparative advantage, opportunity cost, incentives
EngineeringRedundancy, margins of safety, failure mode analysis
HistoryPattern recognition, base rates, what actually happened vs. predictions

Phase 4: Report

Produce a structured report with this format:

Mental Models Analysis — Munger Framework

Situation Summary: [1-2 sentences restating the user's problem/decision]

Key Models Applied:

  • [Model 1: what it revealed about this situation, with specific scoring if applicable]
  • [Model 2: what it revealed]
  • [Model 3: what it revealed]

Second-Order Effects:

  • First order: [immediate effect of the likely decision]
  • Second order: [reaction from competitors/customers/employees]
  • Third order: [downstream consequence in year 2-3]

Incentive Audit Finding: [Key misalignment identified, if any]

Lollapalooza Assessment: [How many independent forces point in one direction? Which direction?]

Recommendations:

  1. [Most important action based on the mental models analysis] — Why: [which model drives this]
  2. [Second action — addressing incentive misalignment or second-order effect]
  3. [Third action — circle of competence or opportunity cost adjustment]

Risk/Watch Items:

  • [Key risk identified through multi-model analysis]
  • [Unintended consequence flagged by second-order thinking]

Bottom Line: [One sentence — the Munger verdict based on multiple converging models]


Sources

  • Poor Charlie's Almanack — Peter Kaufman (ed.)
  • "A Lesson on Elementary, Worldly Wisdom" — Munger speech at USC Business School, 1994
  • Berkshire Hathaway Annual Meeting transcripts 1987-2023
  • Seeking Wisdom: From Darwin to Munger — Peter Bevelin

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.