tailor
Skill1 starsChanged 3 months agoMITView on GitHub
Tailor the resume to a specific job posting — extract what the posting values, map it against the candidate's bullets, then reorder, re-keyword, and swap content to match. Use when the user shares a job posting, link, or company they are applying to.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- rafaym1/scholarship-desktheir own version, first seen Nov 16, 2026
- qbeka/jev-job-searchtheir own version, first seen Nov 12, 2026
- askoulwassim/perfect-placementtheir own version, first seen Oct 15, 2026
- lecegues/hitapply-plugintheir own version, first seen Oct 11, 2026
- leoleolro/career-ostheir own version, first seen Sep 22, 2026
- Tdeniz1/resume-engine-startertheir own version, first seen Sep 2, 2026
Used with
Projects with it also use inbox.
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.
kv0906Skillinbox
Quick capture mode (with content) or batch processing mode (no content). GTD-style routing of inbox items to proper folders. Use "/inbox thought to capture" or "/inbox" to process.
Also in 3 projects that use this
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- qbeka/jev-job-search★ 368same name
- dralgorhythm/claude-agentic-framework★ 118same name
- rafaym1/scholarship-desk★ 18same name
- askoulwassim/perfect-placement★ 3same name
- ledq/resumery★ 1same name
- alexkamen123/resume-tailor★ 0same name
- donsamoylov/tailor-skill★ 0same name
- lecegues/hitapply-plugin★ 0same name
- leoleolro/career-os★ 0same name
- Tdeniz1/resume-engine-starter★ 0same name
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.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Read rules/core.md, rules/profile.md, rules/style.md, and rules/my-rules.md first if you haven't this session.
- Distinctive: line 20
Must-have skills and technologies (repeated or listed as requirements)
- Very specific: line 27
Read resume/resume.tex. For each bullet, note which of the posting's keywords and qualities it already demonstrates, which it could …
“Common” is measured: kept by at least 6 in 10 of the 8 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
Tailoring the resume to a posting
Read rules/core.md, rules/profile.md, rules/style.md, and rules/my-rules.md
first if you haven't this session.
Hard rule: never fabricate. Tailoring means re-emphasizing and re-wording real experience, never inventing skills or inflating scope. If the posting wants something the candidate genuinely lacks, say so — that gap is information for the user, not something to paper over.
1. Digest the posting
From the posting (ask for it if not provided), extract:
- Role, team, seniority
- Must-have skills and technologies (repeated or listed as requirements)
- Nice-to-haves
- Recurring language and values ("ownership", "ships fast", "cross-functional") — this is the vocabulary the resume should echo
2. Inventory the resume
Read resume/resume.tex. For each bullet, note which of the posting's keywords and
qualities it already demonstrates, which it could honestly demonstrate with rewording,
and which it can't.
3. Propose before editing
Present a tailoring plan and get agreement before touching the file:
- Reorder: most posting-relevant experience/projects/bullets first (first bullet per role = the one this hiring manager cares about most)
- Reword: truthful keyword swaps (e.g. their stack's terminology where the candidate's experience genuinely matches)
- Swap: bullets or projects to bench for this application, and what replaces them
- Gaps: requirements nothing in the resume covers
4. Apply and verify
- Suggest a git branch named after the application (e.g.
apply/company-role) so the main branch stays the canonical resume. - Make the edits, then
make check(must PASS) andmake render+ view the png. - Summarize what changed and which posting keywords the resume now hits.
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.

