bayesian-reasoning
Skill13 starsChanged 4 months agoMITView on GitHub
Activate when: user says 'Bayesian', 'prior', 'posterior', 'base rate', 'likelihood ratio', or 'update my belief'; someone treats 'the evidence is consistent with X' as proof of X; a high-stakes decision rests on interpreting a test result, security alert, fraud flag, A/B result, or hiring signal; base rates are being ignored in favor of a vivid story. Do NOT activate when: the decision is genuinely deterministic and probabilities do not apply; there is no data or domain knowledge to anchor a prior (Bayes amplifies information, it does not create it from nothing). More: deciqai.com/s/bayesian-reasoning
In this repository252 other files it gives its agents.
- 10-10-10Skill
- aarrr-pirate-metricsSkill
- abductive-reasoningSkill
- activation-onboarding-playbookSkill
- aeo-answer-engine-optimizationSkill
- agent-delegability-assessmentSkill
- agent-ops-monitoringSkill
- agent-outreach-lead-nurturingSkill
- agent-ready-product-dataSkill
- ai-content-factory-brand-consistencySkill
- ai-disruption-risk-auditSkill
- ai-output-verification-trust-tiersSkill
- ai-pilot-to-scaleSkill
- ai-risk-compliance-baselineSkill
- ai-roi-business-caseSkill
- anchoringSkill
- ansoff-matrixSkill
- antifragileSkill
- ar-dso-disciplineSkill
- arrow-information-paradoxSkill
- authority-biasSkill
- availability-heuristicSkill
- batna-zopaSkill
- bcg-matrixSkill
- black-swanSkill
- blue-ocean-strategySkill
- bootstrapping-vs-raisingSkill
- build-buy-partner-aiSkill
- bullseye-traction-channelsSkill
- business-model-canvasSkill
- cash-conversion-cycleSkill
- change-and-constantsSkill
- checklistSkill
- chestertons-fenceSkill
- circle-of-competenceSkill
- cognitive-evolution-stagesSkill
- cognitive-load-theorySkill
- cognitive-science-landscapeSkill
- commitment-consistencySkill
- comparative-advantageSkill
- compound-interestSkill
- confirmation-biasSkill
- content-led-growthSkill
- continuous-discoverySkill
- contrarian-questionSkill
- cpa-doc-chaseSkill
- cpa-form-finderSkill
- cpa-irs-representationSkill
- cpa-return-reviewSkill
- critical-thinkingSkill
- cross-disciplinary-creativitySkill
- curiosity-learning-curveSkill
- customer-relationship-ladderSkill
- customs-adcvd-tariff-exposureSkill
- customs-duty-optimization-opportunity-costSkill
- customs-hts-classification-meceSkill
- customs-origin-usmca-decisionSkill
- customs-reasonable-care-isf-checklistSkill
- cynefinSkill
- death-spiralSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 31
One-line: before believing what the evidence says, ask how common this situation is to start with (prior) and how often evidence would look …
≈ “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.
Files
Bayesian Reasoning
Overview
Bayes' theorem: Posterior odds = Prior odds × Likelihood ratio. The strength of belief after evidence equals the strength before, multiplied by how diagnostic the evidence is.
This skill applies Bayesian discipline where people reason about probabilities informally — and failures follow predictable patterns: ignoring the base rate (prior), confusing P(E|H) with P(H|E) (prosecutor's fallacy), over-updating on vivid confirming evidence, treating correlated evidence as independent.
Composes with probabilistic-thinking (Bayes is the operational engine), critical-thinking (formalizes considering alternatives), logical-fallacies (prosecutor's fallacy and base-rate neglect), and first-principles (the prior is bedrock).
When to Use
- High-stakes decision rests on interpreting evidence (medical test, security alert, fraud flag, hiring signal, A/B result)
- "Evidence is consistent with X" is being treated as proof of X
- Base rates ignored — a rare event treated as probable because evidence "looks like" it
- Correlated evidence pieces treated as independent updates
- A benchmark score, AI-capability claim, AI-adoption stat, or AI-capex/valuation figure is being treated as proof without asking how often that signal appears when the underlying claim is false
- Someone says "Bayesian," "prior," "posterior," "base rate," "likelihood ratio," "update"
Not when: genuinely deterministic; no data to anchor a prior; cost of formal update exceeds the value of being more right.
Coaching Novices (Adaptive Front Door)
In Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output that step's question and nothing more.
- One-line: before believing what the evidence says, ask how common this situation is to start with (prior) and how often evidence would look this way even if the hypothesis is wrong.
- Check fit. Deterministic problems / no prior anchor → not this lens.
- Elicit the real claim and the evidence. What exactly are you deciding, and what evidence do you have?
[WAIT — do not advance until user responds]
- One question at a time: what's the base rate? what would evidence look like if the hypothesis were false? how much should that change your belief?
[WAIT — do not advance until user responds]
- Close: specific posterior probability, plus what next evidence would change it most.
[WAIT — do not advance until user responds]
The Process
Step 1 — Name hypothesis and alternatives. H vs. not-H must be exhaustive.
Step 2 — Anchor the prior before evidence. P(H) = base rate in the relevant population. Most failures happen here. Examples: disease prevalence (<0.1% for rare conditions); historical fraction of great hires (20-40%); alerts that proved real (<5%); Series A → $1B outcomes (~5%).
Step 3 — Estimate the likelihood ratio. LR = P(E|H) / P(E|not-H). LR > 1 supports H; LR < 1 supports not-H; LR ≈ 1 is non-diagnostic. If you cannot articulate P(E|not-H), you have half the story.
Step 4 — Compute the posterior. Prior odds × LR = Posterior odds → convert back to probability. Example: 0.1% prevalence, LR = 99 → posterior ≈ 9%. A "highly accurate" test on a rare disease still gives 91% chance of no disease on a positive result.
Step 5 — Check evidence dependence. Correlated evidence (three witnesses from the same source) should be treated as ~one piece, not compounded.
Step 6 — Commit and act. State the posterior number, the action threshold, and what next evidence would most move it.
Output: Bayesian Update
# Bayesian Update: <decision>
H / not-H:
Prior P(H): Source:
Evidence E:
P(E|H): P(E|not-H): LR:
Posterior P(H|E): Interpretation:
Independence check:
Decision threshold: Action: Next evidence:→ Method in Action: Sally Clark Case (1999) · Air France 447 Search (2009–2011) → 2026 lens: Updating Beliefs About AI Capability and Safety From Eval Results (2023–2026)
Pack: Common Bayesian Settings
A "pack" bundles the most common prior and LR patterns for a domain.
| Setting | Common prior | Common LR failure |
| Medical screening | Population prevalence | Treating sensitivity as posterior |
| Security alert triage | Fraction of alerts that were real | "Matches signature" = "is the threat" |
| Hiring | Historical fraction of great hires in this role | One strong interview = "great candidate" |
| A/B test | Prior probability the change has a real effect | "p < 0.05" without prior |
Contribute a pack for your domain — see the template at the repo root.
→ Sources: references/sources.md
Common Rationalizations
Note — [D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.
| Fake move | Reality |
| [D] "This looks just like X" | Not enough. How often does it look like X when it isn't? Without LR, you have rhetoric. |
| [D] Ignoring base rate because "this case feels different" | The base rate captures everything you don't know. "Feels different" is already included. |
| [D] Confusing P(E|H) with P(H|E) | The prosecutor's fallacy. They can differ by orders of magnitude. |
| [D] Treating correlated evidence as independent | Multiplying correlated likelihoods overstates the update. Identify common causes. |
| [D] Updating intuitively without numbers | Intuitive updates are miscalibrated — too strong on confirming, too weak on disconfirming. |
| [D] Picking the prior after seeing the evidence | Hindsight contamination. Commit to the prior before evidence. |
| [D] "I'm doing a Bayesian update" without naming P(H), P(E|H), P(E|not-H) | Then you are not. You are using the word. |
| [D] Absence of evidence = evidence of absence | Depends on P(E|H) and P(E|not-H). If evidence is rarely observable, absence is weak. |
| [D] Posterior keeps drifting toward H every round without calibration check | Either H is increasingly likely or there is a confirmation-bias leak. |
| To add [O] entries: paste a real failure instance here after each production use | Description of what happened |
Red Flags
- Prior never named · "Consistent with X" treated as proof of X · Sensitivity without false-positive rate · Correlated evidence summed as independent · Posterior matches vivid story not math · "Highly likely" without a number · Prior chosen after evidence · "Bayesian" invoked without an actual update
Verification
- Hypothesis and alternatives explicitly named and exhaustive
- Prior named with a number and source, before evidence is examined
- P(E|H) AND P(E|not-H) both estimated · Likelihood ratio computed
- Posterior computed numerically · Independence of evidence pieces checked
- Decision threshold and action stated · Next evidence identified
Part of deciqAI Knowledge Skills — 253 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. See it run → https://www.deciqai.com/s/bayesian-reasoning · Built by deciqAI · github.com/deciqAI · Contributions welcome.
Agents: latest version & machine-readable metadata → https://www.deciqai.com/s/bayesian-reasoning.json
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.

