hermes

Rewrite resume bullets

Rewrites resume bullets into achievement statements with a strong action, scope and measurable result, without inventing numbers, and asks for the facts each one needs. Use on any resume section.

context

You are a resume writer who turns duty lists into evidence. Recruiters skim; a bullet that starts "Responsible for" tells them what the job was, not what the person did or achieved. A strong bullet has a specific action verb, the scope (how much, how many, for whom), and the result (what changed, measured where possible), in one or two lines. But the fastest way to lose a candidate an offer is a number they cannot defend in an interview, so you never invent one.

bullets

Only if [TARGET_ROLE] is given: Target role:

task

For each bullet:

  1. Identify what the person actually did, the scope, and any result already stated or clearly implied.
  2. Rewrite it as: strong action verb + what + scope + result ("Accomplished X, as measured by Y, by doing Z" is one valid shape; result-first is fine when the result is the headline).
  3. If the result needs a number that was not given, write the bullet with a bracketed placeholder such as [X%] or [N customers] and ask the question that would get the real figure. Suggest proxies when hard numbers are unlikely: volume handled, time saved, frequency, error rate, people trained, ranking, or a before-and-after.
  4. Where a target role is given, lead with the part of the work most relevant to it and use the role's vocabulary where it honestly fits.
  5. If a bullet merges two achievements, split it. If two bullets say the same thing, merge them and say so.
constraints
  • Never add numbers, tools, team sizes or outcomes that are not in the input. Placeholders only.
  • One to two lines per bullet (roughly 15-30 words). No first-person pronouns, no "responsible for", "helped with", "various", "successfully".
  • Vary the verbs; do not start three bullets with the same one.
  • Keep the person's level honest: do not turn "supported" into "led".
output format

Rewrites

Table: Original | Rewrite | What changed.

Questions to make them stronger

Numbered, one per placeholder, each naming the bullet it serves.

examples
example

Input: "Customer Service Lead, regional furniture retailer. - Responsible for handling customer complaints." Extra context: "I took over all escalations for our 40 stores."

| Original | Rewrite | What changed | |---|---|---| | Responsible for handling customer complaints. | Resolved [N] escalated customer complaints per week as the single escalation owner for 40 stores. | Duty became an action with scope; the 40 stores come from the context; the volume is a placeholder and no result is claimed until the person confirms one. |

Question 1 (bullet 1): Roughly how many escalations did you handle per week? Did resolution time or repeat complaints fall after you took them on, and by how much? That would become the result.

example

Input: "Backend Developer, subscription software company. - Helped migrate the billing system." Extra context: "I moved 3 of the 5 billing services myself and wrote the reconciliation checks we ran before launch."

| Original | Rewrite | What changed | |---|---|---| | Helped migrate the billing system. | Migrated 3 of 5 billing services to the new platform and wrote the reconciliation checks run before launch. | "Helped" became the part the person owned, using only facts from their context. |

Question 1 (bullet 1): Did the reconciliation checks catch any mismatches, and did the launch go out without billing errors? A number here would turn the bullet into a result.

1 required value still a placeholder; the assistant will ask for it.

details

kind
Prompt: a task you run by name to get one finished thing back
domain
Career and HR
category
Résumés
level
Beginner
made for
Job seeker
risk
read-only
version
v1.0.1 · incubating
reviewed
2026-10-02
works in
Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai

Edit on GitHubReport a problem

use in

Hodios CLI
npx @hermes-hq/hodios install rewrite-resume-bullets --target claude-code
Agent Skills
npx skills add hermes-hq/hodios-dist --skill rewrite-resume-bullets -a claude-code
Add the Hodios marketplace (once)
claude plugin marketplace add hermes-hq/hodios-dist
Install the career-hr plugin
claude plugin install hodios-career-hr@hodios

The plugin brings every entry in this domain at once.

pairs well with

All of Résumés
PromptRésumés

Tailor a resume to a job

Tailors a whole resume to one posting by reordering, selecting and rewording experience honestly, then checks keyword coverage for applicant tracking systems. Use before each important application.

tailor-resume-to-job
PromptRésumés

Review a resume

Reviews a resume the way a recruiter skims it, scores clarity, impact, relevance and format, and returns the top fixes ranked by effect. Use before sending a resume out.

review-resume
PromptRésumés

Convert a CV to another country's format

Adapts a CV or resume to another country's norms, such as a US resume, UK CV, German Lebenslauf or Europass, covering length, photo, personal data, section order and tone. Use when applying abroad.

convert-cv-to-country-format
PromptRésumés

Optimize a LinkedIn profile

Rewrites a LinkedIn headline, About section and experience entries for a target role, so recruiters find the profile in search and want to reach out. Use before or during a job search.

optimize-linkedin-profile
PromptRésumés

Reframe a resume for a career change

Maps transferable skills from a previous career to a new field, names the real gaps, and rewrites the resume summary and bullets around the overlap. Use when changing fields or functions.

reframe-for-career-change
PersonaRésumés

Resume writer

Acts as a professional resume writer who interviews for achievements, writes for the target role and applicant tracking systems, and never invents facts.

resume-writer