Skills for Real Engineers. Straight from my .agents directory.
resume-tailor
Agent skill fromreactive-resume/reactive-resume
Tailors one resume to one specific job posting. Builds a must-have/nice-to-have requirement table, an evidence map, gap questions instead of invention, a tailored copy (headline, summary, bullet order, skills), honest ATS guidance, and an optional cover letter for that posting. Use when the user says "tailor my resume to this job", "customize my CV for this posting", "match my resume to this job description", "what keywords am I missing", "make my resume ATS-friendly for this role", "will this get past the ATS", "the job asks for X and I don't have it", or pastes a job ad with a resume. Works from pasted text; uses Reactive Resume MCP tools when connected. Not for bullets with no target job (resume-bullet-writer), what belongs on a resume or a general audit (resume-content-guide), tracking or follow-ups (job-application-manager), or interview prep and practice (interview-prep, mock-interview).
How to install resume-tailor
npx skills add reactive-resume/reactive-resume# or add only this skill to Claude Code: copy the folder
plugins/reactive-resume/skills/resume-tailor/
# into
~/.claude/skills/resume-tailor/ (all projects)
.claude/skills/resume-tailor/ (one project)
1# Resume Tailor23Tailor one resume to one job description (JD). The core artifact is a **requirement → evidence table**. It is close to what current screening tools (Workday HiredScore, Greenhouse Talent Matching, Ashby) build when they grade a candidate, and what a recruiter checks by eye. Tailoring changes **emphasis, order and wording**. It never changes facts.45## Ground rules671. **Facts are locked.** Employers, official job titles, dates, degrees, credentials, metrics and results come from the resume or from the user's answers in this conversation, nothing else. Screening tools now cite resume evidence back to a human reviewer, and background checks verify titles and dates, so an invented line is traceable.82. **A gap is a question, not a fill-in.** Ask about it; add only what the user confirms, in their words. Verbs follow the evidence too: if the user "chose" or "reviewed" something, the bullet doesn't say "ran" or "led" it.93. **Missing numbers:** ask. Accept honest ranges or approximations and keep them marked ("~30%", "20–30 tickets a week"). With no number, use scope, frequency, who benefited, or before/after. A placeholder such as `[x]%` is fine in a draft; never deliver a final copy that still has one.104. **No tricks.** No keyword stuffing, no keyword lists without context, no hidden, white, tiny or off-page text, no instructions aimed at AI screeners. Parsing strips colour and size, so hidden text shows up in the recruiter's view, and recruiters reject for it.11…
Excerpt shown under the repository's MIT license.
More skills in reactive-resume
Similar skill repositories
An agentic skills framework & software development methodology that works.
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
Public repository for Agent Skills
Makes your AI agent think like the laziest senior dev in the room. The best code is the code you never wrote.
An AI skill that provides design intelligence for building professional UI/UX across multiple platforms.
