← ClaudeAtlas

resume-designerlisted

Create, design, rewrite, review, tailor, or critique a resume or CV, and export it to PDF, DOCX, or plain text. Use this skill whenever the user mentions a resume, résumé, CV, curriculum vitae, cover letter pairing, job application, "my experience for a role", ATS or applicant tracking systems, resume templates or formatting, making a resume one page, tailoring a resume to a job description or posting, resume bullet points, or asks to make a resume look professional, premium, modern, or ATS-friendly. Also use when the user shares an existing resume file (PDF/DOCX/YAML) and wants feedback, a redesign, or an export. Produces a typeset, single-column, parse-verified document from an editable YAML source.
marnenivishal/resume-designer · ★ 0 · Data & Documents · score 70
Install: claude install-skill marnenivishal/resume-designer
# Resume Designer Produce a resume that survives both readers: the parser that sees only a text stream, and the human who spends seconds on it. **Do not hand-write HTML for a resume.** Write YAML, use the templates, verify the output. The templates encode measured constraints that are easy to break by hand. ## Scope This skill handles resume/CV content, design, and export (PDF/DOCX/TXT/HTML), plus tailoring to a job posting and critique of an existing resume. It does **not** handle: submitting applications, impersonating a real person, fabricating employment history, credentials, or metrics, or writing content designed to deceive an employer. See Integrity below. ## Workflow ### 1. Gather the material Read `references/intake.md` for the full question set. Never invent facts to fill a gap — ask. Minimum viable: name, contact, target role, work history with dates, and one outcome per role. If the user supplies an existing resume, extract it first: ```bash python scripts/extract.py old_resume.pdf -o resume.yaml # PDF/DOCX -> editable YAML ``` ### 2. Establish context before designing Three answers change the output. Ask if unclear: - **Target role and seniority** — drives section order and length. - **Region** — photo/DOB/address rules differ and some are legal issues. See `references/variants.md`. - **Industry** — finance, academia, US federal, and design each have hard, non-obvious conventions. See `references/variants.md`. ### 3. Write the content Content