Skip to content
Content
Skill

/resume-quantifier

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

From plugin
resumeskills
1.5k22 skills
Install
$ npx -y skills add paramchoudhary/resumeskills --skill resume-quantifier --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/resume-quantifier

Context preview

The summary Claude sees to decide when to auto-load this skill.

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

SKILL.md

resume-quantifier.SKILL.md
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"
  • "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:*

Read more
Ships withresumeskills

A collection of AI agent skills focused on resume optimization, job applications, and career development.

Get the whole plugin