Skill detail

resume

Directly writes ATS-friendly, achievement-led resumes and CVs.

MatchDirectReviewed for resume
Sourcemohitagw15856/pm-claude-skillsExternal source
Reported installs8Popularity signal only

Inspect before use

Automated review checks relevance, not safety or endorsement. Read the source instructions before using this skill.

Saved source preview

SKILL.md

The saved excerpt is a snapshot from review. The external source remains the complete and most current version.

---
name: resume
description: "Write a sharp, achievement-led resume/CV that passes ATS and earns the interview. Use when asked to write or rewrite a resume or CV, turn experience into a resume, or tailor a resume to a job. Produces a clean, single-column, ATS-friendly resume — summary, experience as quantified accomplishment bullets, skills, and education — ready to export as a designed PDF."
---

# Resume Skill

A resume gets ~7 seconds and an ATS scan before a human reads it. So it has to be *scannable*,
*achievement-led*, and *keyword-aligned* — not a job-description recap. This skill turns your experience
into quantified accomplishment bullets, structured single-column (ATS-safe), and tailored to the target
role. Export it with the **Paper** or **Modern** PDF theme for a typeset result.

## Working from a brief

You will often get rough notes, a partial history, or just a target role. **Always deliver a complete,
ready-to-use resume anyway** — do not stop to ask questions and do not leave bracketed placeholders like
`[Company]` or `[add metric]`. Where a detail is missing, infer a specific, realistic one from the rest of
the brief and the target role, and mark anything you inferred *(assumed — confirm)* so the user knows to
verify it. A concrete, labelled assumption always beats a blank or a clarifying question.

Quantify every achievement. **Lead with the user's real numbers** — when they gave a figure, use it exactly.
Only when a metric is genuinely absent, turn the duty into an outcome-focused achievement (the *result*, e.g.
"shipped the mobile app v1, growing it to its first cohort of users"); add a number only if it's a
**defensible, conservative estimate**, marked *(assumed — confirm)*. Never silently fabricate or inflate
numbers on a real person's resume — an unmarked invented metric is the one thing worse than a missing one.

Output **only the finished resume** (and its short tailoring note) — no preamble, no "here's your resume", no
meta-commentary about what you did.

## Inputs (infer any not provided — label assumptions)

- **Target role / job description** — so the resume is tailored and keyword-aligned (generic resumes lose).
- **Your experience** — roles, dates, and what you did/achieved (rough notes fine; the skill quantifies them).
- **Skills, tools, education, certifications.**
- **Seniority & format preference** — reverse-chronological (default) vs. functional; one page (most) vs. two.

## Output Format

A single-column, ATS-friendly resume in this order:

### [Full Name]
[Target title] · [city / remote] · [email] · [phone] · [LinkedIn/portfolio]

**Summary** — 2–3 lines: who you are, your strongest proof, and what you're targeting. No "results-driven professional" filler.

**Experience** — reverse-chronological. Per role:
**[Title]**, [Company] · [dates]
- [Accomplishment bullet: **action verb → what you did → quantified impact**]. e.g. "Cut onboarding drop-off 18%→9%, unlocking ~$140k ARR."
- 3–5 bullets per recent role, fewer for older ones. Achievements, not duties.

**Skills** — grouped, keyword-rich, mirroring the job's language (ATS matches on these).

**Education** — degree, institution, year; certifications.

**Tailoring note** (separate, for the user): which of the job's keywords you wove in, and any gap to address in the cover letter.

## Quality Checks

- [ ] Every experience bullet is an **achievement with a metric**, not a duty ("responsible for…")
- [ ] Bullets start with strong action verbs; no first-person pronouns
- [ ] Single-column, standard headings, no tables/text-boxes/graphics that break ATS parsing
- [ ] Keywords from the target job description appear naturally (skills + bullets)
- [ ] Length fits seniority (1 page < ~10 yrs; 2 max); newest/most-relevant first
- [ ] Contact line is complete and the summary names the target role

## Anti-Patterns

- [ ] Do not list job duties — "managed a team" is a responsibility; "grew the team 4→11 and cut attrition 30%" is an achievement
- [ ]
Read the full source on GitHub (opens external page)
Context

Related work