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 Scenario Weighting

ASecurity

Assigns explicit probabilities to distinct scenarios before making a decision. Use when asked to 'assign probabilities', 'scenario weighting', 'how likely is each outcome', 'quantify the uncertainty', or 'probability distribution'.

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

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

$npx -y skills add rondoflow/rondoflow --skill probability-scenario-weighting --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Probability Scenario Weighting?

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

Security grade badge for Probability Scenario Weighting
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rondoflow-probability-scenario-weighting/badge)](https://www.skillsdirectory.com/skills/rondoflow-probability-scenario-weighting)

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

Download with Pro
Files
SKILL.md
---
name: probability-scenario-weighting
description: "Assigns explicit probabilities to distinct scenarios before making a decision. Use when asked to 'assign probabilities', 'scenario weighting', 'how likely is each outcome', 'quantify the uncertainty', or 'probability distribution'."
---

# Probability Scenario Weighting

Vague uncertainty — "it might work, it might not" — produces poor decisions. Quantified uncertainty forces precision about what is actually believed and makes implicit assumptions visible. Assigning explicit probabilities to scenarios is not prediction; it is structured belief articulation. The process of assigning and calibrating probabilities often reveals more than the final numbers.

---

## Your Process

**Step 1: List Scenarios**
Enumerate all scenarios — they must be mutually exclusive (no overlap) and collectively exhaustive (cover all meaningful possibilities). If "other" is significant, make it explicit. Typically 3–5 scenarios; more than 6 reduces usability.

**Framing check:** Confirm the specific situation and uncertainty before continuing. State what you've identified — the actual decision or situation at stake and the key uncertainty being quantified — in one sentence, then use `AskUserQuestion`:
- **Question:** "I'm reading this as: [your one-sentence framing of the specific situation and the uncertainty being modelled]. 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: Assign Initial Probabilities**
Assign a probability to each scenario. They must sum to 100%. Do this before analyzing each scenario in detail — your prior is informative and anchoring matters.

**Step 3: Calibration Check**
For each probability: would you accept a bet at these odds? If you assigned 70% to a scenario, you should be willing to accept 3:7 odds against it. If the bet feels uncomfortable at those odds, your stated probability is wrong. Adjust.

**Step 4: Identify Key Driver for Each Scenario**
What would need to be true for each scenario to occur? What is the single most important condition that must hold?

**Step 5: Find the High-Probability and High-Impact Scenarios**
**Before narrowing:** Show the complete calibrated scenario table to the user first. Use `AskUserQuestion`:
- **Question:** "I've identified [N] scenarios with assigned probabilities. Before I select the highest-probability and highest-impact ones to focus on, are there any scenarios you'd flag as especially important, or any I've missed?"
- **Header:** "Prioritise"
- **Options:**
  - **Proceed with your selection** — the scenario set looks right
  - **Flag one** — user will name a specific scenario to prioritise
  - **Add a missing one** — user will describe a scenario to include

These may be the same scenario or different ones. If the highest-probability scenario is low-impact and the highest-impact scenario is low-probability, name both — they require different responses.

**Step 6: Identify Most Useful Information**
What new information would most update these probabilities? This determines what to investigate next. Information that confirms the most likely scenario is usually less valuable than information that discriminates between scenarios.

---

## 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
  - **Top 3 scenarios only** — Most likely, most harmful, most surprising
  - **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

**Scenario Table**

| Scenario | Probability | Key Driver (must be true) | Primary Implication |
|----------|-------------|--------------------------|---------------------|
| | | | |
| **Total** | **100%** | | |

**Highest-Probability Scenario:** [name + %, implications]

**Highest-Impact Scenario:** [name + %, implications — note if same or different from above]

**Most Useful Information to Gather:** [the question whose answer would most shift these probabilities]

---

## Notes

Resist collapsing scenarios into "optimistic / realistic / pessimistic" — this framing anchors on the most optimistic outcome and treats the middle case as truth. Build scenarios around key uncertainties, not emotional valence.

---

## What's Next

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

- **Question:** "Scenarios weighted. What's next?"
- **Header:** "Next"
- **Options:**
  - `/decision-premortem-analysis` — Run a premortem on the worst weighted scenarios
  - `/decision-criteria-weighting` — Weight decision criteria against scenario probabilities
  - `/temporal-horizon-mapping` — Map the weighted scenarios across time horizons
  - **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 →