resume-bullet-writer

Original：🇨🇳 Chinese

Translated

Rewrite, diagnose, or enhance resume experience and project bullets. Use this when users request optimizing project descriptions, quantifying achievements, applying the STAR/X-Y-Z framework, making resumes more impactful, or providing weak bullets. Only output evidence-based rewrites and pending confirmation questions; do not fabricate numbers, skills, or achievements.

2installs

Sourcechasen-liao/resume-skills

Added on2026-08-12

NPX Install

npx skill4agent add chasen-liao/resume-skills resume-bullet-writer

SKILL.md Content (Chinese)

View Translation Comparison →

Resume Bullet Rewriter

Rewrite responsibility descriptions into clear, specific, and target-position relevant statements; do not turn language polishing into fictional experiences.

Pre-Read

Before each rewrite, read the Resume Fact Contract and read the Content Writing Guidelines as needed. These two take precedence over the general suggestion of "every bullet must have numbers."

Collaboration Entry

This is a condition-triggered content assistant, not a fixed step in the main workflow. Only suggest using it when users actively request it, or when

resume-builder

/

jd-tailorer

detects that experiences are responsibility-focused, contributions are unclear, evidence is insufficient, or relevance to the position is weak.

Rewrite candidates must be confirmed by the user before being added back to the master version or JD-tailored version; when facts are missing, output follow-up questions instead of directly writing suggestions into the final HTML/PDF.

Workflow

Disassemble the background, personal actions, technologies/methods, deliverables, results, and evidence in the original sentence.
Mark issues: responsibility-focused, unclear subject, non-specific terminology, missing results, irrelevant to the position, or overly long.
Draft 1–2 rewrite candidates using only confirmed facts; prioritize the structure:
```
Strong Verb + Specific Action/Technology + Verified Result or Deliverable + Scope
```
.
If there are credible metrics, retain their sources and limitations; when there are no metrics, use real roles, scopes, launch/acceptance statuses, or deliverables instead of estimating numbers.
When a JD is available, only adopt terms from the candidate's confirmed facts that can correspond to it, and mark the source of keywords.
Turn missing facts into brief follow-up questions, which cannot be included in the final bullet.

Output Format

markdown

### Bullet 1
**Original Sentence**: …
**Issues**: …
**Suggested Rewrite**: …
**Basis**: Confirmed actions / deliverables / metrics
**Pending Confirmation**: …(omit if none)

Checks

Use clear verbs; avoid "responsible for/participated in/assisted with" without specifying specific contributions.
Do not attribute team results to individuals; do not add skills that appear in the JD but the candidate does not possess.
Numbers only appear when
```
metric_status
```
is
```
verified
```
or
```
estimated
```
explicitly accepted by the candidate.
Keep it concise; if information is insufficient, output issues instead of filling with clichés.