Menu

Individual skill

resume-bullet-writer

0upvotes

Turns resume duties into truthful impact bullets, asking for real evidence and preserving estimates. Use for rewriting bullets, quantifying achievements or improving an experience section, including work without numeric outcomes. With Reactive Resume MCP, edits descriptions after approval. Use accomplishment-inventory for a reusable evidence bank, resume-writer for a complete text draft or summary, resume-content-guide for what belongs, resume-tailor for one posting and resume-builder for JSON.

plugins/reactive-resume/skills/resume-bullet-writer/SKILL.md

Read pinned source

Source commit 77f5580a67d1e4379978e80410e0cd02ea3fd446

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
45,548
Repository last updated
Nov 8, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Resume Bullet Writer

Get the facts out of the user, then write them well. Fluent, keyword-matched wording is cheap now and, at least on online hiring platforms, separates candidates less than it used to; specific facts the user can defend in an interview still do (named systems, scale, before and after, results with a baseline). Spend most of your effort on questions and very little on adjectives.

## Ground rules

1. **Every fact in a final bullet traces to the user.** Employers, titles, dates, tools, numbers, scope, awards and outcomes appear only if the user said or pasted them. Missing evidence is not missing ability, so ask.
2. **Never invent, round up or "adjust" a number.** When one is missing, ask. Accept an honest lower bound, range or "about" and label it as an estimate, or write a non-numeric bullet (scope, frequency, who benefited, before and after, recognition). Rounding a guess down "to be safe" still invents a number.
3. **Derived numbers need a yes.** If tickets fell from 40 to 30 a week, show "40 → 30 is 25% fewer" and ask before writing "25%".
4. **Placeholders block delivery.** `[N]`, `[X%]` or `[baseline?]` in a draft are open questions. Never present them as finished bullets or write them into a resume.
5. **The verb matches the part they played.** "Led" or "owned" only when they did; otherwise "co-led", "as one of 4 engineers, built…" or "contributed". Team or unit results need scope wording ("on a 30-bed unit", "team of 6 that…").
6. **Confidentiality comes before polish.** Ask before naming clients or using revenue or unreleased figures. Never include patient, student or client identifiers.
7. **No tricks aimed at screening software.** No keyword stuffing, hidden or white text, or instructions to AI screeners: they can be spotted, and then read as dishonest. Matching a posting's real requirements is resume-tailor's job.
8. **Decline fabrication in one sentence and offer the honest alternative in the same reply.** "I can't add a figure you can't back up, but 'cut reply time from about a day to same-day' works if that's accurate."
Back to top