confidence
Skill1 starsChanged 8 months agoMITView on GitHub
Contextual confidence calibration — DEFLATE for One-Way Doors and RED zones, PROTECT for Two-Way Doors and fundraising, "How does this work step by step?" depth testing, values-to-consequences redirect, unanimity as risk signal. From Knowledge Illusion — overconfidence is sometimes functional. Use when calibrating response intensity, testing founder assumptions, or navigating motivational vs analytical contexts.
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
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
- Distinctive: line 10
Before responding to any strategic decision
- Distinctive: line 11
When the founder expresses high or low confidence
- Distinctive: line 14
When unanimity or values-language appears
- Distinctive: line 46
When a founder shifts from causal reasoning to identity/values language during strategic discussion, detect and redirect:
- Distinctive: line 60
When the entire team agrees on a course of action:
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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.
Files
Contextual Confidence Calibration
When to Apply
- Before responding to any strategic decision
- When the founder expresses high or low confidence
- One-Way Door decisions (deflate)
- Fundraising or team motivation contexts (protect)
- When unanimity or values-language appears
Core Framework
Context-Dependent Calibration
Overconfidence is sometimes functional — it gives founders activation energy to attempt things they would rationally never try. Do NOT universally deflate. Calibrate by context:
| Context | Posture | Behavior |
| One-Way Door decisions | DEFLATE | Full "How does this work step by step?" challenge. Assumption audit, pre-mortem, Devil's Advocate. |
| Two-Way Door decisions | PROTECT | "This is low-risk. Your instinct is worth testing. Ship it." Minimal analysis. |
| Fundraising / team motivation | PROTECT the narrative | Don't puncture the story. Privately flag: "Pitch version and analytical version should differ." |
| Buffer GREEN zone | PROTECT momentum | Celebrate progress. Light-touch monitoring. |
| Buffer YELLOW/RED zone | DEFLATE immediately | Full analytical mode. "We need to confront what's actually happening." |
| Unanimity (team all agrees) | PROBE | Unanimity is a risk signal, not strength. "Can any single team member walk through the full causal chain?" |
Depth Testing: "How" Not "Why"
"Why?" generates supporting reasons -> strengthens overconfidence "How does this actually work step by step?" exposes knowledge gaps -> calibrates confidence
Instead of: "Why do you think this will work?"
Ask: "Walk me through how this works, step by step.
What happens first? Then what? What could go wrong at each step?"This is the Explanation Depth Illusion: people believe they understand systems until asked to explain the mechanism. "How" reveals the gaps; "Why" lets people rationalize.
Values-to-Consequences Redirect
When a founder shifts from causal reasoning to identity/values language during strategic discussion, detect and redirect:
Founder: "This is who we are. We believe in our mission."
Agent: "That's a values statement. Let's set values aside and
examine the expected causal outcomes separately. Values inform
WHY we choose, but consequences determine WHAT happens."Values language during strategic analysis is often a defense against confronting uncertainty. The redirect is respectful but firm.
Unanimity as Risk Signal
When the entire team agrees on a course of action:
Agent: "Everyone agrees — which can mean either genuine alignment
or social conformity. Quick test: can any single team member
walk through the full causal chain from action to result?
If not, team confidence may be a mirage."Unanimous support without individual depth understanding = groupthink risk.
Knowledge Illusion (When Overconfidence is Functional)
From Sloman & Fernbach: humans think with the community, not individually. Overconfidence about collective capabilities can be MORE accurate than individual confidence assessment.
When to let overconfidence stand:
- Two-Way Door decisions where bias toward action is valuable
- Early-stage exploration where activation energy matters more than accuracy
- Team morale contexts where analytical deflation would be destructive
When to deflate:
- One-Way Door decisions where the cost of overconfidence is irreversible
- Buffer RED zone where reality must be confronted
- Load-bearing assumptions that drive resource allocation
Decision Rules
- Context determines posture — never apply the same confidence treatment universally
- "How" for depth testing — always prefer mechanism questions over justification questions
- Protect Two-Way Doors — bias toward action on reversible decisions
- Deflate One-Way Doors — full analytical treatment on irreversible decisions
- Pitch vs analysis separation — fundraising narrative and strategic analysis should differ
- Unanimity = probe — team agreement without individual depth is a warning sign
Anti-Patterns to Detect
| Anti-Pattern | Signal | Response |
| Universal deflation | Challenging every decision equally | "This is a Two-Way Door. Your instinct is worth testing." |
| Universal protection | Never challenging the founder | "This is a One-Way Door. Let's walk through the mechanism step by step." |
| Values as strategy | "This is who we are" in strategic discussion | Redirect: "Values inform WHY. Let's examine WHAT happens." |
| False unanimity | Everyone agrees, no one can explain | "Can anyone walk through the full causal chain?" |
| Puncturing pitch narrative | Analytical mode during fundraising prep | "Pitch version inspires; analysis must be honest. Keep them separate." |
| Analytical mode in GREEN | Heavy analysis when things are working | "Buffer is GREEN. Celebrate progress, monitor lightly." |
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- mthines/agent-skills★ 20same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository24 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- anticipatory-sellingSkill
- choice-architectureSkill
- content-rulesSkill
- critical-chainSkill
- culture-mapSkill
- disruptionSkill
- effectuationSkill
- failure-essenceSkill
- growth-metricsSkill
- kpi-treeSkill
- network-effectsSkill
- pipelineSkill
- plan-bSkill
- pre-mortemSkill
- qualificationSkill
- quest-interviewSkill
- retention-cohortsSkill
- review-engineSkill
- root-causeSkill
- strategy-kernelSkill
- stupid-gamesSkill
- unit-economicsSkill
- value-stickSkill
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
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.

