Power-Law Distribution

Activate when: user is allocating capital or resources across a portfolio and wants to know where to concentrate; user says 'our average customer / deal / em...

deciqAI

@deciqai

What This Skill Does

Statistical reasoning tool that identifies whether a portfolio, customer base, or risk model follows a power-law distribution and guides resource allocation toward the few high-impact outliers. It walks users through distribution diagnostics, tail-exponent estimation, and strategy adjustments to avoid Gaussian-model errors.

Replaces naive averaging and Gaussian risk models (VaR, standard deviation) that systematically underestimate extreme outcomes in domains where a tiny fraction of items drive most of the value.

When to Use It

  • Allocate venture capital or startup portfolio dollars where a few investments drive all returns
  • Prioritize customers or sales channels when 20% of accounts generate 80% of revenue
  • Assess business risk for extreme events that standard deviation or VaR models miss
  • Decide whether to design strategy for the average case or the extreme tail
  • Evaluate AI compute or chip concentration where value captures into a thin tail of companies
  • Identify which features or content pieces produce disproportionate user engagement

Install

$ openclaw skills install @deciqai/power-law-distribution

Power-Law Distribution

Overview

A power-law distribution is a statistical distribution where probability of size x is proportional to x^(−α): large events are rare but far more probable than a Gaussian model predicts, and the largest events dominate the total — there is no "typical" case.

First quantified by Pareto (1896) in wealth; formalized by Mandelbrot (1963) for financial returns; surveyed universally by Newman (2005) across cities, earthquakes, citations, and web traffic.

Composes with pareto-principle (80-20 is the most famous application; this skill provides the math foundation), black-swan (black swans are the extreme upper-tail events power laws make far more probable), expected-value-and-kelly (Kelly sizing breaks under infinite-variance power laws), and antifragile (antifragile strategies exploit the upper tail).

When to Use

  • Allocating capital or resources across a portfolio — power-law returns mean design must prioritize outliers
  • Prioritizing customers, channels, content, or features where a small number account for most value
  • Assessing business risk — Gaussian risk models (VaR, std dev) systematically underestimate extreme risk
  • Any domain where "average" is the planning assumption and extreme outcomes are possible
  • Evaluating AI/compute concentration — AI capex, chip export controls, frontier-lab funding, or "AI bubble" questions where value is capturing into a thin tail of companies

Not when: distribution is demonstrably Gaussian; stakes are low enough that shape doesn't affect the decision; audience will misuse power-law framing as nihilism.

Coaching Novices (Adaptive Front Door)

  • Engine mode: user has a concrete portfolio, risk, or allocation decision → run The Process directly.
  • Coach mode: user is new to the concept → guide step by step.

In Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.

  1. One-liner: a tiny number of items account for a disproportionate fraction of the total. Using averages in a power-law world is systematic error.
  2. Check fit: extreme outcomes dominate the total; no natural "typical" scale; recursive self-similarity (top 20% of top 20% still follows the same ratio).
  3. Elicit: what is being distributed? What does the top 1%, 5%, 10% account for as a fraction of the total?

[WAIT — do not advance until user responds]

  1. One question: are you designing for the average case or the extreme case? What would strategy look like if top 1% drove 50% of total value?

[WAIT — do not advance until user responds]

  1. Close: distribution type confirmed + implications for allocation / risk named + Gaussian errors identified and corrected.

[WAIT — do not advance until user responds]

The Process

Step 1 — Identify the distribution: What is distributed? Preliminary hypothesis: Gaussian or power-law?

Step 2 — Check power-law indicators: Top __% accounts for __% of total. High mean-to-median ratio? Long right tail? Log-log plot roughly linear?

Step 3 — Estimate tail exponent (if data available): α < 2 → infinite variance; α < 1 → infinite mean. Practical implication:

Step 4 — List Gaussian errors being made: Using mean as planning assumption? VaR as risk measure? Designing for "typical" case? Averaging portfolio returns?

Step 5 — Redesign for power-law structure: Concentrate resources on upper-tail upside. Maximize shots at outliers. Size tail risk using extreme value theory, not std dev.

Step 6 — Define monitoring triggers: Track top-N performance, not average. Set review cadence and signal for when distribution shifts.

Output Template

# Power-Law Analysis: <domain>
Distribution: top __% = __% of total | mean-to-median ratio: | long tail: Y/N
Tail exponent α ≈  | implication:
Gaussian errors being made: 1. 2. 3.
Redesigned approach: concentrate on / defocus from / tail risk sized at
Monitoring: metric | review trigger

→ Method in Action: Pareto 1896, Mandelbrot 1963, and VC Return Data

→ 2026 lens: AI & venture returns concentration — a few labs plus Nvidia capture the tail (2023–2026)

Pack: Power-Law Patterns Across Business Domains

DomainPower-law variableTop-N shareGaussian errorCorrect approach
VC / startup investingReturn multiplesTop 1% → ~50% of fundAverage IRRMaximize shots at outliers; write off tail fast
B2B revenueCustomer LTVTop 10% → 50-80% revenueAvg revenue per customerConcentrate on top-tier; cost-to-serve long tail
Knowledge workIndividual outputTop 10% → 50%+ of valueAverage performance reviewIdentify and amplify top performers
Content / mediaPost viralityTop 1% → 50%+ of reachAverage engagement rateOptimize conditions for outlier content
Operational riskEvent severityTop 1% → 99% of damageVaR based on std devExtreme value theory; fat-tail scenarios

→ Primary sources: references/sources.md

Common Rationalizations

[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.

Fake moveReality
[D] "Our average customer LTV is $X — healthy business."If power-law, average is dominated by top 10%. Median customer may be barely profitable.
[D] "We track average deal size to forecast pipeline."Deal size is power-law. Losing one large deal can collapse a forecast the average made look safe.
[D] "Our VaR model shows maximum likely loss is $Y."VaR assumes Gaussian. Real tail risk is orders of magnitude larger. LTCM and 2008 validated this.
[D] "We lost money on 65% of investments, so portfolio is failing."65-75% loss rate is consistent with a top-quartile VC fund if the winners are large enough.
[D] "Risk model is validated because extreme events have been rare."Power-law distributions can go long periods without a tail event — then produce a devastating one.
→ Add [O] entries here after each real use — paste the actual failure patternWhat went wrong and why

Red Flags

  • Planning assumptions built on averages where mean-to-median ratio is high
  • Risk models use std dev, VaR, or normal distribution for outcomes that historically show fat tails
  • Portfolio strategy aims to make most investments "work" rather than maximizing outlier access
  • Top 10% of customers, deals, or investments are not tracked as a distinct priority category

Verification

  • Distribution examined empirically: top-N share calculated
  • Mean-to-median ratio checked: high ratio confirms power-law
  • Log-log plot examined (if data available)
  • Specific Gaussian errors listed and corrected
  • Resource allocation redesigned to concentrate on upper tail
  • Risk model tail assumptions updated to power-law
  • Monitoring metric tracks top-N, not average

Stop rule: if empirical data shows mean ≈ median and symmetric shape, Gaussian tools are appropriate. Do not force power-law framing onto genuinely Gaussian domains.


Part of deciqAI Knowledge Skills — 227 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. See it run → https://www.deciqai.com/c/power-law-distribution · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.

Agents: latest version & machine-readable metadata → https://www.deciqai.com/s/power-law-distribution.json

Top skills in this category

Stock Analysis

@udiedrichsen

Analyze stocks and cryptocurrencies using Yahoo Finance data. Supports portfolio management, watchlists with alerts, dividend analysis, 8-dimension stock scoring, viral trend detection (Hot Scanner), and rumor/early signal detection. Use for stock analysis, portfolio tracking, earnings reactions, crypto monitoring, trending stocks, or finding rumors before they hit mainstream.

25758k

Stock Market Pro

@kys42

Yahoo Finance (yfinance) powered stock analysis skill: quotes, fundamentals, ASCII trends, high-resolution charts (RSI/MACD/BB/VWAP/ATR), plus optional web a...

15532k

A股量化 AkShare

@mbpz

A股量化数据分析工具,基于AkShare库获取A股行情、财务数据、板块信息等。用于回答关于A股股票查询、行情数据、财务分析、选股等问题。

10131k

Stock Watcher

@robin797860

Manage and monitor a personal stock watchlist with support for adding, removing, listing stocks, and summarizing their recent performance using data from 10jqka.com.cn. Use when the user wants to track specific stocks, get performance summaries, or manage their watchlist.

8736k

Intelligent Stocks Screener

@financial-ai-analyst

基于东方财富数据库,支持通过自然语言输入筛选A港美股、基金、债券等多种资产,支持多元指标筛选,含技术面、消息面、基本面及市场情绪等,可用于全球资产速筛、跨市场监控、投资组合构建、策略回测等场景。返回结果包含数据说明及 csv 文件。Natural language screener for investment...

10626k