tailor
Skill0 starsChanged 56 days agoMITView on GitHub
Produce a job-specific resume + cover letter (PDF/DOCX) derived from the master resume, for a job URL or an existing jobs/<slug> folder. Use when the candidate says "tailor", "make a resume for", "apply to this", "cover letter for", or pastes a job link.
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
- Tdeniz1/resume-engine-startertheir own version, first seen Sep 2, 2026
- alexkamen123/resume-tailortheir own version, first seen Aug 28, 2026
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
- leakyhose/resumekit★ 1same name
- ledq/resumery★ 1same name
- alexkamen123/resume-tailor★ 0same name
- donsamoylov/tailor-skill★ 0same name
- lecegues/hitapply-plugin★ 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.
In this repository15 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- applySkill
- career-pathSkill
- decideSkill
- huntSkill
- inboxSkill
- interview-prepSkill
- logSkill
- networkSkill
- offer-reviewSkill
- prefsSkill
- researchSkill
- studySkill
- trackSkill
- weeklySkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
2
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 9
If a jobs/<slug>/jd.md exists, read it.
- Very specific: line 10
Create jobs/<company-jobid-short-title>/ and write jd.md: header (title, company, job id, source URL, apply URL, location, posted/closing …
- Distinctive: line 41
Never state salary figures as fact — give a band with "verify" or say unknown.
- Distinctive: line 51
Check the printed page count and text-extraction line.
“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
/tailor <job url | jobs/<slug>>
1. Get the JD (verify it is open)
- If a
jobs/<slug>/jd.mdexists, read it. Otherwise fetch the posting. Do not trust WebFetch on ATS sites — Phenom (BCG), Workday, Oracle ORC serve a "has been filled" decoy to plain fetches. Use the Browser pane (navigate→ wait 3s →get_page_text) or the matching adapter:node -e 'import("./sources/index.mjs").then(async m=>{const s=m.getSource("phenom");console.log(JSON.stringify(await s.details({sourceId:"bcg-57792",url:"<url>"})))})'. - Create
jobs/<company-jobid-short-title>/and writejd.md: header (title, company, job id, source URL, apply URL, location, posted/closing dates, status + how verified), "What you'll do", "What you'll bring" (verbatim requirement bullets), and Fit notes: each requirement → the candidate's evidence fromprofile/master-resume.md, or "GAP".
2. Inputs (read all)
profile/master-resume.md (only source of facts), profile/certifications.md (what is obtained vs in progress), profile/preferences.json, profile/story-bank.md, profile/achievements.md (recent work not yet in master).
3. Write resume.md (ATS rules)
- No em dashes (—) or en dashes (–) anywhere in resumes or cover letters, ever (the candidate, 2026-09-16: they read as AI-written). Use commas, colons, full stops, "to" for ranges, and "|" as the header/certs separator. Run
grep -n '—\|–' jobs/<slug>/*.mdbefore rendering; it must return nothing. - Each role gets its own heading, even internships (never combine two employers under one heading).
- Certifications: list obtained ones; an exam that is booked may be listed as "(exam booked)"; the candidate's call (2026-09-16) is that an exam scheduled within the week of applying is listed as obtained, and the resume is regenerated the same day if the date slips.
- Header: name, city, phone, email, LinkedIn as plain text (not a link); add
github.com/<you>as plain text on engineering/AI resumes only, never on consulting ones. No photo, no columns, no tables, no icons. - One page for MBB (McKinsey/BCG/Bain) and graduate programs — render with
--compact; two pages max for Australian industry / Big 4 lateral roles. Check the printed page count; cut, don't shrink below --compact. Headline line under the name mirrors the JD's title vocabulary truthfully (e.g. "Technology Consultant | Oracle EPM & Applied AI"). - Summary/Profile: omit for MBB and graduate programs (not the convention — evidence only); for Australian industry / Seek / Big 4 roles keep a 3-line keyword-dense summary, no first person.
- Skills block first for technical roles; Experience first for consulting roles.
- Bullets: verb + what + tool + outcome/number. Reorder and reword master bullets to mirror JD language; never add a claim not in master. If the JD wants a number the candidate doesn't have, ask them — don't invent.
- Certifications: list obtained ones with year; in-progress ones as "in progress (exam
<date>)" — see certifications.md. Never present an unpassed exam as passed. - Consulting roles: include Leadership & Community (society leadership, volunteering). Graduate roles (BCG X): include extra-curricular/interests — ask the candidate if
master-resume.mdstill says TODO. - Australian English. Client names: generalise ("ASX200 mining client") unless the candidate has said they can name them.
4. Write cover-letter.md
≤ 1 page, 4 paragraphs: (1) role + why this firm specifically (cite something real from the JD/company), (2) two proof points matching their top requirements, (3) the AI angle — what the candidate builds outside work, (4) availability, location/relocation, close. No clichés ("I am writing to…"). Date, addressed to the recruiter named in the JD if any (BCG ANZ: recruitmentinANZ@bcg.com).
4b. Write brief.md (the advice layer shown on the dashboard's Job packs tab)
Sections, in this order, grounded in the JD, profile/career-context.md, profile/preferences.json → priority_model (tiers, interest, stay_go_factors) and reports/market-insights-<latest>.md:
- Title line:
# Brief — <role> · <P1/P2/P3> · <rating>then Verdict: one sentence (apply / apply with eyes open / skip) and why. - Does it suit you? For / Against / Net — honest, specific to the candidate.
- Priority reasoning — brand direction vs the current employer (step up / lateral / step down), interest, pay (stated or "verify"), your current employer stay-vs-go context (scandal/restructure) and the neutral interview line.
- How to position yourself — which stories lead (story-bank numbers), what to de-emphasise, how to handle the years line, what to prepare/build before the screen.
- Trajectory of this role — title ladder at that company, typical timing, exit options.
- The company, briefly — what is known; mark anything unverified and point to
/research <company>. - Process to expect — stages, assessments; mark "typical — verify".
- Risks and unknowns · 9. Pack — links to resume/cover letter/interview-prep/research/network files. Never state salary figures as fact — give a band with "verify" or say unknown.
5. Render
export PATH="$HOME/.local/lib/node/bin:$PATH"
cd "$CAREER_OS" # your career-os folder
node tools/render.mjs jobs/<slug> --name Resume_LeoLong_<Company>
# graduate programs that want one PDF (BCG X): add the transcript
node tools/render.mjs jobs/<slug> --name Application_LeoLong_<Company> --merge inbox/UWA_transcript.pdfCheck the printed page count and text-extraction line. Open the PDF (Read tool) and eyeball page 1.
6. Hand over
List the output files, the 3 biggest changes vs the Seek resume and why, any GAPs left, and what the candidate must confirm before applying. Then add to the pipeline: node tools/track.mjs add <url> --status shortlisted --company … --title … --next "Review + apply". Do not apply — that is /apply, and the candidate clicks submit.
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.

