Installs into .claude/skills of the current project.
Are you the author of Resume Quantifier?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/tstapler-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?
Different roles surface different metrics — sales quota attainment, marketing campaign ROI, engineering uptime, and more. See [references/role-specific-metrics.md](references/role-specific-metrics.md) for a breakdown by role.
## Estimation Techniques
When you don't have exact numbers:
- **Conservative estimation** — estimate low to maintain credibility. If you think you saved 100 hours/month, say "75+ hours"; if growth was ~50%, say "~40%".
- **Range estimation** — "Managed team of 8-12", "Generated $100K-$150K in revenue"
- **Minimum bound** — "Served 100+ customers daily", "Managed at least 15 concurrent projects"
- **Percentage of activity** — calculate from known totals, e.g. company had 1000 customers, you managed 20% → "Managed 200 customer accounts"
- **Time-based calculation** — work backwards from frequency, e.g. 5 clients/week × 50 weeks → "Consulted with 250+ clients annually"
For ready-to-use quantification templates (before/after, scale, volume+impact, comparison) and the full output format for a quantification pass, see [references/templates-and-output.md](references/templates-and-output.md).
## Common "I Have No Numbers" Situations
Team contributor, no access to business metrics, no measurable outcomes, confidential results, entry-level with limited impact — each has a specific reframing strategy. See [references/no-numbers-situations.md](references/no-numbers-situations.md).
## Quantification Quality Checklist
For each bullet:
- Has at least ONE number
- Number is relevant (not just any number)
- Scale is clear (what does the number mean?)
- Estimation is conservative and defensible
- Number adds credibility, not confusion
- You can explain the number in an interview
## Numbers to Avoid
- Numbers that make you look bad
- Numbers you can't explain or defend
- Numbers that reveal confidential information
- Exaggerated or inflated numbers
- Numbers without context (e.g., "increased by 300%" without baseline)
- Too many numbers in one bullet (2-3 max)
## Key Principle
**Every bullet can be quantified.** If you think your work can't be measured, you haven't asked the right questions yet.
The goal isn't to have impressive numbers — it's to have SPECIFIC numbers that show the scope and impact of your work.
---
## Related Skills
| Skill | When to apply |
|-------|--------------|
| `resume-bullet-writer` | Rewrite bullets once metrics are identified |
| `resume-tailor` | Ensure quantified bullets match the target role's priorities |
| `resume-ats-optimizer` | Confirm quantified bullets still include required keywords |
| `executive-resume-writer` | Add P&L scale, revenue, and headcount for executive roles |
| `tech-resume-optimizer` | Add technical scale metrics (DAU, latency, uptime) for tech roles |