jirawatp/resume-career-toolkit / skills/bullet-point-rewriter
Bullet Point Rewriter
VerifiedRewrite flat resume bullets into achievement statements with measurable outcomes. Use this skill whenever someone asks to improve resume bullets, make bullets stronger, add impact, add metrics, fix passive language, transform job duties into achievements, or mentions weak/boring/generic resume content. Also trigger when reviewing a resume and spotting bullets that start with "responsible for" or lack any numbers.
Bullet Point Rewriter
Turn duty descriptions into achievement statements that prove value.
The Core Problem
Most bullets describe what someone was supposed to do (duties) rather than what they accomplished (achievements). Recruiters scan for evidence of impact, not job descriptions they already know.
Duty: "Responsible for managing social media accounts" Achievement: "Grew Instagram audience from 5K to 18K in 8 months through a daily content calendar and 12 influencer collaborations, generating 200+ inbound leads"
The Achievement Formula
Every strong bullet follows this pattern:
[Strong verb] + [what you did specifically] + [measured outcome or scale]
At minimum, every bullet needs: one action verb that is not "responsible for", "helped", or "assisted"; and at least one number that gives scale or result.
Rewriting Process
Step 1: Identify the weak pattern
Common weak patterns:
- Starts with "Responsible for..." (passive, describes the job not the person)
- Starts with "Helped..." or "Assisted..." (minimizes contribution)
- No numbers anywhere (vague, no proof of scale)
- Describes a process with no outcome ("Conducted meetings with clients")
- Uses filler words ("various", "multiple", "several" without specifying)
Step 2: Ask what actually happened
For any weak bullet, these questions uncover the achievement:
- How many? (people, projects, dollars, units, customers)
- How much did it change? (before vs. after, percentage improvement)
- What was the business result? (revenue, cost savings, time saved, satisfaction)
- How does it compare? (to quota, to predecessors, to industry average)
- What would have happened without you? (the counterfactual reveals your value)
Step 3: Reconstruct using the formula
Pick the strongest verb from the right category:
Growth: Grew, Increased, Expanded, Scaled, Doubled, Accelerated Efficiency: Reduced, Streamlined, Automated, Consolidated, Eliminated Creation: Built, Designed, Launched, Developed, Established, Pioneered Leadership: Led, Directed, Mentored, Coordinated, Mobilized Analysis: Identified, Diagnosed, Evaluated, Forecasted, Modeled Revenue: Generated, Captured, Secured, Closed, Converted
Step 4: Add the number
If you do not have exact data, use these approaches:
- Conservative estimate: round down ("saved roughly 20 hours per week" becomes "saved 15+ hours weekly")
- Ranges: "managed 8-12 concurrent projects"
- Relative: "outperformed team average by 30%"
- Input metrics when output metrics are unavailable: "analyzed 500+ data points" when you cannot quantify the business outcome
Examples by Function
Engineering: Before: "Worked on backend services" After: "Rebuilt three backend services in Go, cutting average API response time from 800ms to 120ms for 200K daily requests"
Sales: Before: "Met with clients and closed deals" After: "Closed 22 enterprise contracts worth $4.1M in FY23, finishing at 138% of annual quota and ranking 3rd out of 40 reps"
Marketing: Before: "Created marketing campaigns" After: "Launched 8 paid acquisition campaigns across Google and Meta, driving 3,200 qualified leads at $18 cost per lead, 40% below department benchmark"
Operations: Before: "Managed inventory" After: "Redesigned inventory tracking process using barcode scanning, reducing stock discrepancies from 12% to under 2% across 3 warehouse locations"
Customer Support: Before: "Handled customer complaints" After: "Resolved 45+ tickets daily with a 97% first-contact resolution rate and 4.8/5.0 average satisfaction score"
HR: Before: "Conducted hiring" After: "Filled 35 technical roles in 6 months with an average time-to-hire of 28 days, 15 days faster than department average"
Bullet Length and Count
- Keep each bullet to 1-2 lines (roughly 15-25 words)
- Use 3-5 bullets for recent roles, 2-3 for older roles
- Lead each role with the most impressive bullet
- Cut bullets that do not support your target role
Output Format
For each bullet rewrite, provide:
ORIGINAL: "[their bullet]"
ISSUES: [what is wrong -- passive voice, no metrics, vague, etc.]
REWRITTEN: "[improved bullet]"
METRICS USED: [what numbers were added and how they were derived]
Rules
- Never fabricate achievements or inflate numbers
- If the user cannot provide any numbers, quantify the inputs (volume of work, team size, number of stakeholders) rather than leaving the bullet numberless
- Every rewritten bullet must be something the user can confidently discuss in an interview
- Prefer specific over impressive: "saved 12 hours weekly" is better than a vague "significantly improved efficiency"
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |