← ClaudeAtlas

resume-ats-linkedin-optimizerlisted

Build, rewrite, tailor, and audit a world-class resume/CV and LinkedIn profile that wins interviews — optimized at the same time for ATS parsing (Workday, Greenhouse, Lever, Taleo, iCIMS, Ashby), fast recruiter skim-reading, and LinkedIn recruiter search. Use when the user wants to create, improve, fix, or review a resume or CV; tailor a resume to a specific job description; run an ATS check or audit; write or strengthen achievement bullet points; quantify accomplishments; optimize a LinkedIn headline, About, skills, or experience; write a tailored cover letter; or generally maximize their chances of getting hired. Governing rule: zero fabrication — never invent facts, employers, dates, titles, or numbers.
artificialguybr/resume-ats-linkedin-optimizer · ★ 1 · AI & Automation · score 75
Install: claude install-skill artificialguybr/resume-ats-linkedin-optimizer
# Resume + ATS + LinkedIn Optimizer Turn a person's real experience into the strongest possible resume, CV, and LinkedIn profile — one that survives every major ATS parser, wins the 7-second recruiter skim, and ranks in LinkedIn recruiter search. This skill encodes what university career centers (Harvard, MIT), ex-FAANG recruiters, eye-tracking research, and the actual behavior of production ATS agree on, and resolves the places where popular advice is wrong or outdated. ## The prime directive: zero fabrication **Never invent, inflate, or guess a fact.** No fabricated employers, titles, dates, degrees, or metrics. This is non-negotiable and overrides every other goal — a resume that lies fails the moment a recruiter or reference check catches it, and it puts the user's career at risk. What this means in practice: - Every number, employer, title, and date must come from the user or a document they gave you. If you don't have it, ask — don't fill it in. - Metrics the user *has but didn't write down* are fair game to **excavate** (Phase 2). Estimates are allowed **only** when the user confirms them and they are hedged ("~", "approximately", "roughly"). See `assets/metric-proxies.md`. - You may sharpen *language* freely (weak verb → strong verb, task → outcome, vague → specific). You may not sharpen *facts*. - When you reword something, preserve its truth. "Helped build" does not become "single-handedly architected." If the user pushes you to fabricate, refuse and