Resume quantifier

Find opportunities to add metrics and estimate numbers when exact data unavailable

How to use it

  1. Hit Copy the whole skill.
  2. Claude: ⋯ → Download .md, then Customize → Skills → Add → Upload skill.
    ChatGPT: make a Project and paste it into Instructions.
    Neither? Paste it at the top of a new chat — it works for that chat.
  3. Describe your job in plain words. The AI follows the skill from there.
Claude Code — installs the whole folder, not just SKILL.md
npx degit Paramchoudhary/ResumeSkills/skills/resume-quantifier#main ~/.claude/skills/resume-quantifier

For one project only, change the path to .claude/skills/resume-quantifier.

Not working?
  • Check which app you pasted it into — the steps above name the right one.
  • Some skills need the paid tier of Claude or ChatGPT.
Step-by-step guide with screenshots · Ask in the forum

Paste into Claude, ChatGPT or Cursor.

Show the full text351 lines
resume-quantifier/SKILL.md351 lines8.3 KBpushed 189d agoRawView on GitHub

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"
  • "Managed at least 15 concurrent projects"
  • "Generated $500K+ in annual revenue"

Percentage of Activity

Format: Calculate from known totals

Example:

  • Company had 1000 customers → You managed 20% → "Managed 200 customer accounts"
  • Team had 10 people → You supervised 4 → "Supervised 40% of team"

Time-Based Calculation

Format: Work backwards from frequency

Example:

  • Met with 5 clients/week × 50 weeks = "Consulted with 250+ clients annually"
  • Processed 30 invoices/day × 250 days = "Processed 7,500+ invoices annually"

Quantification Templates

Before and After Template

"Improved [X] from [before number] to [after number], resulting in [Y]% improvement"

Example:
"Improved page load time from 8 seconds to 2 seconds, resulting in 75% reduction and 20% increase in user engagement"

Scale Template

"[Verb] [number] [things], resulting in [impact]"

Example:
"Managed 25 concurrent projects worth $3M, delivering 95% on-time with zero budget overruns"

Volume + Impact Template

"Processed [number] [items] per [time period], achieving [quality metric]"

Example:
"Resolved 50+ customer tickets daily, maintaining 98% satisfaction rating and 4-hour average response time"

Comparison Template

"Ranked #[X] out of [Y] in [metric], [context]"

Example:
"Ranked #2 out of 45 sales representatives nationally, generating $3.2M in annual revenue"

Common "I Have No Numbers" Situations

Situation 1: "I was just one person on a team"

Solution: Focus on YOUR contribution

Example:

  • "Part of team that launched product" →
  • "Contributed 40% of front-end code for product launch reaching 100K users"

Situation 2: "I don't have access to business metrics"

Solution: Quantify activities and inputs

Example:

  • "Supported sales team" →
  • "Created 50+ sales presentations and managed pipeline of 200+ prospects in Salesforce"

Situation 3: "My job didn't produce measurable outcomes"

Solution: Measure the work itself

Example:

  • "Wrote documentation" →
  • "Produced 75-page technical documentation reducing new hire onboarding time by 2 weeks"

Situation 4: "Results were confidential"

Solution: Use percentages or ranges

Example:

  • "Increased revenue" →
  • "Grew revenue by 40%+ year-over-year" or "Contributed to $X-$Y million growth"

Situation 5: "I was entry-level with limited impact"

Solution: Quantify learning, throughput, accuracy

Example:

  • "Entered data" →
  • "Processed 200+ records daily with 99.5% accuracy rate, exceeding team average by 15%"

Output Format

When quantifying a resume:

# RESUME QUANTIFICATION

## Analysis Summary
**Bullets without numbers:** X
**Bullets with numbers:** Y
**Target:** 100% of bullets should have at least one metric

## Quantified Bullets

### Original Bullet #1:
"Managed customer accounts"

### Questions to Find Metrics:
- How many accounts? → [User answer: ~40]
- What was the revenue? → [User answer: ~$2M]
- What results did you achieve? → [User answer: retained most]

### Quantified Version:
"Managed portfolio of 40 enterprise accounts representing $2M ARR, achieving 95% retention rate"

### Metrics Added:
- Account count: 40
- Revenue: $2M ARR
- Retention: 95%

---

### Original Bullet #2:
[Continue for each bullet]

## Estimation Notes
- [Metric]: Estimated based on [reasoning]
- [Metric]: Conservative estimate using [method]

## Remaining Questions
- [Questions to ask user for missing information]

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.

1---
2name: resume-quantifier
3description: Find opportunities to add metrics and estimate numbers when exact data unavailable
4---
5 
6# Resume Quantifier
7 
8## When to Use This Skill
9 
10Use this skill when the user:
11- Needs to add metrics and numbers to their resume
12- Has bullets without quantifiable results
13- Doesn't know what numbers to include
14- Says they "don't have metrics" or "can't measure impact"
15- Mentions: "add metrics", "quantify", "add numbers", "measure impact", "no data"
16 
17## Core Capabilities
18 
19- Find hidden metrics in any experience
20- Estimate numbers when exact data unavailable
21- Create before/after comparisons
22- Identify measurable impact points
23- Transform vague statements into quantified achievements
24- Guide users to discover their metrics
25 
26## Why Quantification Matters
27 
28**The Problem:**
29- "Managed projects" vs "Managed 12 projects worth $2M"
30- "Improved processes" vs "Reduced cycle time by 40%"
31- "Helped customers" vs "Resolved 50+ tickets daily with 98% satisfaction"
32 
33**Studies Show:**
34- Resumes with numbers get 30% more attention
35- Quantified bullets are 40% more memorable
36- Numbers provide credibility and scale
37 
38## The Quantification Framework
39 
40### Categories of Metrics
41 
42**1. Money**
43- Revenue generated
44- Costs reduced/saved
45- Budget managed
46- Deal sizes closed
47- Profit margins improved
48 
49**2. Time**
50- Hours saved
51- Cycle time reduced
52- Project duration
53- Response times
54- Time to market
55 
56**3. Percentages**
57- Growth rates
58- Improvement percentages
59- Efficiency gains
60- Error reduction
61- Conversion rates
62 
63**4. Volume/Scale**
64- Number of customers/users
65- Projects managed
66- Team size
67- Transactions processed
68- Items produced
69 
70**5. Quality**
71- Satisfaction scores
72- Error rates
73- Accuracy rates
74- Compliance rates
75- SLA adherence
76 
77**6. Frequency**
78- Per day/week/month
79- Annual totals
80- Meeting cadences
81- Report cycles
82 
83## Finding Hidden Metrics
84 
85### The Discovery Questions
86 
87For any experience, ask:
88 
89**Scale Questions:**
90- How many people/projects/customers?
91- What was the budget/revenue involved?
92- How large was the team?
93- How many locations/regions?
94 
95**Impact Questions:**
96- What changed because of your work?
97- What would have happened without you?
98- What problems did you solve?
99- What got better/faster/cheaper?
100 
101**Comparison Questions:**
102- How was it before vs. after?
103- How did you compare to others/previous results?
104- What was the baseline you improved?
105 
106### Role-Specific Metric Discovery
107 
108**Sales:**
109- Quota attainment percentage
110- Revenue generated
111- Number of deals closed
112- Average deal size
113- Pipeline generated
114- New accounts acquired
115- Retention rate
116 
117**Marketing:**
118- Leads generated
119- Campaign ROI
120- Engagement rates
121- Follower growth
122- Website traffic increase
123- Conversion rates
124- Brand awareness metrics
125 
126**Customer Service:**
127- Tickets resolved per day
128- Customer satisfaction score
129- Average response time
130- First call resolution rate
131- NPS score contribution
132 
133**Operations:**
134- Efficiency improvements
135- Cost reductions
136- Process cycle times
137- Error rate reductions
138- Throughput increases
139 
140**Engineering:**
141- System uptime
142- Performance improvements
143- Bug resolution rate
144- Deployment frequency
145- Code coverage
146 
147**Project Management:**
148- Number of projects
149- Budget sizes
150- Team sizes
151- On-time delivery rate
152- Stakeholders managed
153 
154**HR/Admin:**
155- Hiring numbers
156- Time to fill
157- Employee satisfaction scores
158- Training completion rates
159- Onboarding efficiency
160 
161## Estimation Techniques
162 
163When you don't have exact numbers:
164 
165### Conservative Estimation
166 
167**Principle:** Estimate low to maintain credibility
168 
169**Example:**
170- You think you saved 100 hours/month → say "75+ hours"
171- You think growth was 50% → say "~40%"
172- You think you served 500 customers → say "400+"
173 
174### Range Estimation
175 
176**Format:** "X-Y" or "X to Y"
177 
178**Examples:**
179- "Managed team of 8-12"
180- "Generated $100K-$150K in revenue"
181- "Saved 20-30 hours weekly"
182 
183### Minimum Bound
184 
185**Format:** "X+" or "at least X"
186 
187**Examples:**
188- "Served 100+ customers daily"
189- "Managed at least 15 concurrent projects"
190- "Generated $500K+ in annual revenue"
191 
192### Percentage of Activity
193 
194**Format:** Calculate from known totals
195 
196**Example:**
197- Company had 1000 customers → You managed 20% → "Managed 200 customer accounts"
198- Team had 10 people → You supervised 4 → "Supervised 40% of team"
199 
200### Time-Based Calculation
201 
202**Format:** Work backwards from frequency
203 
204**Example:**
205- Met with 5 clients/week × 50 weeks = "Consulted with 250+ clients annually"
206- Processed 30 invoices/day × 250 days = "Processed 7,500+ invoices annually"
207 
208## Quantification Templates
209 
210### Before and After Template
211```
212"Improved [X] from [before number] to [after number], resulting in [Y]% improvement"
213 
214Example:
215"Improved page load time from 8 seconds to 2 seconds, resulting in 75% reduction and 20% increase in user engagement"
216```
217 
218### Scale Template
219```
220"[Verb] [number] [things], resulting in [impact]"
221 
222Example:
223"Managed 25 concurrent projects worth $3M, delivering 95% on-time with zero budget overruns"
224```
225 
226### Volume + Impact Template
227```
228"Processed [number] [items] per [time period], achieving [quality metric]"
229 
230Example:
231"Resolved 50+ customer tickets daily, maintaining 98% satisfaction rating and 4-hour average response time"
232```
233 
234### Comparison Template
235```
236"Ranked #[X] out of [Y] in [metric], [context]"
237 
238Example:
239"Ranked #2 out of 45 sales representatives nationally, generating $3.2M in annual revenue"
240```
241 
242## Common "I Have No Numbers" Situations
243 
244### Situation 1: "I was just one person on a team"
245 
246**Solution:** Focus on YOUR contribution
247 
248**Example:**
249- "Part of team that launched product" →
250- "Contributed 40% of front-end code for product launch reaching 100K users"
251 
252### Situation 2: "I don't have access to business metrics"
253 
254**Solution:** Quantify activities and inputs
255 
256**Example:**
257- "Supported sales team" →
258- "Created 50+ sales presentations and managed pipeline of 200+ prospects in Salesforce"
259 
260### Situation 3: "My job didn't produce measurable outcomes"
261 
262**Solution:** Measure the work itself
263 
264**Example:**
265- "Wrote documentation" →
266- "Produced 75-page technical documentation reducing new hire onboarding time by 2 weeks"
267 
268### Situation 4: "Results were confidential"
269 
270**Solution:** Use percentages or ranges
271 
272**Example:**
273- "Increased revenue" →
274- "Grew revenue by 40%+ year-over-year" or "Contributed to $X-$Y million growth"
275 
276### Situation 5: "I was entry-level with limited impact"
277 
278**Solution:** Quantify learning, throughput, accuracy
279 
280**Example:**
281- "Entered data" →
282- "Processed 200+ records daily with 99.5% accuracy rate, exceeding team average by 15%"
283 
284## Output Format
285 
286When quantifying a resume:
287 
288```markdown
289# RESUME QUANTIFICATION
290 
291## Analysis Summary
292**Bullets without numbers:** X
293**Bullets with numbers:** Y
294**Target:** 100% of bullets should have at least one metric
295 
296## Quantified Bullets
297 
298### Original Bullet #1:
299"Managed customer accounts"
300 
301### Questions to Find Metrics:
302- How many accounts? → [User answer: ~40]
303- What was the revenue? → [User answer: ~$2M]
304- What results did you achieve? → [User answer: retained most]
305 
306### Quantified Version:
307"Managed portfolio of 40 enterprise accounts representing $2M ARR, achieving 95% retention rate"
308 
309### Metrics Added:
310- Account count: 40
311- Revenue: $2M ARR
312- Retention: 95%
313 
314---
315 
316### Original Bullet #2:
317[Continue for each bullet]
318 
319## Estimation Notes
320- [Metric]: Estimated based on [reasoning]
321- [Metric]: Conservative estimate using [method]
322 
323## Remaining Questions
324- [Questions to ask user for missing information]
325```
326 
327## Quantification Quality Checklist
328 
329For each bullet:
330- ✅ Has at least ONE number
331- ✅ Number is relevant (not just any number)
332- ✅ Scale is clear (what does the number mean?)
333- ✅ Estimation is conservative and defensible
334- ✅ Number adds credibility, not confusion
335- ✅ You can explain the number in an interview
336 
337## Numbers to Avoid
338 
339- ❌ Numbers that make you look bad
340- ❌ Numbers you can't explain or defend
341- ❌ Numbers that reveal confidential information
342- ❌ Exaggerated or inflated numbers
343- ❌ Numbers without context (e.g., "increased by 300%" without baseline)
344- ❌ Too many numbers in one bullet (2-3 max)
345 
346## Key Principle
347 
348**Every bullet can be quantified.** If you think your work can't be measured, you haven't asked the right questions yet.
349 
350The goal isn't to have impressive numbers—it's to have SPECIFIC numbers that show the scope and impact of your work.
351 

Discussion

Alternatives

Also in Job hunting