mcpField
P
pareto

pareto

github.com/majesticlabs-devProductivity5040 installsUpdated 7w ago
Repository

About pareto

A Pareto analysis skill for identifying activities that contribute disproportionately to results. It guides users to list inputs, estimate impact, rank activities, and validate conclusions with data, with examples spanning business, software, learning, and productivity.

Key features

  1. 01Input and output impact estimation
  2. 02Activity ranking by ratio
  3. 03Double down, optimize, or eliminate guidance
  4. 04Data validation prompts
  5. 05Examples across several domains

Use cases

  1. 01Prioritizing revenue-driving customers or products
  2. 02Finding high-impact marketing channels
  3. 03Focusing software testing on frequent bugs
  4. 04Allocating time to productive tasks

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/majesticlabs-dev/majestic-marketplace --skill pareto

After installing, type/paretoin Claude Code to confirm it loaded.

Details

From the project README

Pareto Principle Analyzer

Identify the vital 20% of activities that produce 80% of results using real case studies and proven 80/20 patterns.

Real 80/20 Case Studies

Business Revenue

Case: SaaS Company Revenue Analysis

  • 22% of customers generated 89% of revenue
  • Top 5 customers = 41% of total revenue
  • Action: Created dedicated success team for top 22%, reduced support for bottom 50%
  • Result: 34% revenue increase, 20% cost reduction

Case: E-commerce Product Analysis

  • 18% of SKUs generated 82% of profit
  • 40% of SKUs were break-even or losing money
  • Action: Discontinued bottom 30% of products
  • Result: 15% profit increase, 40% reduction in inventory costs
Software Development

Case: Bug Distribution (Microsoft Study)

  • 20% of bugs caused 80% of crashes
  • 1% of bugs caused 50% of crashes
  • Action: Prioritize top 1% first, then top 20%
  • Result: Most stable Windows release to date

Case: Code Optimization

  • 4% of code executed 50% of runtime
  • 20% of functions contained 80% of bugs
  • Action: Focused optimization and testing on hot paths
  • Result: 10x performance improvement with 20% of the effort
Sales & Marketing

Case: B2B Sales Pipeline

  • 23% of leads converted to 81% of deals
  • Pattern: Leads with technical champion + budget authority
  • Action: Qualification focused on these two factors
  • Result: Sales cycle shortened by 40%

Case: Marketing Channels

  • 2 channels (of 8 tested) drove 76% of conversions
  • 4 channels had negative ROI when fully costed
  • Action: 10x budget on top 2, killed bottom 4
  • Result: 3x marketing efficiency
Personal Productivity

Case: Developer Time Study

  • 2 hours of deep work = 80% of meaningful output
  • 6 hours of meetings/email = 20% of output
  • Pattern: First 2 hours of day most productive
  • Action: Protected morning block, batched communication
  • Result: Same output in 6 hours vs previous 10

80/20 Patterns by Domain

Business
AreaTypical 80/20 FindingAction
Customers20% generate 80% of revenueTier support, dedicated success for top tier
Products20% generate 80% of profitDiscontinue losers, double down on winners
Features20% used 80% of timeKill unused features, polish core ones
Support tickets20% of issues cause 80% of volumeFix root causes, not symptoms
Salespeople20% close 80% of dealsStudy their methods, replicate or replace
Learning
AreaTypical 80/20 FindingAction
Vocabulary2,000 words = 80% of spoken languageLearn frequency lists first
Concepts20% of concepts enable 80% of problemsMaster fundamentals before advanced
Practice20% of exercises build 80% of skillIdentify and repeat high-value drills
Books20% of content has 80% of valueRead intros, conclusions, skim middle
Productivity
AreaTypical 80/20 FindingAction
Tasks20% of tasks produce 80% of resultsDo high-impact first, eliminate rest
Time20% of hours are 80% productiveProtect peak hours, batch low-value
Meetings20% of meetings matterCancel the rest, send updates instead
Email20% of emails need responseProcess in batches, auto-archive rest

How to Find YOUR 80/20

Step 1: List Everything

Write down ALL activities in the area you're analyzing:

  • What do you spend time on?
  • What generates results?
  • What costs money/energy?
Step 2: Measure Impact

For each activity, estimate:

  • Input: Time, money, or energy spent (% of total)
  • Output: Results generated (% of total)
  • Ratio: Output ÷ Input

Example:

ActivityInput (%)Output (%)Ratio
Cold email30%5%0.17
Referrals10%45%4.5
Content25%30%1.2
Paid ads35%20%0.57
Step 3: Rank and Cut
  1. Double down: Top 20% by ratio (Referrals in example)
  2. Optimize: Middle 40% (Content, Paid ads)
  3. Eliminate: Bottom 40% (Cold email)
Step 4: Validate with Data

Don't trust gut alone:

  • Pull actual revenue by customer
  • Track actual time by activity
  • Measure actual results by channel

Output Format

# 80/20 ANALYSIS: [AREA]

## Data Summary

| Activity | Input (%) | Output (%) | Ratio | Action |
|----------|-----------|------------|-------|--------|
| [Activity 1] | X% | Y% | Y/X | DOUBLE DOWN |
| [Activity 2] | X% | Y% | Y/X | OPTIMIZE |
| [Activity 3] | X% | Y% | Y/X | ELIMINATE |

## Vital 20%

### 1. [Top activity]
- **Current state:** [What you're doing now]
- **Opportunity:** [What doubling down looks like]
- **This week:** [One specific action]

### 2. [Second activity]
- **Current state:** [What you're doing now]
- **Opportunity:** [What doubling down looks like]
- **This week:** [One specific action]

## Eliminate

- [Low-value activity 1] → Stop immediately
- [Low-value activity 2] → Delegate or automate
- [Low-value activity 3] → Reduce frequency

## Expected Impact

- **Time saved:** X hours/week
- **Results increase:** Y% improvement
- **When to measure:** [Specific date]

Conversation Starter

Use AskUserQuestion to begin:

"I'll help you find the 20% of activities driving 80% of your results.

What area do you want to analyze?

  • Business (revenue, customers, products)
  • Learning (skill, subject, language)
  • Productivity (time, tasks, energy)
  • Other (describe)"

Then ask:

  1. "What activities/inputs are involved?" (Get the full list)
  2. "What results/outputs matter?" (Define success)
  3. "Do you have data, or should we estimate?" (Quantify)

Comments

Markdown supported