Job-Seeker Comeback Kit — 5 Claude Skills for Getting Back to Work

---
name: ats-resume-rewriter
description: Use to rewrite, tailor, and ATS-optimize a resume for applicant tracking systems and human recruiters. Triggers: "rewrite my resume," "tailor my resume to this job," "make my resume ATS-friendly," "optimize resume keywords," "fix my resume summary," "improve my resume bullet points," "match my resume to a job description," "resume for [role/title]," "resume for a career change." Takes a current resume plus a pasted job description and returns an ATS-safe rewrite: a role-targeted summary, quantified-where-true bullets (asks for real numbers, never fabricates them), clean reverse-chronological section order with standard headings, and a qualitative keyword-coverage table (Covered / Partial / Missing — never a fake "ATS match %," search volume, or callback rate). Flags every gap with [brackets] to confirm before sending. Works with no job description too (skips keyword alignment). Not career, legal, or immigration advice; never invents employers, dates, titles, certifications, metrics, or scores.
---

# ATS Resume Rewriter — human-readable + machine-parseable

## Overview
Rewrites an existing resume so it reads like a real person wrote it AND parses cleanly through Applicant Tracking Systems. It returns a strong role-targeted summary, quantified-where-true bullets (using only numbers the user supplies), an ATS-safe section order, and keyword alignment to a pasted job description — then flags every gap to confirm before the user sends anything. It never fabricates metrics, employers, dates, tools, or an "ATS match score."

## What it is NOT
- Not a guarantee of interviews and not a "% match" — ATS configurations vary by employer and no outside tool can read their parser.
- Not career, legal, or immigration advice.
- It will not invent numbers, certifications, job titles, or skills. Anything missing becomes a [bracketed placeholder] or a flagged question — never a guess.

## Input contract (ask only what changes the output)
Required:
1. Current resume (paste full text or the relevant sections).
2. Target job description (paste). If none is supplied, say so — the rewrite still runs, just without keyword alignment.

Optional, ask if absent (each genuinely changes the output):
3. Target job title / seniority.
4. Real numbers for vague bullets ("how many? how much? over what time period?").
5. Constraints: 1 page vs 2; region norms (US: no photo/no DOB); industry.
6. Anything to handle carefully: employment gap, career change, contract roles.

If only a resume is pasted: run the rewrite, mark keyword alignment "no JD supplied," and ask the 2–3 highest-leverage questions only.

## Output contract (return in this order)
A. **Rewritten resume** — plain text, ATS-safe: single column, no tables/text boxes/images/headers-footers/special glyphs. Section order: Contact → Summary → Skills → Experience → Education → (Certifications / Projects). Reverse-chronological. Standard headings ("Work Experience," never "Where I've Been").
B. **Summary** — 2–3 lines, targeted to the role, third person, no clichés ("results-driven team player" is banned).
C. **Bullets** — strong past-tense verb + what you did + scope/impact; quantified ONLY where the user gave a real number, otherwise a [bracket] prompt.
D. **Keyword alignment** — each must-have term from the JD marked **Covered / Partial / Missing** (qualitative bands, never a percentage). Missing terms are listed so the user can add them truthfully.
E. **Gaps to confirm** — every [bracket], every assumption, every place a number or skill is implied but unproven.

## Internal logic