home / skills / openclaw / skills / munger-observer

munger-observer skill

safe

This skill helps you perform daily Munger-style reviews by surfacing cognitive traps and decision blind spots to improve thinking and outcomes.

npx playbooks add skill openclaw/skills --skill munger-observer

Review the files below or copy the command above to add this skill to your agents.

Files (2)

SKILL.md

2.7 KB

---
name: munger-observer
description: 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".
---

# 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`

Overview

This skill performs a daily wisdom review that applies Charlie Munger's mental models to your recent work and decisions. It surfaces blind spots, cognitive traps, and opportunity costs so you can course-correct quickly. Use it on a schedule or on demand for a compact, actionable Munger-style review.

How this skill works

The observer reads today's activity—memory entries, session logs, decisions, tasks, and user requests—then runs a set of canonical mental models against that activity. It checks inversion, second-order effects, incentives, opportunity cost, bias patterns, circle of competence, and margin of safety. The output is 1–2 short, prioritized observations or an "all clear" message if nothing notable is found.

When to use it

End-of-day review to catch blind spots before tomorrow
After making important decisions or planning major work
When you suspect bias in your reasoning or team decisions
Before committing resources to a new project
On a recurring daily cron for habit-forming checks

Best practices

Run at the end of your workday to capture fresh context and avoid hindsight decay
Include concise activity logs or decisions so the observer has concrete inputs
Treat observations as prompts for targeted follow-ups, not prescriptions
Combine with a short action list: what to stop, start, or test based on the insight
Use recurring reviews to track whether identified blind spots reappear over time

Example use cases

Daily automated check that flags overconfidence in a product roadmap
Post-mortem light: detect sunk-cost escalation after a stalled project
Pre-commit sanity check for hiring, spending, or major technical decisions
Coach-style review of reasoning patterns for founders or operators
Team ritual: surface systemic incentives driving local optimization

FAQ

What triggers the Munger Observer?

It runs on scheduled daily reviews or manual requests such as "run munger observer," "review my thinking," "check for blind spots," or a configured cron trigger.

What if nothing notable is found?

The report returns a concise "All clear — no cognitive landmines detected today," so you can move on without noise.