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
Cluster a conference's event records into a small set of coarse themes with finer sub-clusters, an explicit outlier bucket, and soft (multi-membership) affinities — using the hybrid embed-then-label pipeline (embed abstracts, reduce, density-cluster, then LLM-label the clusters) when embedding libraries are available, and an LLM-reasoned hierarchical fallback when they are not. Embeddings do the grouping; the LLM only names the groups. Conference-agnostic. Use when turning structured event records into a navigable theme map for preference elicitation and scheduling, when you need 6-8 reasonable themes rather than 20 muddy ones, or when overlapping talks must belong to more than one theme. Trigger keywords - theme clustering, cluster talks, embed then label, soft membership, outlier talks, conference themes, topic map.
development
Build a personal conference schedule as a constraint-optimization problem — hard constraints (no time overlap, room-to-room travel time, capacity/registration, the attendee's own must-attends and blackouts) plus a user-owned weighted objective trading interest against breadth, pacing (maximize contiguous free time), and serendipity. Surfaces unbreakable conflicts (two high-value overlapping talks the model cannot rank) as decisions for the human rather than silently picking, and reports what each choice traded away. Conference-agnostic. Use to turn a preference profile plus a theme map into a day-by-day plan, to resolve overlapping sessions, or to balance a packed vs paced schedule. Trigger keywords - schedule optimization, conference schedule, constraint optimization, overlapping talks, contiguous free time, conflict surfacing, packed vs paced.
development
Parse a heterogeneous conference program (markdown, HTML, PDF-derived text, or JSON) into normalized event records with per-field confidence scores and independent classification axes (topic, depth, format, prerequisites, recorded, capacity). Detects the program's format before extracting, treats every inferred field as uncertain (present vs inferred vs missing), and flags thin or missing abstracts so downstream enrichment can target them. Conference-agnostic. Use when ingesting a conference or event schedule into a structured store, normalizing a talk/session list, or extracting per-session metadata with calibrated confidence. Trigger keywords - program ingestion, parse schedule, session extraction, event records, conference program, talk metadata, per-field confidence.
development
Build a personalized preference profile from a small number of well-chosen, cluster-grounded questions instead of a long survey. Represents the person's interests as an uncertainty region over the theme map, picks the single highest-information-gain choice-based question (contrasting real talks from different clusters), balances exploiting known interests against exploring uncertain ones, deliberately injects outlier probes to fight selection bias, and stops as soon as the schedule would be stable. Also elicits the user-owned objective weights and hard constraints. Interactive — runs where it can actually ask the person. Conference-agnostic. Use to turn a theme map into a preference profile, to decide what to ask a conference attendee, or to elicit scheduling priorities. Trigger keywords - preference elicitation, ask few questions, information gain, choice-based questions, selection bias probe, objective weights, attendee preferences.