resume-quantifier

这段内容是审核时保存的快照。外部来源才是完整且最新的版本。

---
name: resume-quantifier
description: Find opportunities to add metrics and estimate numbers when exact data unavailable
---

# Resume Quantifier

## When to Use This Skill

Use this skill when the user:
- Needs to add metrics and numbers to their resume
- Has bullets without quantifiable results
- Doesn't know what numbers to include
- Says they "don't have metrics" or "can't measure impact"
- Mentions: "add metrics", "quantify", "add numbers", "measure impact", "no data"

## Core Capabilities

- Find hidden metrics in any experience
- Estimate numbers when exact data unavailable
- Create before/after comparisons
- Identify measurable impact points
- Transform vague statements into quantified achievements
- Guide users to discover their metrics

## Why Quantification Matters

**The Problem:**
- "Managed projects" vs "Managed 12 projects worth $2M"
- "Improved processes" vs "Reduced cycle time by 40%"
- "Helped customers" vs "Resolved 50+ tickets daily with 98% satisfaction"

**Studies Show:**
- Resumes with numbers get 30% more attention
- Quantified bullets are 40% more memorable
- Numbers provide credibility and scale

## The Quantification Framework

### Categories of Metrics

**1. Money**
- Revenue generated
- Costs reduced/saved
- Budget managed
- Deal sizes closed
- Profit margins improved

**2. Time**
- Hours saved
- Cycle time reduced
- Project duration
- Response times
- Time to market

**3. Percentages**
- Growth rates
- Improvement percentages
- Efficiency gains
- Error reduction
- Conversion rates

**4. Volume/Scale**
- Number of customers/users
- Projects managed
- Team size
- Transactions processed
- Items produced

**5. Quality**
- Satisfaction scores
- Error rates
- Accuracy rates
- Compliance rates
- SLA adherence

**6. Frequency**
- Per day/week/month
- Annual totals
- Meeting cadences
- Report cycles

## Finding Hidden Metrics

### The Discovery Questions

For any experience, ask:

**Scale Questions:**
- How many people/projects/customers?
- What was the budget/revenue involved?
- How large was the team?
- How many locations/regions?

**Impact Questions:**
- What changed because of your work?
- What would have happened without you?
- What problems did you solve?
- What got better/faster/cheaper?

**Comparison Questions:**
- How was it before vs. after?
- How did you compare to others/previous results?
- What was the baseline you improved?

### Role-Specific Metric Discovery

**Sales:**
- Quota attainment percentage
- Revenue generated
- Number of deals closed
- Average deal size
- Pipeline generated
- New accounts acquired
- Retention rate

**Marketing:**
- Leads generated
- Campaign ROI
- Engagement rates
- Follower growth
- Website traffic increase
- Conversion rates
- Brand awareness metrics

**Customer Service:**
- Tickets resolved per day
- Customer satisfaction score
- Average response time
- First call resolution rate
- NPS score contribution

**Operations:**
- Efficiency improvements
- Cost reductions
- Process cycle times
- Error rate reductions
- Throughput increases

**Engineering:**
- System uptime
- Performance improvements
- Bug resolution rate
- Deployment frequency
- Code coverage

**Project Management:**
- Number of projects
- Budget sizes
- Team sizes
- On-time delivery rate
- Stakeholders managed

**HR/Admin:**
- Hiring numbers
- Time to fill
- Employee satisfaction scores
- Training completion rates
- Onboarding efficiency

## Estimation Techniques

When you don't have exact numbers:

### Conservative Estimation

**Principle:** Estimate low to maintain credibility

**Example:**
- You think you saved 100 hours/month → say "75+ hours"
- You think growth was 50% → say "~40%"
- You think you served 500 customers → say "400+"

### Range Estimation

**Format:** "X-Y" or "X to Y"

**Examples:**
- "Managed team of 8-12"
- "Generated $100K-$150K in revenue"
- "Saved 20-30 hours weekly"

### Minimum Bound

**Format:** "X+" or "at least X"

**Examples:**
- "Served 100+ customers daily"
- "Manage