← Back to Skills Marketplace
deciqai

Bayesian Reasoning

by deciqAI · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ Security Clean
26
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install deciqai-bayesian-reasoning
Description
Activate when: user says 'Bayesian', 'prior', 'posterior', 'base rate', 'likelihood ratio', or 'update my belief'; someone treats 'the evidence is consistent...
README (SKILL.md)

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
  • 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.

  1. 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.
  2. Check fit. Deterministic problems / no prior anchor → not this lens.
  3. 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]

  1. 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]

  1. 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 (\x3C0.1% for rare conditions); historical fraction of great hires (20-40%); alerts that proved real (\x3C5%); Series A → $1B outcomes (~5%).

Step 3 — Estimate the likelihood ratio. LR = P(E|H) / P(E|not-H). LR > 1 supports H; LR \x3C 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: \x3Cdecision>
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)


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 \x3C 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 — open-source thinking skills that make rigor executable for AI agents. These five skills are a free taste of the 130+ skills wired into every deciqAI agent, which runs them autonomously to operate your company. Try it free → https://www.deciqai.com/skills?utm_source=skill&utm_medium=oss&utm_campaign=knowledge-skills&utm_content=bayesian-reasoning · Built by deciqAI · github.com/deciqAI · Contributions welcome.

Usage Guidance
Install if you want a Bayesian reasoning coaching aid. Be aware it may activate too easily on the word "update," and treat outputs as reasoning support rather than professional medical, legal, security, or hiring advice.
Capability Assessment
Purpose & Capability
The files coherently provide a Bayesian reasoning framework, examples, and sources for interpreting evidence, priors, likelihood ratios, and base-rate errors.
Instruction Scope
One runtime trigger uses the standalone word "update," which is broader than the Bayesian context and could activate the skill in unrelated conversations, but it does not grant sensitive authority or cause hidden actions.
Install Mechanism
The artifact contains only markdown files and no install scripts, executable code, package dependencies, or setup steps.
Credentials
No environment variables, network calls, local file reads beyond the skill content, credentials, or external services are requested.
Persistence & Privilege
No persistence, background execution, privilege escalation, mutation authority, credential-store access, or broad local indexing is present.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install deciqai-bayesian-reasoning
  3. After installation, invoke the skill by name or use /deciqai-bayesian-reasoning
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
**Initial release of the Bayesian Reasoning skill.** - Guides users to apply Bayes' theorem to real-world decision-making, highlighting common errors (base rate neglect, prosecutor's fallacy, evidence dependence). - Details when and how to use Bayesian reasoning, with clear exclusions for deterministic/no-data scenarios. - Provides an adaptive, stepwise coaching process for novices, including WAIT prompts for interactive learning. - Supplies a structured update template and domain-specific "packs" for frequent Bayesian settings (medicine, security, hiring, A/B tests). - Lists common rationalization failures and verification steps to ensure Bayesian rigor. - Integrates with related skills: probabilistic thinking, critical thinking, logical fallacies, and first-principles reasoning.
Metadata
Slug deciqai-bayesian-reasoning
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Bayesian Reasoning?

Activate when: user says 'Bayesian', 'prior', 'posterior', 'base rate', 'likelihood ratio', or 'update my belief'; someone treats 'the evidence is consistent... It is an AI Agent Skill for Claude Code / OpenClaw, with 26 downloads so far.

How do I install Bayesian Reasoning?

Run "/install deciqai-bayesian-reasoning" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Bayesian Reasoning free?

Yes, Bayesian Reasoning is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Bayesian Reasoning support?

Bayesian Reasoning is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Bayesian Reasoning?

It is built and maintained by deciqAI (@deciqai); the current version is v1.0.0.

💬 Comments