mcpbeat Sign in

Munger Observer Agent Skill

Daily wisdom review applying Charlie Munger's mental models to your work and thinking. Use when asked to review decisions, analyze thinking patterns, detect biases, apply mental models, do a "Munger review", or run the Munger Observer. Triggers on scheduled daily reviews or manual requests like "run munger observer", "review my thinking", "check for blind spots", or "apply mental models".

763 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
239
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/jdrhyne/agent-skills --skill munger-observer

The instruction itself

9 sections, as written by the author

Munger Observer

Automated daily review applying Charlie Munger's mental models to surface blind spots and cognitive traps.

Process

1. Gather Today's Activity

  • Read today's memory file (memory/YYYY-MM-DD.md)
  • Scan session logs for today's activity
  • Extract: decisions made, tasks worked on, problems tackled, user requests

2. Apply Mental Models

Inversion

  • What could go wrong? What's the opposite of success here?
  • "Tell me where I'm going to die, so I'll never go there."

Second-Order Thinking

  • And then what? Consequences of the consequences?
  • Short-term gains creating long-term problems?

Incentive Analysis

  • What behaviors are being rewarded? Hidden incentive structures?
  • "Show me the incentive and I'll show you the outcome."

Opportunity Cost

  • What's NOT being done? Cost of this focus?
  • Best alternative foregone?

Bias Detection

  • Confirmation bias: Only seeking validating information?
  • Sunk cost fallacy: Continuing because of past investment?
  • Social proof: Doing it because others do?
  • Availability bias: Overweighting recent/vivid information?

Circle of Competence

  • Operating within known territory or outside?
  • If outside, appropriate humility/caution?

Margin of Safety

  • What's the buffer if things go wrong?
  • Cutting it too close anywhere?

3. Generate Output

If insights found: 1-2 concise Munger-style observations

If nothing notable: "All clear — no cognitive landmines detected today."

Output Format

🧠 **Munger Observer** — [Date]

[Insight 1: Model applied + observation + implication]

[Insight 2 if applicable]

— "Invert, always invert." — Carl Jacobi (Munger's favorite)

Example

🧠 **Munger Observer** — January 19, 2026

**Opportunity Cost Alert:** Heavy focus on infrastructure today. The content queue is aging — are drafts decaying in value while we polish tools?

**Second-Order Check:** Speed improvement is good first-order thinking. Second-order: faster responses may raise expectations for response quality. Speed without substance is a trap.

— "Invert, always invert."

Scheduling (Optional)

Set up a cron job for daily automated review:

  • Recommended time: End of workday (e.g., 5pm local)
  • Trigger message: MUNGER_OBSERVER_RUN

Privacy Addendum

  • Analyze only the minimum required memory/session span for the requested review.
  • Exclude credentials, financial account numbers, health data, and private identifiers from outputs.
  • Do not copy or forward personal excerpts outside the current workspace/session without explicit user instruction.

Other skills for the same job

different authors, same section of the catalogue
Doc Coauthoring
by anthropics
vendor ×10

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

4k tokens
File Organizer
by frostant
×10

Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.

3k tokens
Domain Name Brainstormer
by frostant
×8

Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.

1k tokens
Brainstorming
by ZhanlinCui
×4

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

626 tokens
Planning With Files
by ZhanlinCui
×3

Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.

9k tokens scripts
Scientific Brainstorming
by christophacham
×3

Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.

5k tokens
GitHub Project Management
by ComeOnOliver
×3

Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning

14k tokens
Grill Me
by ComeOnOliver
×3

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

3k tokens

How to use it

Copy the folder

Take jdrhyne/munger-observer from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.