thinking-probabilistic
Use when forecasting, estimating, or sizing risk — anchor on base rates, give ranges, update prior→likelihood→posterior on evidence, and factor unmeasured…
Skill by tjboudreaux
Chalk Labs
Need help deploying thinking-probabilistic?
Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/tjboudreaux-thinking-probabilistic
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/thinking-probabilistic
What's inside
- Skill name
thinking-probabilistic- Description
- 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.
- License
- MIT
- Instructions
- 51 lines in SKILL.md · view on GitHub
Files (1)
- SKILL.md
SKILL.md (first lines)
# Probabilistic Thinking
**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.
## When to Use
- Timeline, effort, or outcome forecasts where the true value is uncertain.
- Risk sizing for a change, migration, deploy, or launch.
- Any moment you are about to state a confident single number you cannot actually know.
- New evidence arrives and a prior estimate should move.
## When NOT to Use
- The quantity is measurable or look-up-able — measure or look it up.
- The decision is invariant across the whole plausible range — skip the estimate and act.
- There is no real reference class and you would invent a base rate — label it a guess, not a calibrated forecast.
- You only need a binary gate and already have a decisive observation — do not pad with ceremony.
## Procedure
1. **Define a checkable claim:** outcome + timeframe + unit. Prefer a falsifiable statement over vague language ("likely").
2. **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%).
3. **Express a range, not a point:** give at least one confidence interval (50% and 80% preferred). Assume overconfidence; widen intervals when the outside view is thin.
4. **Update prior → likelihood → posterior when evidence arrives:**
- Prior odds = p / (1 − p).
- Likelihood ratio LR = P(E|H) / P(E|¬H). LR > 1 supports H; LR = 1 is noise; LR < 1 undermines H.
- Posterior odds = prior odds × LR (multiply even when LR < 1); p = odds / (1 + odds).
- Strength bands for distance from 1: weak ~1.5–3×, moderate 3–10×, strong 10–100×, definitive 100×+.
- Yesterday's posterior is today's prior for the next evidence. For rare events, start from the base rate — vivid positives still leave most mass on false alarms.
5. **Fermi-bound unmeasured quantities** (only when you need a magnitude you cannot measure/look up):
- Decompose: Quantity = Factor₁ × Factor₂ × … (or sum of components).
- Bound each factor with a range; use one-significant-figure geometric means for order-of-magnitude.
- Multiply; report "~X within 3–5×"; sanity-check whether a 10× error would change the decision; replace any factor that is actually lookup-able.
- Skip Fermi when the number is cheaply measurable, when the decision needs tighter than ~3–5× precision, or when every factor is pure invention.
6. **State the final estimate for checking:** claim, range/CIs, key uncertainties, and the observation that would prove it wrong. Stop when the decision is stable across the remaining range or the next update needs new evidence you do not have.
## Output
1. **Claim** — falsifiable statement with timeframe.
2. **Prior** — base rate, alternative path, adjustment reason, strongest countercase, and resulting prior probability.
3. **Range** — confidence intervals (not a lone point).
4. **Updates** — each evidence row: prior, LR (or explicit heuristic Δ), posterior.
5. **Fermi bounds** (if used) — factor product and "~X within N×".
6. **Decision implication** — what changes if the true value is at the low vs high end of the range.
## Verification
- **Falsify/stop:** if you cannot name a base rate, alternative, or serious countercase, label the estimate as a guess rather than calibrated. If the decision is unchanged across the full range, stop estimating. If new evidence arrives and the number does not move (or moves without an LR/Δ), recompute.
- **Over-application guard:** do not dress checkable facts as probabilities, invent reference classes, or Fermi-decompose quantities you can measure. Do not report three significant figures on a 5×-uncertain product. For rare events, refuse jumps from one vivid hit to near-certainty without the base-rate prior.From tjboudreaux/cc-thinking-skills, MIT.
More from tjboudreaux/cc-thinking-skills
- 0.782score
thinking-circle-of-competence
tjboudreaux
Use when a specific claim may lack grounding.
SkillBFreshness: B★ 1.7KClaude Code +9 - 0.782score
thinking-via-negativa
tjboudreaux
Use when the reflex is to add a feature, layer, or process.
SkillBFreshness: B★ 1.7KClaude Code +9 - 0.782score
thinking-kepner-tregoe
tjboudreaux
Use when a selective defect needs IS/IS-NOT difference analysis or a consequential option choice needs must/want weighting and adverse-consequence comparison.
SkillBFreshness: B★ 1.7KClaude Code +9 - 0.782score
thinking-lindy-effect
tjboudreaux
Use when longevity of a non-perishable option matters.
SkillBFreshness: B★ 1.7KClaude Code +9 - 0.782score
thinking-bounded-rationality
tjboudreaux
Use when search or investigation could run forever.
SkillBFreshness: B★ 1.7KClaude Code +9 - 0.778score
thinking-theory-of-constraints
tjboudreaux
When throughput or latency is pipeline-limited, identify the single binding constraint and exploit, subordinate, elevate, then recheck—ignore non-constraints.
SkillBFreshness: B★ 1.7KClaude Code +9 - 0.778score
thinking-systems
tjboudreaux
When behavior is emergent across components—fixes elsewhere break, loops/delays dominate—map boundary, stocks/flows, feedback, archetypes, then rank leverage.
SkillBFreshness: B★ 1.7KClaude Code +9 - 0.778score
thinking-ooda
tjboudreaux
Use under time pressure when the situation is still changing and you must act before certainty — cycle Observe→Orient→Decide→Act on ~70% confidence, then…
SkillBFreshness: B★ 1.7KClaude Code +9 - 0.778score
thinking-effectuation
tjboudreaux
Under genuine uncertainty with no reliable forecast, inventory means, cap downside at affordable loss, act for commitments, and let goals emerge from…
SkillBFreshness: B★ 1.7KClaude Code +9 - 0.778score
thinking-steel-manning
tjboudreaux
Before rejecting a proposal or reflexively agreeing, build the strongest faithful opposing case, state agreement conditions, then update or reaffirm.
SkillBFreshness: B★ 1.7KClaude Code +9 - 0.778score
thinking-first-principles
tjboudreaux
When a constraint is treated as fixed, separate physics from convention, keep only independently supported primitives, and rebuild the simplest solution that…
SkillBFreshness: B★ 1.7KClaude Code +9 - 0.778score
thinking-red-team
tjboudreaux
For authorized security review of code, auth, or APIs you control, model the attacker, map the attack surface, and report only findings with a reproducible…
SkillBFreshness: B★ 1.7KClaude Code +9
Signals
- Stars
- 1,668
- Forks
- 185
- Open issues
- 2
- Last commit (this folder)
- Jul 17, 2026 (3 months ago)
- Last release
- Aug 4, 2026 (2 months ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from tjboudreaux
- 0.782score
thinking-circle-of-competence
tjboudreaux
Use when a specific claim may lack grounding.
SkillBFreshness: B★ 1.7KClaude Code +9 - 0.782score
thinking-lindy-effect
tjboudreaux
Use when longevity of a non-perishable option matters.
SkillBFreshness: B★ 1.7KClaude Code +9 - 0.782score
thinking-via-negativa
tjboudreaux
Use when the reflex is to add a feature, layer, or process.
SkillBFreshness: B★ 1.7KClaude Code +9 - 0.782score
thinking-bounded-rationality
tjboudreaux
Use when search or investigation could run forever.
SkillBFreshness: B★ 1.7KClaude Code +9 - 0.782score
thinking-kepner-tregoe
tjboudreaux
Use when a selective defect needs IS/IS-NOT difference analysis or a consequential option choice needs must/want weighting and adverse-consequence comparison.
SkillBFreshness: B★ 1.7KClaude Code +9 - 0.778score
thinking-systems
tjboudreaux
When behavior is emergent across components—fixes elsewhere break, loops/delays dominate—map boundary, stocks/flows, feedback, archetypes, then rank leverage.
SkillBFreshness: B★ 1.7KClaude Code +9
Done for you
Rather not set it up yourself?
Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.
See how we build AI agents →Read the case studies
Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.
- launches shipped
- 50+
- launches shipped
- media placements
- 500+
- media placements
- founders on every account
- 2
- founders on every account
Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block
Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.
Get thinking-probabilistic running in your business
Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.
Cite this page
thinking-probabilistic skill. Agent Mart. https://agentmart.dev/skills/tjboudreaux-thinking-probabilistic (last updated 2026-10-24)