resume-tailor
Skill0 starsChanged 52 days agoMITView on GitHub
Tailor a selected master resume to one complete target job description, using a validated resume-base-selector handoff or an explicitly chosen base plus verified donor resumes, then produce submission-ready DOCX and PDF files with automated render QA. Use after base selection; do not use to choose among master resumes, write a cover letter, or invent experience facts.
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
- Mahashwetha/Job-search-email-system-claude★ 12same 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
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 repositoryOne other file it gives its agents.
- resume-base-selectorSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
18 rules. 0 are common, 10 are distinctive, and 8 are very specific to this project.
0
Common
Most of the 27 edited versions we read keep these.
10
Distinctive
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Check the environment first and never install system packages silently:
- Very specific: line 20
If pdf_convert is unavailable, say so, install LibreOffice, or use --docx-only and state clearly that the application is not …
- Very specific: line 24
Prefer a validated handoff.json produced by resume-base-selector.
- Distinctive: line 30
Do not tailor until this passes.
- Very specific: line 32
If no handoff exists, run base selection first, including for a single resume.
- Very specific: line 33
Never infer requirements from a title, snippet, or expired link.
- Very specific: line 35
Use the local .venv Python for every command.
- Distinctive: line 39
Read the handoff, the base structured evidence, the approved donor evidence, and references/evidence-policy.md.
- Very specific: line 52
Write applications/<slug>/tailoring-audit.json using references/audit-contract.md and …
- Distinctive: line 58
Read references/output-spec.md.
- Distinctive: line 72
If no page images could be rendered, say that visual inspection was not possible instead of claiming it passed.
- Distinctive: line 95
Never overwrite a master resume or its structured source file.
- Distinctive: line 96
Never create or strengthen metrics, scope, ownership, seniority, tools-in-use, employers, titles, dates, degrees, licenses, clearance, …
- Distinctive: line 97
Never move a claim to a different employer or employment period.
- Very specific: line 98
Do not use ats-added skills anywhere in the submitted resume.
- Distinctive: line 99
Do not hide an unmet hard gate with adjacent experience or a Skills entry.
- Distinctive: line 100
Do not use historical tailored applications as factual sources unless the user explicitly names one.
- Very specific: line 101
Do not call the work complete until both DOCX and PDF exist, verify passes, and the page render was actually inspected.
“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
Turn one selected base resume into a job-specific resume whose experience claims remain traceable while its positioning, ordering, wording, and Skills section are optimized for the target role.
Runtime and document tools
This skill uses portable tooling only: python-docx for the DOCX, LibreOffice headless (or a configured alternative) for the PDF, and Poppler or a maintained Python library for PDF inspection and page images. There is no dependency on any vendor-specific Documents or PDF tool.
Check the environment first and never install system packages silently:
python3 resume-workflow/scripts/check_dependencies.pyIf pdf_convert is unavailable, say so, install LibreOffice, or use --docx-only and state clearly that the application is not submission-ready.
Required inputs
Prefer a validated handoff.json produced by resume-base-selector. It must contain the full JD snapshot, target metadata, selected base, optional donors, structured resume paths, known gaps, and confidence. Read references/handoff-contract.md, then:
python3 resume-workflow/scripts/run_resume_workflow.py validate-handoff --slug <slug>Do not tailor until this passes. The runner refuses every later step while the handoff is missing or invalid.
If no handoff exists, run base selection first, including for a single resume.
Never infer requirements from a title, snippet, or expired link. Import PDF/DOCX
via resume-workflow/scripts/import_resumes.py, following the agent's Step 1b.
Use the local .venv Python for every command; users never hand-write JSON.
Tailoring workflow
- Read the handoff, the base structured evidence, the approved donor evidence, and references/evidence-policy.md.
- Choose
balancedby default; useatsorhmonly when the user asks or the job clearly warrants it. Read references/tailoring-method.md. - Build an internal requirement-to-evidence map. Classify every important requirement as
direct,transferable,skills-only, ornot-evidenced. - Preserve the base resume's identity: employers, roles, dates, locations, education, and chronology. A donor claim may support only the matching employer and the same underlying employment period.
- Draft
applications/<slug>/tailored_resume.jsonusing ../../../resume-workflow/schemas/tailored-resume-schema.json. Every summary or experience claim must cite one or more sourceclaim_idvalues. - Include only evidence-backed skills, marked
"evidence_status": "verified". Missing JD keywords belong in the private gap report; never add unsupported skills. Validate provenance; resolve every error before rendering:
python3 resume-workflow/scripts/run_resume_workflow.py validate-tailored --slug <slug>Write
applications/<slug>/tailoring-audit.jsonusing references/audit-contract.md and ../../../resume-workflow/schemas/tailoring-audit-schema.json, then:python3 resume-workflow/scripts/run_resume_workflow.py validate-audit --slug <slug>Read references/output-spec.md. Render and verify:
python3 resume-workflow/scripts/run_resume_workflow.py render --slug <slug> python3 resume-workflow/scripts/run_resume_workflow.py verify --slug <slug>Inspect the rendered pages when page images exist (
applications/<slug>/render-preview/*.png). Iterate until the DOCX and PDF are visually clean, ATS-readable, and within the page budget, then record the review honestly:python3 resume-workflow/scripts/run_resume_workflow.py record-visual-inspection \ --slug <slug> --status completed --performed-by "<agent or person>" --notes "<what you checked>"If no page images could be rendered, say that visual inspection was not possible instead of claiming it passed.
- Save the full application bundle without overwriting any master resume.
Output contract
For a slug such as acme-senior-business-system-analyst:
applications/<slug>/
|-- job-description.txt
|-- handoff.json
|-- tailored_resume.json
|-- tailoring-audit.json
|-- workflow-state.json
|-- <Name>_Resume_<Company>_<Role>.docx
|-- <Name>_Resume_<Company>_<Role>.pdf
`-- render-qa.jsontailoring-audit.json, workflow-state.json, and render-qa.json are private working artifacts. They are never part of the submitted resume.
Non-negotiable boundaries
- Never overwrite a master resume or its structured source file.
- Never create or strengthen metrics, scope, ownership, seniority, tools-in-use, employers, titles, dates, degrees, licenses, clearance, language fluency, or work authorization.
- Never move a claim to a different employer or employment period.
- Do not use
ats-addedskills anywhere in the submitted resume. - Do not hide an unmet hard gate with adjacent experience or a Skills entry.
- Do not use historical tailored applications as factual sources unless the user explicitly names one.
- Do not call the work complete until both DOCX and PDF exist,
verifypasses, and the page render was actually inspected.
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.

