skills/reference-class-forecasting/SKILL.md
Anchors predictions in historical reality by identifying a class of similar past events and using their statistical frequency as a baseline (outside view) before analyzing case-specific details. Use when starting a forecast, establishing base rates, testing "this time is different" claims, or when user mentions reference classes, outside view, base rates, or starting a new prediction.
npx skillsauth add lyndonkl/claude reference-class-forecastingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
What would you like to do?
1. Find My Base Rate - Identify reference class and get statistical baseline
2. Test "This Time Is Different" - Challenge uniqueness claims
3. Calculate Funnel Base Rates - Multi-stage probability chains
4. Validate My Reference Class - Ensure you chose the right comparison set
5. Learn the Framework - Deep dive into methodology
6. Exit - Return to main forecasting workflow
Let's establish your statistical baseline.
Tell me the specific event or outcome you're predicting.
Example prompts:
I'll help you identify what bucket this belongs to.
Framework:
Key Questions:
I'll work with you to refine this until we have a specific, searchable class.
I'll help you find the base rate using:
Search Strategy:
"historical success rate of [reference class]"
"[reference class] failure statistics"
"[reference class] survival rate"
"what percentage of [reference class]"
Once we find the base rate, that becomes your starting probability.
The Rule:
Treat this base rate as your starting point. Adjust only when you have specific, evidence-based reasons from your "inside view" analysis.
Default anchors if no data found:
Next: Return to menu or proceed to inside view analysis.
Challenge uniqueness bias.
When someone (including yourself) believes "this case is special," we need to stress-test that belief.
Question 1: Similarity Matching
Question 2: The Reversal Test
Question 3: Burden of Proof The base rate says [X]%. You claim it should be [Y]%.
Calculate the gap: |Y - X|
Required evidence strength:
I'll tell you:
Next: Return to menu
For multi-stage processes without a single base rate.
Example: "Will Bill X become law?"
No direct data on "Bill X success rate," but we can model the funnel:
Stage 1: Bills introduced → Bills that reach committee
Stage 2: Bills in committee → Bills that reach floor vote
Stage 3: Bills voted on → Bills that pass
Final Base Rate:
P(law) = P(committee) × P(floor) × P(pass)
I'll help you:
Next: Return to menu
Ensure you chose the right comparison set.
Test 1: Homogeneity
Example: "Tech startups" is too broad (consumer vs B2B vs hardware are very different). Subdivide.
Test 2: Sample Size
Test 3: Relevance
I'll walk you through:
Output: Confidence level in your reference class (High/Medium/Low)
Next: Return to menu
Deep dive into the methodology.
📄 Outside View Principles
📄 Reference Class Selection Guide
📄 Common Pitfalls
Next: Return to menu
Find what usually happens to things like this, start there, and only move with evidence.
estimation-fermi if you need to calculate base rate from componentsbayesian-reasoning-calibration to update from base rate with new evidencescout-mindset-bias-check to validate you're not cherry-picking the reference class📁 resources/
Ready to start? Choose a number from the menu above.
testing
--- name: advisory-edit description: A strict advisory-only editing discipline for a writer who dictates ("speaks out") essays and wants help WITHOUT having their voice changed. The editor directs structure, flags grammar, and suggests strategic language — but never modifies the writer's text unless the writer explicitly says "apply" / "make that change" / "rewrite this." Produces a line-referenced, suggestion-only critique where every item is marked the writer's call. Four passes: structural, l
testing
Provides the house style for analyst-grade strategist writing — third-person register with sparing first-person, no em dashes, no "not X, not Y, not Z" negation cascades, numbered footnote citations rather than inline source parentheticals, specific opinion-signaling phrases, and topic-forward paragraph structure modeled on voice patterns observed in Damodaran's Musings on Markets and Thompson's Stratechery. Use when consolidating working notes into a finished long-form strategist or analyst report that must read as written by a senior human analyst rather than an AI assistant.
testing
Renders a markdown report to a PDF using pandoc with xelatex (11pt serif body, 1-inch margins, numbered footnotes, formal heading hierarchy). Requires a one-time install of pandoc and a LaTeX engine on the user's machine — basictex on macOS or texlive-xetex on Linux. Does not attempt automatic install. Fails loudly with the exact install commands if pandoc or xelatex is missing on the user's PATH. Use when producing a finished strategist or analyst report PDF from a polished markdown source.
testing
Produces step-by-step computational walkthroughs of vector and matrix operations as a sequence of numbered "frames", showing the explicit state at each step. The text-equivalent of a 3Blue1Brown animation — each frame shows what changed and why, so the learner can re-trace the operation by hand. Use when the learner needs to *see* a computation unfold (eigenvalue computation, attention with 3 tokens, gradient descent step, SVD on a 2×2, layer norm on a 3-vector, softmax of a small input), when an explanation has been given but the learner needs to ground it in a worked example, or when introducing an operation that's intimidating in symbol form but trivial in pencil-and-paper form.