agentleFS
babypochi06babypochi06/cc-thinking-skills/skills/thinking-debiasing/SKILL.md

thinking-debiasing

Skill2 starsChanged 9 months agoMITView on GitHub

Systematic checklist to identify and counteract cognitive biases in decision-making. Use before major decisions, when evaluating recommendations, or when stakes are high.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈12

    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 making or approving major decisions

    line 14
  2. Distinctive:

    When stakes are high and errors costly

    line 16
  3. Distinctive:

    When you feel very confident (overconfidence is a bias)

    line 17
  4. Distinctive:

    When a decision "feels right" but you can't articulate why

    line 19
  5. Distinctive:

    Before approving any significant recommendation, evaluate:

    line 35
  6. Distinctive:

    Ask: "What if the true number is 2x or 0.5x?"

    line 107
  7. Distinctive:

    Use multiple independent estimators

    line 108
  8. Distinctive:

    Ask: "What would make us wrong?"

    line 112
  9. Distinctive:

    Use reference class forecasting (base rates)

    line 117
  10. Distinctive:

    Ask: "How often have similar predictions been right?"

    line 118
  11. Distinctive:

    Ask: "Would we start this project today knowing what we know?"

    line 121
  12. Distinctive:

    Consider opportunity cost of continuing

    line 123

≈ “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

Cognitive Debiasing

Overview

Based on Daniel Kahneman, Dan Lovallo, and Olivier Sibony's research, this skill provides a systematic checklist to identify cognitive biases that distort decisions. Awareness of biases alone doesn't prevent them—structured checklists and processes do.

Core Principle: Your brain is systematically wrong in predictable ways. Use checklists to catch errors your intuition will miss.

When to Use

  • Before making or approving major decisions
  • Evaluating recommendations from others
  • When stakes are high and errors costly
  • When you feel very confident (overconfidence is a bias)
  • During investment, hiring, or strategic decisions
  • When a decision "feels right" but you can't articulate why

System 1 vs System 2

System 1 (Fast)System 2 (Slow)
Automatic, effortlessDeliberate, effortful
Emotional, intuitiveAnalytical, logical
Pattern-matchingRule-following
Prone to biasesCan catch biases
Default modeRequires activation

Goal: Activate System 2 for important decisions using structured processes.

The 12-Point Decision Quality Checklist

Before approving any significant recommendation, evaluate:

Self-Interest Biases

1. Is there self-interest at play?

  • Does the recommender benefit from this decision?
  • Would they recommend the same if incentives were different?
  • Are there conflicts of interest?

2. Is there emotional attachment (affect heuristic)?

  • Has the team fallen in love with the proposal?
  • Are they dismissing concerns too quickly?
  • Is criticism being taken personally?

Group Dynamics

3. Has dissenting opinion been suppressed (groupthink)?

  • Were alternative views genuinely explored?
  • Is there pressure to conform?
  • Has a devil's advocate been assigned?

4. Is there appropriate diversity of opinion?

  • Did independent thinkers contribute?
  • Were estimates made independently before discussion?
  • Has anyone with a different perspective reviewed this?

Pattern Recognition Errors

5. Are we over-relying on a single analogy (saliency bias)?

  • Is there one "this is just like X" dominating thinking?
  • Have we sought disconfirming analogies?
  • Are we cherry-picking the comparison?

6. Are we anchored on an initial number?

  • Where did the first estimate come from?
  • Would a different starting point change the conclusion?
  • Have we re-estimated from scratch?

Confirmation Bias

7. Were credible alternatives seriously considered?

  • Did we explore at least 2-3 real alternatives?
  • Were alternatives given fair evaluation?
  • Or were they strawmen to justify the preferred option?

8. Are we seeking confirming evidence only?

  • What evidence would disprove this thesis?
  • Have we actively looked for disconfirming data?
  • Are we explaining away contradictory evidence?

Planning Fallacies

9. Is the base case realistic?

  • Is this more optimistic than similar past projects?
  • What's the base rate of success for similar efforts?
  • Have we adjusted for "this time is different" thinking?

10. Is the worst case bad enough?

  • Does worst case assume only one thing goes wrong?
  • What if multiple risks materialize simultaneously?
  • Have we considered tail risks?

11. Are we discounting sunk costs appropriately?

  • Would we make this decision if starting fresh?
  • Are we continuing because we've "invested too much"?
  • What would an outsider with no history decide?

Halo Effects

12. Are we assuming success transfers?

  • Are we trusting this team/approach because of past wins?
  • Were past successes in similar contexts?
  • Are we attributing success to skill when luck played a role?

Quick Debiasing Techniques

For Anchoring

  • Generate estimate BEFORE seeing others' numbers
  • Ask: "What if the true number is 2x or 0.5x?"
  • Use multiple independent estimators

For Confirmation Bias

  • Assign someone to argue the opposite position
  • Ask: "What would make us wrong?"
  • Seek out critics, not supporters

For Overconfidence

  • Widen confidence intervals (usually too narrow)
  • Use reference class forecasting (base rates)
  • Ask: "How often have similar predictions been right?"

For Sunk Cost

  • Ask: "Would we start this project today knowing what we know?"
  • Ignore past investment when evaluating future returns
  • Consider opportunity cost of continuing

For Groupthink

  • Collect independent opinions before discussion
  • Assign devil's advocate role
  • Make it safe to dissent

Decision Quality Audit Template

# Decision Quality Audit: [Decision Name]

## Recommendation Summary
[Brief description]

## Bias Checklist

### Self-Interest & Emotion
- [ ] Self-interest checked: [Notes]
- [ ] Emotional attachment assessed: [Notes]

### Group Dynamics  
- [ ] Dissent encouraged: [Notes]
- [ ] Independent input gathered: [Notes]

### Pattern Recognition
- [ ] Multiple analogies considered: [Notes]
- [ ] Anchoring effects checked: [Notes]

### Confirmation Bias
- [ ] Alternatives genuinely evaluated: [Notes]
- [ ] Disconfirming evidence sought: [Notes]

### Planning Realism
- [ ] Base case reality-checked: [Notes]
- [ ] Worst case severe enough: [Notes]
- [ ] Sunk costs ignored: [Notes]

### Halo Effects
- [ ] Success transfer questioned: [Notes]

## Red Flags Identified
[List any concerns from checklist]

## Mitigations
[How will identified biases be addressed?]

## Decision
- [ ] Proceed as recommended
- [ ] Proceed with modifications
- [ ] Requires more analysis
- [ ] Reject recommendation

Verification Checklist

  • Systematically evaluated all 12 bias categories
  • Identified at least 2 potential biases affecting this decision
  • Applied specific debiasing technique to each identified bias
  • Sought independent/outside perspective
  • Documented reasoning for future reference
  • Comfortable defending decision process (not just outcome)

Key Questions

  • "What would have to be true for this to be wrong?"
  • "How confident am I, and what's driving that confidence?"
  • "What would an outsider with fresh eyes conclude?"
  • "Am I reasoning toward a conclusion I already want?"
  • "What's the base rate of success for decisions like this?"
  • "If I'm wrong, how will I know, and when?"

Kahneman's Warning

"We can be blind to the obvious, and we are also blind to our blindness."

You cannot debias through willpower alone. Use checklists, processes, and outside perspectives to catch what your intuition misses.

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.