ワンクリックで
forecasting
Superforecasting with calibrated reasoning, Brier score tracking, and prediction ledger management
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Superforecasting with calibrated reasoning, Brier score tracking, and prediction ledger management
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | forecasting |
| description | Superforecasting with calibrated reasoning, Brier score tracking, and prediction ledger management |
| consumer | cc_background_research |
| phase | 7 |
| skill_type | uplift |
Make specific, falsifiable predictions with calibrated confidence levels. Track accuracy over time using Brier scores. Apply superforecasting methodology (Tetlock/Good Judgment Project) to any domain — technology trends, project outcomes, market shifts, competitive moves, risk assessment.
| Signal Type | Weight | Description |
|---|---|---|
| Leading indicator | High | Predicts before the event (e.g., job postings predict growth) |
| Lagging indicator | Medium | Confirms after the event (e.g., quarterly earnings) |
| Base rate | High | Historical frequency of similar events |
| Expert opinion | Medium | Domain expert assessment (weight by track record) |
| Data point | High | Quantitative measurement directly relevant |
| Anomaly | High | Deviation from expected pattern — investigate |
| Structural change | Very High | Rules of the game changing (regulation, technology shift) |
| Sentiment shift | Medium | Public/market mood change (often noise, sometimes signal) |
Signal strength:
| Probability | Meaning | Betting Odds |
|---|---|---|
| 5% | Almost certainly not | 19:1 against |
| 15% | Very unlikely | ~6:1 against |
| 25% | Unlikely but plausible | 3:1 against |
| 35% | Somewhat unlikely | ~2:1 against |
| 45% | Toss-up, leaning no | ~1.2:1 against |
| 55% | Toss-up, leaning yes | ~1.2:1 for |
| 65% | Somewhat likely | ~2:1 for |
| 75% | Likely | 3:1 for |
| 85% | Very likely | ~6:1 for |
| 95% | Almost certain | 19:1 for |
Adjustment rules: +/-5-15% per strong signal, +/-2-5% per moderate signal. If gut says 80% but analysis says 55%, trust the analysis.
Before finalizing ANY prediction, check against these 8 biases:
| Bias | Check | Fix |
|---|---|---|
| Anchoring | Am I stuck on the first number I thought of? | Re-derive from base rates |
| Availability | Am I overweighting recent/vivid examples? | Search for boring counterexamples |
| Confirmation | Am I only finding evidence that agrees? | Explicitly search for disconfirming evidence |
| Narrative | Am I constructing a compelling story that feels true? | Check: does the data support this without the story? |
| Overconfidence | Am I more certain than my evidence warrants? | Would I bet real money at these odds? |
| Scope insensitivity | Am I treating "some" and "a lot" as the same? | Quantify: how much exactly? |
| Recency | Am I overweighting what happened last? | Check 5-year and 10-year base rates |
| Status quo | Am I assuming things will stay the same? | What would need to change, and how likely is each change? |
For each prediction, construct:
Brier = (predicted_probability - actual_outcome)^2
Where actual_outcome is 0 (didn't happen) or 1 (happened).
| Score | Quality |
|---|---|
| < 0.10 | Excellent |
| 0.10 - 0.15 | Good |
| 0.15 - 0.25 | Average |
| 0.25 | Coin flip (no skill) |
| > 0.30 | Worse than guessing |
Track cumulative Brier score across all resolved predictions. Review monthly. If cumulative Brier > 0.25, recalibrate methodology.
When explicitly requested or when consensus confidence exceeds 85%:
| Domain | Priority Sources |
|---|---|
| Technology | GitHub trending, HN, arXiv, Crunchbase, job postings, patent filings |
| Finance | FRED, SEC filings, central bank statements, VIX, yield curves |
| Geopolitics | UN resolutions, RAND, think tank reports, diplomatic cables |
| Climate/Energy | IPCC, IEA, CDP, BloombergNEF, utility filings |
| AI/ML | arXiv, model benchmarks, API pricing trends, conference papers |
prediction_id: <PRED-YYYY-MM-DD-NNN>
created: <YYYY-MM-DD>
domain: <technology | finance | geopolitics | climate | ai_ml | general>
time_horizon: <1_week | 1_month | 3_months | 1_year>
prediction: <specific, falsifiable statement>
confidence: <probability 0.05-0.95>
reasoning_chain:
reference_class:
base_rate: <probability>
analogues:
- <historical analogue and outcome>
specific_evidence:
- signal: <description>
type: <leading | lagging | base_rate | expert | data | anomaly | structural | sentiment>
strength: <strong | moderate | weak>
adjustment: <+/- percentage>
synthesis: <narrative combining outside and inside views>
key_assumptions:
- assumption: <what must hold>
if_violated: <probability shift>
resolution:
date: <YYYY-MM-DD>
criteria: <exact observable condition>
data_source: <where to verify>
bias_check: <which biases were checked and adjustments made>
status: active | resolved | expired
updates:
- date: <YYYY-MM-DD>
old_confidence: <previous>
new_confidence: <updated>
reason: <what changed>
resolution_result:
date: <YYYY-MM-DD>
outcome: true | false
evidence: <what happened>
brier_score: <calculated score>
lesson: <what to learn from this>
src/genesis/learning/ — Outcome tracking for Brier score integrationsrc/genesis/identity/REFLECTION_STRATEGIC.md — Strategic reflection contextThis skill should be used when developing, debugging, refactoring, or building Genesis itself — tasks like "fix this in Genesis", "add a new MCP tool", "wire up the runtime", "Genesis won't start", "create a worktree", "debug the bridge", or "add a capability". Applies to any task modifying files under src/, .claude/, or tests/. Do NOT load for Genesis-as-tool work ("summarize this", "write a LinkedIn post", "research X") or general questions unrelated to Genesis internals.
Foundational voice authority and AI humanizer — writes content in the user's authentic voice with built-in AI detection, and supports stealth / anti- attribution writing (forum personas, anonymous posts, "write as not-me"). Use when asked to write/draft/generate content, invoke /voice, /write-as-me, or /humanize, run voice calibration, check "does this sound like me?", "make this sound human" / "de-AI this", "write a forum post as [persona]", or run AI detection ("does this sound like AI?", "check for AI patterns", "anti-slop check"). Do NOT use this skill for code, technical docs, or any output the user has not asked to be written in their voice — code styling defers to the separate code-voice skill.
Forward Deployed Engineer delivery contract for AWS engagements, build-first artifacts, grounded cost estimates, Well-Architected review, evolution roadmap
This skill should be used before answering "does Genesis have X", "does Genesis lack X", auditing Genesis capabilities, comparing Genesis to an external system, or reviewing/summarizing the architecture. It routes to the canonical judgment-layer subsystem map so audits start from the map, not from a cold grep. Also fires after changing a subsystem's capabilities, to keep the map current.
First-run onboarding — guides new users through Genesis setup on their first CC session. Configures user profile, essential API keys, Telegram, GitHub backup, and service verification. Triggered automatically when ~/.genesis/setup-complete is absent. Re-runnable by asking Genesis to "run setup" or "reconfigure [section]".
Apply when Genesis writes as itself — outreach, public content, community posts, emails, DMs. Not for writing in the user's voice (that's voice-master). Activate when Genesis is the author, not the ghostwriter.