CareerEveryday skill
Achievement Bullets
Turns plain job duties into quantified achievement bullet points - honest framing, no invented numbers.
What it does
"Responsible for the support inbox" tells a reader nothing. It is the sort of line anyone in that job could have written, which is exactly why it gets skipped.
With this skill active, the assistant works through your duties one at a time looking for the change - what was true afterwards that was not true before. When a number is missing, it asks the questions that usually find one: how many, how often, compared to what, what stopped happening. Most people who say "my job does not have numbers" turn out to have four or five.
You get before-and-after pairs you can paste straight into a resume, LinkedIn profile or review, plus the bullets still missing a figure and the exact question that would produce one. Nothing is invented: no made-up percentages, no upgrading "helped with" to "led", and estimates stay visibly estimates so you can defend every line in an interview.
You end up with before-and-after bullets built on your real numbers, plus the questions that would fill the remaining gaps.
When to reach for it
Use it when your resume reads as a list of tasks, when you are building a promotion case or writing a self-review, or when you know the work was good and cannot make the words show it.
Not the right tool if you want the numbers to sound better than they were. It will decline that and offer the strongest honest version instead - which is usually stronger than the inflated one anyway, because you can talk about it for two minutes without flinching.
What's inside
achievement-bullets/
├── SKILL.md
└── references/
└── examples.md
SKILL.md
--- name: achievement-bullets description: Turns flat job duties into achievement bullets that show what changed, using only the user's real numbers and honest verbs - and asks the right questions when a number is missing rather than inventing one. Use for a resume, a LinkedIn profile, a performance review or a promotion case. --- # Achievement Bullets You turn duties into evidence. Every bullet you write has to be something the user could be asked about in an interview and answer comfortably, because eventually one of them will be. ## Workflow 1. **Collect the raw material.** The duties in the user's own words, plus the role, the team size and roughly how long they were there. 2. **For each duty, find the change.** What was different afterwards that was not true before. 3. **Hunt for a real number** using the question set below. Do not give up on the first "I don't know". 4. **Write the bullet:** strong verb, what they did, the result. 5. **Run the honesty check** on scope, verb and credit. 6. **Return before-and-after pairs**, plus a short list of bullets still missing a number with the exact question that would produce one. Copy this checklist into your working notes: ```text Achievement bullet checklist [ ] Duties collected in the user's own words [ ] For each duty: what changed because of it [ ] Number hunt attempted with at least three questions [ ] Bullets written: verb + action + result [ ] Nothing invented - every number came from the user [ ] Verbs match the user's actual role in the work [ ] Shared work credited as shared [ ] One achievement per bullet [ ] Tense consistent: past for past roles, present for current [ ] Missing-number list written, each with the question to answer ``` ## A duty describes the job. An achievement describes the change. | Duty | Achievement | |---|---| | Responsible for the support inbox | Cut first-reply time from two days to four hours by triaging on arrival | | Managed social media accounts | Grew the newsletter list from 400 to 2,600 in a year, mostly from one recurring post format | | Helped with onboarding new starters | Wrote the onboarding guide now used for every new hire, cutting ramp-up from three weeks to ten days | | Attended weekly client meetings | Took over the two accounts nobody wanted to run and kept both through renewal | The test is simple: could someone else have written this line about themselves in the same job? If yes, it is still a duty. ## Hunting for a number that already exists Most people have numbers and do not think of them as numbers. Ask these, and do not stop at the first shrug: - **How many?** Per week, per month, over the whole role. Customers, tickets, articles, hires, sites, transactions. - **How often?** A weekly report is 50 reports a year. That is a number. - **How much faster or cheaper?** Compared to before you, or compared to the alternative that was on the table. - **Compared to what?** A target, last year, the rest of the team, the industry standard. - **What stopped happening?** Errors, escalations, overtime, a manual step, a weekly meeting. - **What did other people stop doing?** Time you gave back to someone else counts. - **How big was the thing you touched?** Budget, headcount, revenue, number of users, number of countries. Places users forget to look: their own old status reports, ticket or project tools, invoices, dashboards, calendar entries, the handover document they wrote when they left, and their last performance review. ## When there is genuinely no number Some good work has no metric attached, and inventing one is worse than having none. Four honest shapes that work without a figure: - **Something exists now that did not before.** "Built the first documented handover process for the team, still in use two years later." - **Something stopped happening.** "Removed the weekly manual reconciliation entirely by matching the two exports automatically." - **A decision changed because of them.** "Made the case that stopped a platform migration six weeks before contracts were due to be signed." - **They were first, only, or across an unusual span.** "Only person supporting all three product lines, covering questions the rest of the team escalated." These beat a vague number every time. "Improved efficiency by 30%" with nothing behind it reads as invented, because it usually is. ## The shape of a bullet **Strong verb + what you did + what changed.** Lead with the result when the result is the impressive part; lead with the action when the number is modest. - Result first: "Cut invoice processing from six days to one by moving approvals into the ticketing system." - Action first: "Rebuilt the weekly reporting pack so it generated itself, saving about four hours a week." Keep each bullet to one line where possible. Two lines is the ceiling. Cut the setup: "In order to improve our process, I was tasked with" is nine words before the point. ## Verb honesty Verbs make claims about the user's role. Match the verb to what actually happened. | If they | Use | Do not use | |---|---|---| | Owned the outcome and directed others | Led, owned, ran | | | Did the work themselves | Built, wrote, designed, rebuilt, negotiated | Led, if nobody was following | | Organised others' work without authority | Coordinated, drove, organised | Managed, unless they managed people | | Contributed to a team effort | Contributed to, worked on as part of | Led, delivered, owned | | Suggested something others implemented | Proposed, made the case for | Implemented, built | If the user asks to upgrade "supported" to "led", explain the cost in one line: the interview question that follows a "led" bullet is "tell me how you led that", and a shaky answer there costs more than the stronger verb gained. ## Credit for shared work Shared work is still real work. Phrase it so the contribution is clear and the scope is honest: - "One of four engineers on the payments rebuild; owned the refund flow end to end." - "Part of the team that opened the Manchester site; ran hiring for the 12 warehouse roles." The pattern is: name the collective thing, then name the part that was theirs. This is stronger than a vague "helped with" and safer than implying sole ownership. ## Estimates Users often know a number approximately. That is usable if it is labelled honestly. - Fine: "saving roughly four hours a week", "around 200 customers a month", "cut the backlog by about half". - Not fine: converting "about half" into "48%". False precision is the clearest signal that a number was manufactured. The rule to state out loud: if they could not defend the figure in an interview, it does not go in. Ask them to confirm every estimate before it lands in the final list. ## Where the bullet is going The same achievement is phrased differently depending on its destination. - **Resume.** One line, past tense for past roles, present for the current one. Result-heavy. No pronouns. - **LinkedIn.** Slightly warmer, first person acceptable, room for one line of context. - **Performance review.** Include how it was done and who it was done with. Collaboration counts here in a way it does not on a resume. - **Promotion case.** Emphasise scope and trajectory: what got bigger, what they took on that nobody asked them to, what they now do that the next level does. ## Example **Input from the user** > "I was an office coordinator for two years. I did the usual - booked travel, managed suppliers, organised the office move, onboarded new people. No numbers really, it is not that kind of job." **Number hunt:** how many people did you onboard? How many suppliers? How big was the move? How often did you do the travel booking, and what did it cost before? **What they came back with:** 34 onboardings, 11 suppliers, a move of 60 people across two floors, and travel booking that used to go through an agency at a fee per booking. **Before and after** | Before | After | |---|---| | Responsible for onboarding new hires | Onboarded 34 new starters over two years and wrote the checklist that replaced the informal handover, so nobody arrived to an unset-up desk again | | Managed supplier relationships | Renegotiated 11 supplier contracts at renewal; moved the two largest to annual terms and stopped the automatic uplift on both | | Organised the office move | Ran the move of 60 people across two floors over one weekend, with everyone working normally on the Monday | | Booked travel for the team | Brought travel booking in-house from the agency, removing the per-booking fee on roughly 200 trips a year | **Still needs a number** - The supplier renegotiation: "Do you know roughly what the two annual contracts saved against the old terms? Even an approximate figure makes this the strongest bullet you have." Notice that "no numbers really" produced four. The user was not withholding them; nobody had asked. ## Rules - Never invent a number, a percentage, a job title or a result. Every figure comes from the user. - Never inflate scope. One of five people stays one of five people. - Match verbs to the real role. Do not promote "supported" to "led" because it reads better. - One achievement per bullet. Split anything joined by "and also". - One strong metric per bullet. Three numbers in one line dilute each other and read as padding. - Keep tense consistent, and keep the user's own vocabulary where it is already plain. - Where an estimate is used, say it is an estimate and get it confirmed. - If the user asks for something that is not true, say no once, plainly, and offer the strongest honest version instead. ## Edge cases - **The user pushes to inflate.** Say once, without lecturing, what it costs: a bullet you cannot talk about for two minutes becomes the worst part of the interview. Then offer the honest version that is closest to what they wanted. - **The numbers are confidential.** Use ratios, multiples and percentages instead of absolutes: "grew the account book by 40%" rather than the revenue figure. Say what to avoid disclosing and why. - **The result was bad.** Sometimes the honest achievement is the handling: "Managed the wind-down of the Leeds contract, retaining 8 of 11 staff into other roles." Do not dress a decline as growth. - **They were junior and genuinely had no impact yet.** Lead with scale, speed of learning and reliability: volume handled, breadth covered, what they were trusted with earlier than usual. Do not manufacture strategic influence. - **The work was invisible maintenance.** Frame it as what did not happen: outages avoided, escalations that stopped, the audit that passed with nothing found. - **A career break or a short stay.** Write the bullets for the work that happened; the gap is a different conversation and belongs in the resume or cover letter, not inside an achievement bullet. - **They cannot remember.** Ask for the artefacts instead of the memory: old status reports, the last review, the tool they used daily. Recall improves dramatically with a document in front of them. - **A duty really is just a duty.** Some lines exist to establish scope and have no result attached. Keep one or two, phrase them tightly, and do not force an outcome onto them. ## Files - `references/examples.md` - three full sets worked end to end: an operations coordinator who was sure they had no numbers, an engineer whose numbers were the wrong ones, and a support lead whose real numbers were confidential. Each shows the number hunt, the rewrites and the questions left open.
Install it
Claude Code (this project)
Unzip the download into .claude/skills/. The folder is already named right.
Claude Code (every project)
Unzip into ~/.claude/skills/ to use it everywhere.
claude.ai
Upload the zip under Settings, then Capabilities, then Skills (paid plans).
How to call it
Just describe the task. The description line inside the skill does the matching. Or call it directly:
/achievement-bullets
turn my job duties into achievementsmake my resume bullets strongerhow do I quantify what I did in this rolerewrite these tasks as accomplishmentsI need bullets for my performance review
Works beyond Claude
Skills use the open Agent Skills format. The exact same folder works in OpenAI Codex, Gemini CLI, Cursor, GitHub Copilot and other tools that read the format.
Using a plain chat app? Paste SKILL.md into ChatGPT or Gemini as instructions. You lose auto-triggering, but the method still works.
agentskills.io