Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Probability Base Rate Anchoring

ASecurity

Anchors estimates in historical base rates before adjusting for specific factors. Use when asked 'what's the base rate', 'am I being too optimistic', 'outside view', 'reference class', 'how often does this actually happen', or 'historical frequency'.

19 stars
0 votes
0 copies
1 views
Added 9/19/2026
ai-agentsgo

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

$npx -y skills add rondoflow/rondoflow --skill probability-base-rate-anchoring --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Probability Base Rate Anchoring?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Probability Base Rate Anchoring
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rondoflow-probability-base-rate-anchoring/badge)](https://www.skillsdirectory.com/skills/rondoflow-probability-base-rate-anchoring)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: probability-base-rate-anchoring
description: "Anchors estimates in historical base rates before adjusting for specific factors. Use when asked 'what's the base rate', 'am I being too optimistic', 'outside view', 'reference class', 'how often does this actually happen', or 'historical frequency'."
---

# Probability Base Rate Anchoring

The most common forecasting error is treating every situation as unique and ignoring what usually happens. Kahneman called this neglecting the outside view. Before adjusting for what makes this situation special, you must first establish what happens in situations like this one. The base rate is the outside view — the answer to "what fraction of attempts like this one succeed?" — and it is almost always more informative than inside-view reasoning about this particular case.

---

## Your Process

**Step 1: State the Prediction or Estimate**
Name the specific outcome being predicted and the current estimate or intuition. What is being forecast and at what implied probability?

**Framing check:** Confirm the specific prediction before continuing. State what you've identified — the outcome being forecast, the current intuitive estimate, and the time horizon — in one sentence, then use `AskUserQuestion`:
- **Question:** "I'm reading this as: [your one-sentence framing of the prediction and implied probability]. 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: Find the Reference Class**
What category of similar situations does this belong to? This is the most important and contested step. The reference class should be: (a) large enough to have stable base rates, (b) genuinely similar in the ways that matter, (c) not cherry-picked to flatter the prediction. If multiple reference classes apply, note them all.

**Step 3: Find the Base Rate**
How often does this outcome actually occur in that reference class? Use historical data where available. If the exact rate is unknown, estimate a range from the most similar data available. This is the outside view — state it plainly, even if it is uncomfortable.

**Step 4: Adjust for Differentiating Factors**
What specific, verifiable features of this situation distinguish it from the reference class? For each: does it push the probability up or down from the base rate? Explicitly consider factors that cut against your prior, not only those that support it.

**Step 5: State as a Range**
Combine the base rate with adjustments to produce a final probability range, not a point estimate. The range should reflect genuine uncertainty.

---

## 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
  - **Base rate only** — Identify the historical rate without Bayesian adjustment
  - **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

**Prediction:** [the specific outcome + current intuitive estimate]

**Reference Class:** [the category used + why it applies]

**Base Rate:** [historical frequency in this class + data source or basis]

**Adjustment Factors**

| Factor | Direction (↑/↓) | Magnitude | Rationale |
|--------|----------------|-----------|-----------|
| | | | |

**Final Estimate:** [range — low to high] — [brief rationale]

**Calibration Note:** [if final estimate differs substantially from base rate, explain why the differentiating factors justify the gap]

---

## Notes

Only adjust from the base rate when you have specific, verifiable reasons — not because the situation feels different. The inside view always feels justified; the outside view is the corrective.

---

## What's Next

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

- **Question:** "Base rates anchored. What's next?"
- **Header:** "Next"
- **Options:**
  - `/probability-scenario-weighting` — Weight scenarios against the established base rate
  - `/probability-confidence-calibration` — Calibrate confidence given what the base rates revealed
  - `/decision-criteria-weighting` — Feed adjusted probabilities into the decision criteria
  - **Done** — Wrap up and synthesise what we have so far

Attribution

rondoflowrondoflow
View sourceMore from rondoflow →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

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 (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1074701 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

693621 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

691 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →