resume-builder
Skill0 starsChanged 17 days agoMITView on GitHub
Build one-page, ATS-safe resumes and matching cover letters as PDFs in a clean "Slate" style (single column, centered name, small-caps section titles, IBM Plex Sans, 11pt minimum) from structured JSON. Use when a tailored resume or cover letter is needed for a job, or when base resume variants are being created.
25 other projects use a version of this.
Adopted by
Most recently taken up by
- siddqamar/resume-builder-skilltheir own version, first seen Nov 8, 2026
- HeisenbergUwU/resume-builder-skilltheir own version, first seen Nov 8, 2026
- HaroonArshad-53/skills-for-everyonetheir own version, first seen Oct 17, 2026
- barryallen16/ats-resume-creation-skilltheir own version, first seen Oct 15, 2026
- aadilmallick/claude-skillstheir own version, first seen Oct 15, 2026
- Chasen-Liao/resume-skillstheir own version, first seen Oct 1, 2026
Other versions25 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 25
- Jichengyuuuuu/resume-builder-skill★ 160same name
- StoneLL1/resume-builder★ 127same name
- Exploration-labs/Nates-Substack-Skills★ 55same name
- cosen1024/resume-builder-skill★ 43same name
- Chasen-Liao/resume-skills★ 36same name
- aiunlocked1412/claude-skill-unlock★ 18same name
- jackjin1997/ClawForge★ 12same name
- toddward/claude-skills-playground★ 12same name
- phanghonghao/THU-Awesome-Skills★ 8same name
- HeisenbergUwU/resume-builder-skill★ 6same name
15 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 repository4 other files it gives its agents.
- job-fact-checkSkill
- job-form-answersSkill
- job-outreachSkill
- job-pipelineSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
0
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 11
Every line comes from the candidate's facts file.
- Very specific: line 30
Look at the page (on macOS: qlmanage -t -s 1100 -o /tmp file.pdf, then open the PNG): no orphan lines, dates aligned, no highlighted …
“Common” is measured: kept by at least 6 in 10 of the 16 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 and cover letter builder
Output: a one-page PDF resume and an optional one-page cover letter with the same letterhead. Single column, no tables, icons or photos, real text in the PDF, so applicant tracking systems parse it cleanly.
Content rules
- Every line comes from the candidate's facts file. Run
job-fact-checkbefore calling anything final. - Body text never below 11pt. If a page overflows, cut or tighten wording; do not shrink type.
- Bullets: action verb + what + how + result. Prefer concrete verbs (built, designed, defined, coordinated) over vague ones ("responsible for", "led").
- Give a one-line descriptor only to employers a reader is unlikely to know.
- Letter size for US employers, A4 elsewhere.
- Cover letters: 250–380 words; opening (role + strongest fit), two proof paragraphs mapped to the JD's main needs, a specific why-this-company paragraph, a short close with availability. No "I am writing to apply", no "dream job".
Build
python3 skills/resume-builder/scripts/build_resume.py content.json out/resume.html
bash skills/resume-builder/scripts/render_pdf.sh out/resume.html "out/<First>_<Last>_Resume.pdf"
python3 skills/resume-builder/scripts/build_cover_letter.py letter.json out/letter.html
bash skills/resume-builder/scripts/render_pdf.sh out/letter.html "out/<First>_<Last>_Cover_Letter.pdf"See examples/ at the repository root for content files. render_pdf.sh fails if the PDF is not exactly one page.
Check before delivering
render_pdf.shreports one page.- Look at the page (on macOS:
qlmanage -t -s 1100 -o /tmp file.pdf, then open the PNG): no orphan lines, dates aligned, no highlighted placeholders left in a letter. job-fact-checkpasses.- File names are clean:
<First>_<Last>_Resume.pdfand<First>_<Last>_Cover_Letter.pdf. No page size, variant or company name in submitted file names.
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.

