eighty-twenty-power-curve
Apply 80/20 power-curve thinking to sales, marketing, customers, offers, traffic, time, and operations. Use when finding leverage, diagnosing uneven results, prioritizing high-upside segments, or replacing average-based reasoning with Pareto and power-law analysis.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- eighty-twenty-power-curve
- license
- MIT
- metadata
- { "tags": "eighty-twenty,pareto,sales,marketing,prioritization", "version": "0.1.0", "category": "Marketing", "displayName": "80/20 Power Curve" }
- description
- Apply 80/20 power-curve thinking to sales, marketing, customers, offers, traffic, time, and operations. Use when finding leverage, diagnosing uneven results, prioritizing high-upside segments, or replacing average-based reasoning with Pareto and power-law analysis.
- compatibility
- Codex, Claude Code, and other Agent Skills-compatible clients.
03 SKILL.md 正文
80/20 Power Curve
Use this skill to find where a small minority of inputs creates most of the value, cost, waste, demand, or opportunity. It is based on 80/20 Sales and Marketing by Perry Marshall.
Source Traceability
Primary source: 80/20 Sales and Marketing, chapters 1, 5, 14, and the appendix.
- Chapter 1 introduces compounding 80/20 behavior and warns against average thinking.
- Chapter 5 applies the power curve to business opportunity and resource shifts.
- Chapter 14 explains why positive feedback creates non-linear outcomes.
- The appendix gives the math-oriented version of the power curve.
Workflow
1. Name The Population
Define the set being ranked:
- Customers, leads, products, pages, ads, keywords, salespeople, tasks, support issues, markets, partners, content assets, or campaigns.
- Time window.
- Outcome metric: revenue, profit, conversions, usage, retention, attention, qualified pipeline, cost, complaints, or effort.
If the user provides only averages, ask for raw counts or ranked items. If raw data is unavailable, create an explicit estimate and label it.
2. Rank By The Outcome That Matters
Sort items from strongest to weakest. Prefer profit or qualified action over surface volume.
Use these questions:
- Which few items create most of the upside?
- Which few items create most of the waste?
- What is the best item worth compared with the median?
- Where does the distribution drop sharply?
- What would change if resources moved from the weak tail to the strong head?
3. Look For Nested 80/20
After finding the top 20 percent, look inside that group for the top 20 percent again. Stop when the data becomes too thin to interpret.
Useful nested cuts:
- Top customers inside the top customer segment.
- Best ads inside the best campaign.
- Highest-intent keywords inside the best keyword cluster.
- Best tasks inside the highest-value role.
4. Decide The Resource Shift
Recommend one of four moves:
- Double down on the strongest items.
- Split-test or refine the items near the threshold.
- Stop, delegate, or automate the weak tail.
- Gather better data before acting.
Do not recommend optimization of the average item unless it unlocks a stronger power-curve move.
Output Format
# 80/20 Power Curve Analysis
## Population
- Items ranked:
- Time window:
- Outcome metric:
- Data quality:
## Power-Curve Findings
| Rank/Segment | Item Or Group | Outcome | Interpretation |
|--------------|---------------|---------|----------------|
## Nested 80/20
- Strongest sub-segment:
- Weak tail:
- Biggest surprise:
## Recommended Resource Shift
- Move resources from:
- Move resources to:
- Expected effect:
- Data still needed:
Quality Bar
- Do not use averages as the main conclusion.
- Do not treat all customers, leads, channels, or tasks as equal.
- Separate upside concentration from waste concentration.
- Prefer profit, qualified action, or strategic value over raw volume.
- Label assumptions when exact ranked data is missing.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.