resume-tailor
Skill12 starsChanged 11 days agoMITView on GitHub
This skill should be used when the user wants to tailor or customize their resume for a specific job or company. Triggers on phrases like "tailor resume for [company]", "customize resume for [job]", "generate resume for [company]", "adapt resume to this job posting", "create resume for [company] role".
32 other projects use a version of this.
Adopted by
Most recently taken up by
- studiocon/resume-templatetheir own version, first seen Nov 15, 2026
- wangssc/resume-tailor-skilltheir own version, first seen Nov 15, 2026
- chezou/skillstheir own version, first seen Nov 15, 2026
- skills-agents-co/skills-and-agents-librarytheir own version, first seen Nov 11, 2026
- gkmr/career-agent-kittheir own version, first seen Nov 8, 2026
- sunil-kumarr/JobIttheir own version, first seen Nov 8, 2026
Used with
Projects with it also use application-tracker, job-search and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
xiding-codeSkillapplication-tracker
Automatically log and track all job applications submitted. Use this skill after every application submission to record the details in a tracking spreadsheet and save relevant documents. Also trigger when the user asks "application status", "what have I applied to", "tracking", or wants to review their application history. Maintains a single source of truth for all job search activity.
Also in 3 projects that use this
rhowardstoneSkilljob-search
Search for jobs across multiple boards and company career pages. Use when looking for new positions to apply to.
Also in 3 projects that use this
AnthropicSkillinterview-prep
Create structured interview plans with competency-based questions and scorecards. Trigger with "interview plan for", "interview questions for", "how should we interview", "scorecard for", or when the user is preparing to interview candidates.
Also in 3 projects that use this
Other versions32 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 32
- claude-office-skills/skills★ 433same name
- olegvg/resume-tailor-plugin★ 44same name
- vignzpie/resume-agent-skills★ 17same name
- FlavioZanoni/mercury★ 8same name
- opencue/cuecards★ 8same name
- tstapler/dotfiles★ 8same name
- KinomotoMio/resumaker★ 5same name
- chezou/skills★ 4same name
- wexxwuther/job-hunter★ 4same name
- ZoolCoder/scoutjobs★ 4same name
22 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- cover-letterSkill
- fit-checkSkill
- mark-rejectedSkill
- new-jobSkill
- open-hot-jobsSkill
- reject-jobSkill
- remove-hot-jobSkill
- searchSkill
- send-outreachSkill
- test-runSkill
- update-hrSkill
- update-statusSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. 0 are common, 7 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 27 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
No Gemini call, so it uses none of the 20/day free quota.
- Distinctive: line 16
Run the tracker check (step 0 below) for every URL.
- Very specific: line 20
Read the CV(s) once (cv, and the AI CV with BASE_CV_DOCX=...
- Distinctive: line 28
All edits are checked before any PDF is made.
- Very specific: line 33
Check the tracker first (always, before any other step): Run python .claude/skills/search/scripts/search_tracker.py "<url>", then again …
- Very specific: line 40
Get the job description: Run python cv_tailor.py jd "<url>".
- Very specific: line 44
Read the CV: Run python cv_tailor.py cv (prints each paragraph of the base CV DOCX).
- Very specific: line 48
Ask with multi-select: Use AskUserQuestion with multiSelect: true: up to 4 questions of up to 4 missing skills each, mandatory JD skills …
- Distinctive: line 51
If a confirmed skill needs context to be described honestly (where/how), ask a short follow-up.
- Distinctive: line 69
Only facts on the CV or confirmed by the user in step 4.
- Distinctive: line 70
Keep content intact: never delete Projects, the NDS acquisition note, education details or the word "fintech" in the SMARTS bullet.
- Very specific: line 76
Don't put it in add_skills or a replace yourself.
- Distinctive: line 79
Never write "learning / deepening / upskilling in X" for a gap.
“Common” is measured: kept by at least 6 in 10 of the 27 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Resume Tailor (evidence-only, with skill confirmation)
Tailors the current CV DOCX for one job using cv_tailor.py. Claude does the comparison and asks
the user which missing skills they really have; the script applies the edits and exports a PDF (the temporary DOCX is deleted).
No Gemini call, so it uses none of the 20/day free quota.
Several postings at once (user gives 2+ URLs): use the batch flow below instead of repeating the steps per job.
Batch flow (several postings)
- Run the tracker check (step 0 below) for every URL; list all hits together and ask once before going on.
python cv_tailor.py jds <scratchpad>/jds <url1> <url2> ...fetches all JDs in parallel intojd_1.txt,jd_2.txt, ... (input order). For any line marked FAILED, open the page in the browser or ask the user to paste it.- Read the CV(s) once (
cv, and the AI CV withBASE_CV_DOCX=...if any posting is AI-focused). - Compare each JD (step 3 below) and draft each job's tailored Summary (step 5 below). Ask ONE AskUserQuestion round for all jobs: merge the missing skills across postings and ask each skill once (a confirmed skill counts for every job that needs it).
- Write
<scratchpad>/batch.json:[{"company": "Acme Backend", "base": "main", "edits": {"replace": [...], "add_skills": [...]}}, ...]baseismain(BASE_CV_DOCX) orai(BASE_CV_DOCX_AI). Use a distinctcompanyper posting (e.g. company + role) so the PDFs don't overwrite each other. python cv_tailor.py apply-batch <scratchpad>/batch.json(optional--workers N, default 3). All edits are checked before any PDF is made; PDFs export in parallel, one Word instance per worker.- Report per job as in step 8 (one table per job is fine), including the tailored summary.
Steps
- Check the tracker first (always, before any other step). Run
python .claude/skills/search/scripts/search_tracker.py "<url>", then again with the company name once you know it (from the JD title or page). Compare the company's rows with this posting's role title. If the same or a near-identical role is already tracked (applied, in progress or rejected, including reposts under another URL), stop and tell the user first: show the matching rows with status and comments, and say e.g. "already rejected in row 410, another application still open in row 454". Continue only if the user says so. Other roles at the same company are just mentioned in one line, no stop. - Get the job description. Run
python cv_tailor.py jd "<url>". Any job link works: LinkedIn, Welcome to the Jungle, Ashby and Greenhouse use the site's own data for a clean description; other sites (company career pages, Workday, etc.) fall back to reading the page. If it fails (login walls, closed jobs), ask the user to paste the description. - Read the CV. Run
python cv_tailor.py cv(prints each paragraph of the base CV DOCX). - Compare. List the JD's skills/requirements, in English even if the JD is French. Split them into:
- already on the CV (nothing to do, or surface better wording if the evidence is there)
- missing from the CV
- Ask with multi-select. Use AskUserQuestion with
multiSelect: true: up to 4 questions of up to 4 missing skills each, mandatory JD skills first. Question text like "Which of these have you used in real work?". The user can type extra detail in "Other" (e.g. the tool they used). If a confirmed skill needs context to be described honestly (where/how), ask a short follow-up. - Tailor the Summary (AI CV only). The main CV has NO Summary since 2026-11-05 (removed to keep it to 1 page;
the real-time/post-trade line moved into the NASDAQ SMARTS bullet), so skip this step for
main;applyskips the check too. The AI CV has aSummaryparagraph right after the contact line (one plain run). Rewrite it for this JD as areplacewhoseoldis the whole summary text from step 2: 2-3 lines, lead with the JD's top requirement that the CV can prove (e.g. Java/Spring backend, architecture and mentoring for lead/staff roles, LLM work for AI roles), mirror the JD's role title when it fits, keep "11+ yrs", and use only facts already on the CV or confirmed in step 4. Never name a skill the user didn't confirm, and don't claim the JD's stack (e.g. "Ruby") to match it.applyprints a WARNING if no edit touches the summary. - Draft the other edits (rules below) and write them to a JSON file in the scratchpad:
{"replace": [{"old": "...", "new": "..."}], "add_skills": ["..."]}. Eacholdmust sit inside ONE run of the DOCX. Bold highlights are separate runs, so keep each edit within a plain or a bold segment of the paragraph text from step 2. - Apply. Run
python cv_tailor.py apply "<Company>" <edits.json>. - Report the "Words changed" output from
apply(shown as removed -> added), the confirmed skills added, the page count, the JD skills still missing, and the output paths.
Edit rules
- Only facts on the CV or confirmed by the user in step 4. Never invent tools, numbers or domains.
- Keep content intact: never delete Projects, the NDS acquisition note, education details or the word "fintech" in the SMARTS bullet. No "| Fintech" in the title line.
- Confirmed skills go into the
Frameworks & Tools:line viaadd_skills, not into a specific job's bullet, unless the user said where they used it. - "Agent guardrails" is added to the AI skills line of EVERY tailored CV by
apply(CV_ALWAYS_AI_SKILLSinconfig.py;AI & Upskilling:on the main CV,AI & LLM:on the AI CV). Don't put it inadd_skillsor areplaceyourself. Mention it in the step 8 report. - AI CV only:
applyalso runsCV_AI_DEFAULT_REPLACEfromconfig.py(adds the weekly HR agent to the job-search project bullet). Don't repeat it in your edits; mention it in the report. - Never write "learning / deepening / upskilling in X" for a gap.
- English only. Do not switch to the JD's language.
- Going over 1 page is acceptable. Prefer edits that don't add lines, and say when the CV grows.
Output
resume_adjusted\resume_<company>.pdf only (folder from RESUME_OUTPUT_DIR in config.py).
An existing file with the same name is overwritten.
Base CV: BASE_CV_DOCX in config.py
(override with BASE_CV_DOCX in config.py). PDF export needs Microsoft Word.
AI-focused roles ("use AI resume"): prefix both cv and apply with the env var
BASE_CV_DOCX="<path>", where <path> is BASE_CV_DOCX_AI in config.py.
It has an AI & LLM: skills line; put confirmed AI skills there with a replace, not add_skills.
Legacy
resume_tailor.py (Gemini, batch from tracker) targets the OLD CV layout (fixed paragraph
numbers) and a PDF base path, so it does not work with the current CV. Use the steps above.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

