Skip to content
Skills Library
Management & product · Analysis

munger

/munger

Tests a significant decision against Charlie Munger's principles (inversion, avoiding stupidity, circle of competence, incentives, second-order effects, opportunity cost) and returns a definite yes or no. Use when the user is weighing whether to commit to something with real stakes, such as a job offer, a business deal, a big client, a hire, a partnership, a new product or a market entry, and asks "should I/we...?". Not for small or technical choices such as tabs versus spaces or which library to use, not for checking whether a claim is true, and not for preparing a pitch or proposal to a clie

Licence
MIT
Last repository change
10.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 10.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Tests a significant decision against Charlie Munger's principles (inversion, avoiding stupidity, circle of competence, incentives, second-order effects, opportunity cost) and returns a definite yes or no. Use when the user is weighing whether to commit to something with real stakes, such as a job offer, a business deal, a big client, a hire, a partnership, a new product or a market entry, and asks "should I/we...?". Not for small or technical choices such as tabs versus spaces or which library to use, not for checking whether a claim is true, and not for preparing a pitch or proposal to a clie

Triggers from the description

should I/we...?
Original author description

Tests a significant decision against Charlie Munger's principles (inversion, avoiding stupidity, circle of competence, incentives, second-order effects, opportunity cost) and returns a definite yes or no. Use when the user is weighing whether to commit to something with real stakes, such as a job offer, a business deal, a big client, a hire, a partnership, a new product or a market entry, and asks "should I/we...?". Not for small or technical choices such as tabs versus spaces or which library to use, not for checking whether a claim is true, and not for preparing a pitch or proposal to a clie

How it works

  1. Principles
  2. Method
  3. Output
  4. Rules
  5. Credit
Original SKILL.md headings · 45 lines, 529 words
SKILL.md preview
---
name: munger
description: Tests a significant decision against Charlie Munger's principles (inversion, avoiding stupidity, circle of competence, incentives, second-order effects, opportunity cost) and returns a definite yes or no. Use when the user is weighing whether to commit to something with real stakes, such as a job offer, a business deal, a big client, a hire, a partnership, a new product or a market entry, and asks "should I/we...?". Not for small or technical choices such as tabs versus spaces or which library to use, not for checking whether a claim is true, and not for preparing a pitch or proposal to a client (that is spinova).
license: MIT
metadata:
  author: Sam Hon
  part-of: futureman
---

# Munger

Test the decision against the principles below and end with a definite yes or no. The point is to avoid the big mistake, not to find the brilliant move.

## Principles

1. **Invert.** Ask "how would this fail?" before "how would this succeed?". List the most likely ways it goes badly, then check whether any of them is fatal.
2. **Avoid stupidity over seeking brilliance.** A plan that dodges every fatal flaw beats a clever plan with one. Weigh the worst case more heavily than the best case.
3. **Circle of competence.** Is this inside what the user (or their team) actually knows how to do? Say where the boundary is. Outside it, the odds are worse than they look.
4. **Definite yes or no.** No lingering "maybe". If it is not clearly a yes, it is a no. If one missing fact would flip the answer, name it, and give the answer each way.
5. **Latticework of mental models.** Look at it through more than one lens: psychology, economics, maths, biology, history. Use whichever lenses actually change the picture.
6. **Second-order thinking.** For each main effect, ask "and then what?". One step further is enough here.
7. **Incentives.** Who gains what, and who is paid to say yes? "Show me the incentive and I'll show you the outcome."
8. **Patience and opportunity cost.** Saying yes rules out everything else this time, money or attention could do. Is this a rare, high-odds opportunity, or one of many?

## Method

1. State the decision in one sentence.
2. Go through the principles. Write about only the ones that change the answer: at most four. Skip the rest without comment.
3. Give the verdict.

## Output

Start with the verdict: **Yes** or **No**, and the single strongest reason, in one sentence.

Then one or two sentences per principle used, each starting with the principle's name in bold.

End with **What would change my answer**: the one or two facts that would flip the verdict.

Keep the whole reply under about 250 words, with no `#` headers and no sections beyond the ones above. This skill runs straight away; it does not need to offer first.

If the decision has a large blast radius, reaching a whole market, an ecosystem of partners, or regulators, add one last line offering an Nth-order analysis that traces the knock-on effects up to five levels (the `nth-order` skill).

## Rules

- Never end on "it depends" or "maybe". If the user has not given enough to decide, say what you need, and give the answer you would give on the most likely assumption.
- Use the user's own numbers. Do not invent figures. If you estimate, say so.
- For personal money decisions, such as investing savings or buying a specific stock, apply the principles to the reasoning but do not recommend a specific security. Say that you are not a licensed financial adviser.
- Plain words. Technical and financial terms stay exact.

## Credit

Principles from Charlie Munger's talks and writing, collected in *Poor Charlie's Almanack*. "Definite yes or no" uses Sam Hon's definition: reject the lingering maybe. Part of Sam Hon's futureman.

Versions

RepositoryScoreLicence
This page · coffeesam/claude-futureman90MIT
questflowai/investorskills100MIT

Database snapshot: 13.11.2026 · package version b18bd2487a1c (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100munger-mental-models-worldly-wisdom
    Apply Charlie Munger mental models to investments, decisions, and bias diagnosis. Trigger on Munger checklist or spot biases.
  • 100munger-observer
    Review a specific decision, plan, or artifact using bounded evidence, counterevidence, alternatives, opportunity cost, and verifiable next checks. Use for a "Munger review", decision review, premortem, or blind-spot review. Do not automatically scan history or assess a person's…
  • 95botlearn-mental-models
    A latticework thinking advisor built on Charlie Munger's mental models framework. Activate when the user faces a genuine judgment call — a decision where reasonable people could disagree, where the right answer depends on their specific situation, or where the framing itself…
  • 95inversion
    \"Invert, always invert.\" Apply Carl Jacobi's mathematical principle and Charlie Munger's investing wisdom to solve problems by thinking backward from failure. Use when: **Goal setting** - Define what would guarantee failure, then avoid it; **Risk analysis** - Identify what…
  • 100circle-of-competence
    Activate when: user says 'should I enter this market / make this hire / invest in this domain,' 'am I qualified to evaluate this,' 'stay in your lane,' 'stick to what you know,' or is about to make a consequential decision in an unfamiliar domain. Do NOT activate when: the…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.