skills/quant/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 The-Utopia-Studio/skills 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.
data-ai
Raw mechanical interfaces fusing Swiss typographic print with military terminal aesthetics. Rigid grids, extreme type scale contrast, utilitarian color, analog degradation effects. For data-heavy dashboards, portfolios, or editorial sites that need to feel like declassified blueprints.
development
Teaches the AI to design like a high-end agency. Defines the exact fonts, spacing, shadows, card structures, and animations that make a website feel expensive. Blocks all the common defaults that make AI designs look cheap or generic.
development
Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.
development
Senior UI/UX Engineer. Architect digital interfaces overriding default LLM biases. Enforces metric-based rules, strict component architecture, CSS hardware acceleration, and balanced design engineering.