# Resume Tailor

> Tailor a resume to a specific job posting — rewrite bullet points to mirror the posting's language and priorities, reorder sections by relevance, and flag keyword gaps that would trip an ATS (applicant tracking system) filter. Use whenever the user shares a resume plus a job posting/description and asks to "tailor my resume", "optimize this for the job", "will this pass ATS", "rewrite my bullets for this role", or asks for feedback on a resume against a specific opportunity. Also trigger for general resume review even without a specific posting, defaulting to strong-generalist best practices.

- Skill: `zeiynz/resume-tailor` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add zeiynz/resume-tailor`
- Raw SKILL.md: https://api.skillmd.com/api/skills/zeiynz/resume-tailor/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: zeiynz (https://skillmd.com/u/zeiynz)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/zeiynz/resume-tailor

---


# Resume Tailor

Rewrites resume content to match a specific job posting without fabricating experience. The line this skill must never cross: **reframe truthfully-held experience in the posting's language — never invent skills, titles, metrics, or responsibilities the person didn't have.**

## Core principle: mirror, don't fabricate

Job postings and resumes often describe the same underlying work in different vocabulary (the posting says "stakeholder management," the resume says "worked with clients"). This skill's job is to find those true equivalences and rewrite toward the posting's language — not to add capabilities that weren't there. If a required qualification is genuinely absent, say so plainly rather than papering over the gap with vague phrasing.

## Workflow

### Step 1: Parse the posting for signal
Extract three things from the job description:
1. **Hard requirements** (explicitly "required," years of experience, specific tools/certifications)
2. **Repeated language/keywords** — terms that appear multiple times or in the first few bullets are usually weighted more heavily by both ATS parsing and the human reviewer's mental model of the role
3. **Implicit priorities** — what's listed first in "responsibilities" is usually what the role actually spends the most time on, regardless of title

### Step 2: Map resume content to posting priorities
For each posting requirement, find the resume's closest true match. Where a match exists but uses different vocabulary, rewrite the bullet using the posting's terms. Where no match exists, don't force one — flag it as a gap (see Step 4).

### Step 3: Rewrite bullets using the results-first pattern
Convert task-description bullets into **action + method + measurable result**:
- Weak: "Responsible for managing social media accounts"
- Strong: "Grew Instagram following 40% in 6 months by shifting to a weekly content calendar and creator partnerships"

If the person doesn't have a number for something, don't invent one — use a concrete scope descriptor instead ("managed a portfolio of 12 enterprise accounts" beats a fabricated percentage).

### Step 4: ATS keyword check
List the posting's key terms (tools, certifications, exact job-title language) alongside whether the resume currently contains a matching term. For genuine gaps, tell the user directly — this is where the honesty constraint matters most; a resume that pretends to have a required certification is a liability, not a fix.

### Step 5: Section ordering
Recommend reordering (not rewriting) sections so the most relevant experience for *this* posting appears first — a generalist resume often buries the most relevant role third or fourth.

## What this skill will not do
- Invent job titles, employers, dates, degrees, or certifications
- Inflate metrics beyond what the user has stated or can reasonably estimate from context they've given
- Claim proficiency in tools/skills not mentioned by the user anywhere in the conversation

## Output format
Present as a **before/after per bullet** (not a full rewritten resume dumped without context) so the user can see exactly what changed and why, then offer the full tailored version as a follow-up if they want it as a file (use the docx skill for a downloadable version).