Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问clear审计提醒

reference-class-forecasting参考类预测

Agent Skill

reference-class-forecasting 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

1,273

周安装

51

GitHub Stars

85

下载量

412
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:reference-class-forecasting(参考类预测)
来源仓库:https://github.com/lyndonkl/claude
仓库路径:skills/reference-class-forecasting
安装命令:
npx skills add https://github.com/lyndonkl/claude --skill reference-class-forecasting
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/lyndonkl/claude --skill reference-class-forecasting

简介

reference-class-forecasting 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。

  • 适用于基于相似项目历史数据的工期估算、资源需求预测或风险概率评估。
  • 利用过往重构案例的时间线和成本分布提供参考基准。
  • 安装命令:npx skills add https://github.com/lyndonkl/claude --skill reference-class-forecasting。
  • 预测结果仅供参考,实际执行受团队能力和外部环境变化影响较大。

SKILL.md

Reference Class Forecasting

Table of Contents


Interactive Menu

What would you like to do?

Core Workflows

1. Find My Base Rate - Identify reference class and get statistical baseline

  • Guided process to select correct reference class
  • Search strategies for finding historical frequencies
  • Validation that you have the right anchor

2. Test "This Time Is Different" - Challenge uniqueness claims

  • Reversal test for uniqueness bias
  • Similarity matching framework
  • Burden of proof calculator

3. Calculate Funnel Base Rates - Multi-stage probability chains

  • When no single base rate exists
  • Sequential probability modeling
  • Product rule for compound events

4. Validate My Reference Class - Ensure you chose the right comparison set

  • Too broad vs too narrow test
  • Homogeneity check
  • Sample size evaluation

5. Learn the Framework - Deep dive into methodology

6. Exit - Return to main forecasting workflow


1. Find My Base Rate

Let's establish your statistical baseline.

Step 1: What are you forecasting?

Tell me the specific event or outcome you're predicting.

Example prompts:

  • "Will this startup succeed?"
  • "Will this bill pass Congress?"
  • "Will this project launch on time?"

Step 2: Identify the Reference Class

I'll help you identify what bucket this belongs to.

Framework:

  • Too broad: "All companies" → meaningless
  • Just right: "Seed-stage B2B SaaS startups in fintech"
  • Too narrow: "Companies founded by people named Steve in 2024" → no data

Key Questions:

  1. What type of entity is this? (company, bill, project, person, etc.)
  2. What stage/size/category?
  3. What industry/domain?
  4. What time period is relevant?

I'll work with you to refine this until we have a specific, searchable class.


Step 3: Search for Historical Data

I'll help you find the base rate using:

  • Web search for published statistics
  • Academic studies on success rates
  • Government/industry reports
  • Proxy metrics if direct data unavailable

Search Strategy:

"historical success rate of [reference class]"
"[reference class] failure statistics"
"[reference class] survival rate"
"what percentage of [reference class]"

Step 4: Set Your Anchor

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:

  • Novel innovation: 10-20% (most innovations fail)
  • Established industry: 50% (uncertain)
  • Regulated/proven process: 70-80% (systems work)

Next: Return to menu or proceed to inside view analysis.


2. Test "This Time Is Different"

Challenge uniqueness bias.

When someone (including yourself) believes "this case is special," we need to stress-test that belief.

The Uniqueness Audit

Question 1: Similarity Matching

  • What are 5 historical cases that are most similar to this one?
  • For each, what was the outcome?
  • How is your case materially different from these?

Question 2: The Reversal Test

  • If someone claimed a different case was "unique" for the same reasons you're claiming, would you accept it?
  • Are you applying special pleading?

Question 3: Burden of Proof The base rate says [X]%. You claim it should be [Y]%.

Calculate the gap: |Y - X|

Required evidence strength:

  • Gap < 10%: Minimal evidence needed
  • Gap 10-30%: Moderate evidence needed (2-3 specific factors)
  • Gap > 30%: Extraordinary evidence needed (multiple independent strong signals)

Output

I'll tell you:

  1. Whether "this time is different" is justified
  2. How much you can reasonably adjust from the base rate
  3. What evidence would be needed to justify larger moves

Next: Return to menu


3. Calculate Funnel Base Rates

For multi-stage processes without a single base rate.

When to Use

  • No direct statistic exists (e.g., "success rate of X")
  • Event requires multiple sequential steps
  • Each stage has independent probabilities

The Funnel Method

Example: "Will Bill X become law?"

No direct data on "Bill X success rate," but we can model the funnel:

  1. Stage 1: Bills introduced → Bills that reach committee

- P(committee | introduced) =?

  1. Stage 2: Bills in committee → Bills that reach floor vote

- P(floor | committee) =?

  1. Stage 3: Bills voted on → Bills that pass

- P(pass | floor vote) =?

Final Base Rate:

P(law) = P(committee) × P(floor) × P(pass)

Process

I'll help you:

  1. Decompose the event into sequential stages
  2. Search for statistics on each stage
  3. Multiply probabilities using the product rule
  4. Validate the model (are stages truly independent?)

Common Funnels

  • Startup success: Seed → Series A → Profitability → Exit
  • Drug approval: Discovery → Trials → FDA → Market
  • Project delivery: Planning → Development → Testing → Launch

Next: Return to menu


4. Validate My Reference Class

Ensure you chose the right comparison set.

The Three Tests

Test 1: Homogeneity

  • Are the members of this class actually similar enough?
  • Is there high variance in outcomes?
  • Should you subdivide further?

Example: "Tech startups" is too broad (consumer vs B2B vs hardware are very different). Subdivide.


Test 2: Sample Size

  • Do you have enough historical cases?
  • Minimum: 20-30 cases for meaningful statistics
  • If N < 20: Widen the class or acknowledge high uncertainty

Test 3: Relevance

  • Have conditions changed since the historical data?
  • Are there structural differences (regulation, technology, market)?
  • Time decay: Data from >10 years ago may be stale

Validation Checklist

I'll walk you through:

  • Class has 20+ historical examples
  • Members are reasonably homogeneous
  • Data is from relevant time period
  • No major structural changes since data collection
  • Class is specific enough to be meaningful
  • Class is broad enough to have data

Output: Confidence level in your reference class (High/Medium/Low)

Next: Return to menu


5. Learn the Framework

Deep dive into the methodology.

Resource Files

📄 Outside View Principles

  • Statistical thinking vs narrative thinking
  • Why the outside view beats experts
  • Kahneman's planning fallacy research
  • When outside view fails

📄 Reference Class Selection Guide

  • Systematic method for choosing comparison sets
  • Balancing specificity vs data availability
  • Similarity metrics and matching
  • Edge cases and judgment calls

📄 Common Pitfalls

  • Base rate neglect examples
  • "This time is different" bias
  • Overfitting to small samples
  • Ignoring regression to the mean
  • Availability bias in class selection

Next: Return to menu


Quick Reference

The Outside View Commandments

  1. Base Rate First: Establish statistical baseline BEFORE analyzing specifics
  2. Assume Average: Treat case as typical until proven otherwise
  3. Burden of Proof: Large deviations from base rate require strong evidence
  4. Class Precision: Reference class should be specific but data-rich
  5. No Narratives: Resist compelling stories; trust frequencies

One-Sentence Summary

Find what usually happens to things like this, start there, and only move with evidence.

Integration with Other Skills

  • Before: Use estimation-fermi if you need to calculate base rate from components
  • After: Use bayesian-reasoning-calibration to update from base rate with new evidence
  • Companion: Use scout-mindset-bias-check to validate you're not cherry-picking the reference class

Resource Files

📁 resources/


Ready to start? Choose a number from the menu above.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Claude Code

31.74%
按下载量换算131

Gemini CLI

25.43%
按下载量换算105

Antigravity

18.09%
按下载量换算75

windsurf

12.03%
按下载量换算50

OpenCode

7.13%
按下载量换算29

github-copilot

3.2%
按下载量换算13

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。

来源信息

继续浏览同类 Skills