Skip to content
FunCoding

Search

Search docs, Skills and MCP

thinking-probabilistic

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.

AI 与智能体1.6kskills/thinking-probabilistic/SKILL.md

Install

Send this to Claude Code, Codex or Cursor. The agent checks the Skill for safety first and installs it only after you confirm.

读取 https://funcoding.ai/skills/tjboudreaux/cc-thinking-skills/thinking-probabilistic/install.md ,按里面的步骤帮我安装这个 Skill。

SKILL.md

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.

Similar Skills

brand-guidelines
anthropics/skills180k

brand-guidelines

Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.

AI & agents

internal-comms
anthropics/skills180k

internal-comms

A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).

AI & agents

template-skill
anthropics/skills180k

template-skill

Replace with description of the skill and when Claude should use it.

AI & agents

mcp-builder
anthropics/skills180k

mcp-builder

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

AI & agents

algorithmic-art
anthropics/skills180k

algorithmic-art

Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.

AI & agents

academy-guide
anthropics/skills180k

academy-guide

Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.

AI & agents