AgentSkillsCN

Achievement Quantifier

通过添加具体指标、百分比、时间跨度以及可量化的成果，强化简历中的项目亮点。

SKILL.md
--- frontmatter
name: Achievement Quantifier
description: Strengthens CV bullet points by adding specific metrics, percentages, timescales, and quantifiable results.
allowed-tools:
  - read
  - write

Achievement Quantifier Skill

This skill transforms vague CV bullet points into specific, quantified achievement statements.

Purpose

Improve CV content by:

  • •Adding specific metrics to vague claims
  • •Extracting quantifiable impact from experiences
  • •Prompting for missing details
  • •Rewriting weak statements as strong achievements

The Problem

Weak CV bullets like:

  • •"Improved system performance"
  • •"Led team projects"
  • •"Managed stakeholder relationships"
  • •"Drove digital transformation"

These tell the reader nothing specific and could apply to anyone.

The Solution

Strong CV bullets include:

  • •What - specific action taken
  • •How - method, tools, approach used
  • •Result - quantified outcome with numbers

Quantification Process

Step 1: Identify the Weak Statement

Look for bullets that:

  • •Use vague words (various, several, significant, multiple)
  • •Lack numbers or percentages
  • •Don't specify the outcome
  • •Could apply to anyone

Step 2: Ask Probing Questions

For "improved performance":

  • •What system/process?
  • •What aspect improved (speed, accuracy, cost)?
  • •By how much (percentage, time, money)?
  • •Over what period?
  • •What was the business impact?

For "led team":

  • •How many people?
  • •What type of team (engineers, cross-functional)?
  • •What did you deliver?
  • •What was the outcome?

For "managed stakeholders":

  • •Which stakeholders (C-suite, clients, partners)?
  • •How many?
  • •What did you achieve with them?
  • •Any specific wins?

Step 3: Extract the Numbers

Prompt for specifics:

  • •Team sizes
  • •Budget amounts
  • •Time reductions (percentage or hours/days)
  • •Cost savings (£ or percentage)
  • •Revenue impact
  • •User numbers
  • •Transaction volumes
  • •Error rate changes
  • •Customer satisfaction scores
  • •Project timelines met/improved

Step 4: Rewrite with Impact

Transform:

code
Before: "Improved database performance"

After: "Optimised PostgreSQL queries reducing average response time from
4.2s to 180ms (96% improvement), enabling real-time reporting for
2,000 daily users"

Example Transformations

Example 1: Leadership

Weak: "Led development team on important project"

Questions:

  • •How many people?
  • •What project?
  • •What was delivered?
  • •What was the impact?

Strong: "Led team of 6 engineers to deliver customer onboarding platform in 4 months, reducing onboarding time from 2 weeks to 48 hours and increasing conversion rate by 23%"

Example 2: Cost Savings

Weak: "Reduced infrastructure costs"

Questions:

  • •Which infrastructure?
  • •By how much?
  • •How did you do it?
  • •What was the £ saving?

Strong: "Cut AWS infrastructure costs by 45% (£180k annually) by rightsizing EC2 instances, implementing spot instances for batch processing, and eliminating unused resources across 12 production environments"

Example 3: Process Improvement

Weak: "Improved deployment process"

Questions:

  • •From what to what?
  • •How much faster?
  • •What tools?
  • •What was enabled?

Strong: "Redesigned CI/CD pipeline using GitHub Actions and Terraform, reducing deployment time from 4 hours to 15 minutes and enabling daily releases (previously monthly)"

Output Format

For each weak bullet, provide:

Original Statement

[The weak version]

Probing Questions

  • •[Question 1]
  • •[Question 2]
  • •[Question 3]

Information Needed

  • •[Missing detail 1]
  • •[Missing detail 2]

Suggested Rewrite

[Strong version with quantification]

Alternative if Numbers Not Available

[Best possible version with available info]

When Exact Numbers Aren't Available

If they can't provide exact figures, use:

  • •Approximate ranges: "approximately £150k", "around 40%"
  • •Scale indicators: "6-figure savings", "doubled", "halved"
  • •Relative terms: "reduced by more than half", "tripled throughput"
  • •Time context: "within first 3 months", "ahead of 6-month deadline"

But always push for actual numbers first - they're almost always more impressive than people realise.

Common Weak Words to Flag

  • •Significant
  • •Various
  • •Multiple
  • •Several
  • •Many
  • •Improved
  • •Enhanced
  • •Supported
  • •Assisted
  • •Helped
  • •Contributed to
  • •Involved in

Replace with specific, quantified alternatives.

Critical Rules

  • •Don't invent numbers - only use what they provide
  • •Push for specifics but accept ranges if that's all available
  • •Ensure claims can be backed up in interviews
  • •Numbers don't have to be exact, but must be honest
  • •Round numbers are fine (40% not 39.7%)