Find opportunities to add metrics and estimate numbers when exact data unavailable
35
30%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/resume-quantifier/SKILL.mdUse this skill when the user:
The Problem:
Studies Show:
1. Money
2. Time
3. Percentages
4. Volume/Scale
5. Quality
6. Frequency
For any experience, ask:
Scale Questions:
Impact Questions:
Comparison Questions:
Sales:
Marketing:
Customer Service:
Operations:
Engineering:
Project Management:
HR/Admin:
When you don't have exact numbers:
Principle: Estimate low to maintain credibility
Example:
Format: "X-Y" or "X to Y"
Examples:
Format: "X+" or "at least X"
Examples:
Format: Calculate from known totals
Example:
Format: Work backwards from frequency
Example:
"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""[Verb] [number] [things], resulting in [impact]"
Example:
"Managed 25 concurrent projects worth $3M, delivering 95% on-time with zero budget overruns""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""Ranked #[X] out of [Y] in [metric], [context]"
Example:
"Ranked #2 out of 45 sales representatives nationally, generating $3.2M in annual revenue"Solution: Focus on YOUR contribution
Example:
Solution: Quantify activities and inputs
Example:
Solution: Measure the work itself
Example:
Solution: Use percentages or ranges
Example:
Solution: Quantify learning, throughput, accuracy
Example:
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]For each bullet:
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.
24c6edc
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.