Skip to content
Back to skills

S4h Probability Confidence Calibration

ASecurity

Tests whether stated confidence levels match available evidence — catching overconfidence and underconfidence. Use when asked to 'calibrate my confidence', 'am I overconfident', 'confidence check', 'how sure should I be', or 'is this as certain as it seems'.

  • 219 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 6, 2026
developmentrustgo

Security analysis

A100/100

Scanned September 6, 2026

npx -y skills add human-avatar/skills-for-humanity --skill s4h-probability-confidence-calibration --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of S4h Probability Confidence Calibration?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for S4h Probability Confidence Calibration
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/human-avatar-s4h-probability-confidence-calibration/badge)](https://www.skillsdirectory.com/skills/human-avatar-s4h-probability-confidence-calibration)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: s4h-probability-confidence-calibration
description: "Tests whether stated confidence levels match available evidence — catching overconfidence and underconfidence. Use when asked to 'calibrate my confidence', 'am I overconfident', 'confidence check', 'how sure should I be', or 'is this as certain as it seems'."
---

# Probability Confidence Calibration

Overconfidence is the most documented and costly bias in judgment. People who say they are 90% confident are right far less than 90% of the time. But underconfidence is also costly — excessive hedging prevents commitment and action when evidence is actually sufficient. Calibration is not about being less confident; it is about having confidence levels that match the available evidence.

---

## Your Process

**Step 1: State the Claim and Current Confidence**
Name the specific claim — not a vague domain but a specific, falsifiable statement — and state the current confidence level as a percentage.

**Framing check:** Confirm the specific claim and confidence level before continuing. State what you've identified — the actual claim being evaluated and its stated confidence percentage — in one sentence, then use `AskUserQuestion`:
- **Question:** "I'm reading this as: [your one-sentence framing of the specific claim and confidence level, e.g. 'You believe X with 85% confidence and want to know if that's calibrated to the evidence']. Is that right?"
- **Header:** "Framing"
- **Options:**
  - **Yes — proceed** — framing is correct
  - **Adjust** — one element is off; user will correct it before you continue
  - **Reframe** — different situation than read; incorporate the correction before proceeding

**Step 2: Audit Supporting Evidence**
List the evidence supporting the claim. For each piece: classify its strength:
- **Direct observation:** you or a trusted source directly witnessed this
- **Inference:** logical or empirical inference from other data
- **Anecdote:** one or a few cases, not systematic
- **Assumption:** believed without verification

**Step 3: List Counter-Evidence and Gaps**
What evidence exists against the claim? What would you expect to see if the claim were true that you do not see? What have you not checked that bears on the claim?

**Step 4: Identify the Most Likely Failure Mode**
If this claim is wrong, what is the most probable reason? Is that failure mode being appropriately weighted in the current confidence assessment, or is it being minimized?

**Step 5: Apply the Frequency Test**
At this confidence level, across many similar judgments, you would be right X% of the time. Does that feel right given the quality of evidence? This frequentist reframe often corrects overconfidence.

**Step 6: State Calibrated Confidence**
Adjust the confidence level to reflect the evidence quality, gaps, and failure mode weight. State direction of adjustment and reason.

---

## Human Check-in

Before proceeding, use the `AskUserQuestion` tool. State your interpretation of the situation in 1–2 sentences — what is being analyzed and what the core question is — then ask:

- **Question:** "My read: [your 1–2 sentence interpretation]. How do you want to proceed?"
- **Header:** "Scope"
- **Options:**
  - **Full analysis** — Complete all steps, reasoning shown throughout
  - **Key findings only** — Bottom-line output, skip step-by-step detail
  - **Miscalibrations only** — Flag where confidence exceeds evidence, skip well-calibrated claims
  - **Reframe** — The read is off; correct it and the analysis will follow the corrected framing

Proceed based on their selection. If the user reframes, incorporate the correction before running any analysis.

## Output Format

**Claim:** [specific, falsifiable statement]

**Original Confidence:** [%]

**Evidence Quality Audit**

| Evidence | Type (observation/inference/anecdote/assumption) | Strength |
|----------|------------------------------------------------|---------|
| | | |

**Counter-Evidence and Gaps:** [what works against the claim or has not been checked]

**Most Likely Failure Mode:** [if wrong, why — and is it being weighted correctly?]

**Calibrated Confidence:** [%] — [direction: raised/lowered/unchanged + one-sentence rationale]

---

## Notes

A well-calibrated person is not one who is always uncertain — they are confident when evidence is strong and uncertain when it is weak. The goal is accuracy of confidence, not uniformly lower confidence.

---

## What's Next

After delivering this output, use `AskUserQuestion` to offer the next move:

- **Question:** "Confidence calibrated. What's next?"
- **Header:** "Next"
- **Options:**
  - `/s4h-probability-scenario-weighting` — Weight scenarios with calibrated confidence levels
  - `/s4h-decision-premortem-analysis` — Stress-test with calibrated risk estimates
  - `/s4h-decision-reversibility-analysis` — Assess how reversibility changes given this uncertainty level
  - **Done** — Wrap up and synthesise what we have so far

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.