thinking-probabilistic
Agent skill fromtjboudreaux/cc-thinking-skills
Use when forecasting, estimating, or sizing risk — anchor on base rates, give ranges, update prior→likelihood→posterior on evidence, and factor unmeasured quantities into order-of-magnitude bounds.
How to install thinking-probabilistic
install thinking-probabilistic
# install the cc-thinking-skills pack with the skills CLI
npx skills add tjboudreaux/cc-thinking-skills# or add only this skill to Claude Code: copy the folder
skills/thinking-probabilistic/
# into
~/.claude/skills/thinking-probabilistic/ (all projects)
.claude/skills/thinking-probabilistic/ (one project)
1# Probabilistic Thinking23**Core rule:** State beliefs as numbers and ranges, not vibes. Anchor on a base rate, update with an explicit likelihood, and bound unknowns by factoring them — never invent false precision.45## When to Use67- Timeline, effort, or outcome forecasts where the true value is uncertain.8- Risk sizing for a change, migration, deploy, or launch.9- Any moment you are about to state a confident single number you cannot actually know.10- New evidence arrives and a prior estimate should move.1112## When NOT to Use1314- The quantity is measurable or look-up-able — measure or look it up.15- The decision is invariant across the whole plausible range — skip the estimate and act.16- There is no real reference class and you would invent a base rate — label it a guess, not a calibrated forecast.17- You only need a binary gate and already have a decisive observation — do not pad with ceremony.1819## Procedure20211. **Define a checkable claim:** outcome + timeframe + unit. Prefer a falsifiable statement over vague language ("likely").222. **Lock a prior and challenge it:** name a reference-class base rate and at least one credible alternative path/hypothesis with its rate. Pull the prior toward the base rate unless you write a concrete reason for deviation. Then state the strongest evidence-based case that your chosen prior or range is wrong, what estimate it supports, and revise if that countercase survives. Convert vague words to numbers (e.g. "likely" ≈ 65–80%).23…
Excerpt shown under the repository's MIT license.
