fermi-estimation

Decompose unknown quantities into estimable factors and compute bounded ranges.

7|2|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/AndurilCode/craftwork --skill fermi-estimation-andurilcode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fermi-estimation
Source: https://github.com/AndurilCode/craftwork/tree/main/skills/fermi-estimation
Command: npx skills add https://github.com/AndurilCode/craftwork --skill fermi-estimation-andurilcode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fermi estimation helps you produce a quantitative, order-of-magnitude answer when you lack precise data, so you can sanity-check plans, make feasibility calls, or answer “how much/how long” questions.

Core Features & Use Cases

  • Decompose unknown quantities into estimable factors (e.g., rate × time, count × average) with consistent units.
  • Compute and bound ranges (low/central/high) to surface the most influential assumptions.
  • Sanity-check and identify key drivers by checking reference points and determining which factor would need validation.
  • Use case: You’re planning an agent pipeline and need a quick token/cost estimate to decide whether the approach is practical before measurement.

Quick Start

Ask the assistant to estimate the token cost of one agent pipeline run by decomposing the total into “number of turns × average tokens per turn,” then provide a low/central/high range with the main key driver.

Frequently Asked Questions about fermi-estimation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I estimate token cost and compute effort for an agent pipeline when I lack precise metrics?

To estimate token cost and compute effort without precise metrics, decompose the target quantity into independent estimable factors like rate × time or count × average, then compute low, central, and high bounded ranges to surface key driver assumptions.

What is Fermi estimation and when should I use it for scenario planning?

Fermi estimation is a quantitative reasoning method that produces order-of-magnitude answers for scenario planning when precise data is missing, allowing you to sanity-check plans and make fast feasibility calls for scaling and resource questions.

How do I perform a sanity check on cost feasibility for uncertain scenarios?

Perform a cost feasibility sanity check by defining your target quantity and units, decomposing it into estimable factors, computing bounded ranges, and checking reference points to identify which key driver factor would need validation.

Can I use order-of-magnitude estimation for budgeting resources across uncertain scaling scenarios?

Yes, you can use order-of-magnitude estimation for token budgeting and resource scaling by breaking down unknown quantities into independent factors like number of turns multiplied by average tokens per turn to generate a practical low to high range.

What is the best way to identify the key driver factor in a quantitative estimate?

The best way to identify the key driver factor in a quantitative estimate is to decompose the target into independent factors, compute bounded low, central, and high ranges, and perform sanity checks against reference points to determine which assumption most influences the result.

What are the limitations of using order-of-magnitude estimates for agent pipeline planning?

Order-of-magnitude estimates are limited to sanity checking and feasibility calls rather than precise measurement, meaning the bounded ranges identify which key driver factor requires validation but do not replace actual runtime token usage data.