← ClaudeAtlas

ats-resume-builderlisted

Build, review, or tailor a software engineering resume/CV that survives ATS parsing and recruiter skimming, following the Tech Interview Handbook's FAANG resume guide. Produces a single-page ATS-safe .docx plus a submission-ready PDF. Use this skill whenever the user mentions a resume, CV, curriculum vitae, job application, "applying to Google/Meta/Amazon", ATS or applicant tracking systems, rewriting or strengthening resume bullet points, tailoring a resume to a job description, or asks for feedback on a resume they upload — even if they only say something vague like "make this sound better" while attaching a resume, or ask for help with just one section (summary, skills, experience, projects). Also use it when someone asks how to describe an internship, side project, or career gap on a resume.
udcw1995/ats-resume-builder · ★ 0 · Web & Frontend · score 62
Install: claude install-skill udcw1995/ats-resume-builder
# CV Builder A resume has two readers and both can reject it before a human ever considers the candidate: 1. **The parser.** An applicant tracking system (ATS) converts the file into database fields. Anything it cannot read — a two-column layout, a name inside a text box, dates inside a table — becomes a blank field or garbled text. A blank "Company" field is often an automatic filter-out. 2. **The skimmer.** A recruiter spends a handful of seconds deciding whether to read properly. They are usually not an engineer. "Contributed to an open source project" means nothing to them; "maintainer of Docusaurus, the static site generator behind React Native and Jest's docs" means a great deal. Every rule in this skill exists to serve one of those two readers. When a judgement call comes up that the rules do not cover, resolve it by asking which reader is being served and what would help them. Source material: the Tech Interview Handbook resume guide (https://www.techinterviewhandbook.org/resume/). The distilled ruleset lives in `references/handbook-rules.md`. --- ## Pick a mode | The user is asking for | Mode | Start at | |---|---|---| | A resume from scratch, or from notes / a LinkedIn export / an old messy doc | **Build** | [Mode A](#mode-a--build) | | Feedback, a critique, a score, "is this good enough for FAANG?" | **Review** | [Mode B](#mode-b--review) | | A version aimed at a specific job posting or company | **Tailor** | [Mode C](#mode-c--tailor) | Th