Skill detail
resume-builder
Directly creates professionally designed resume PDFs.
Inspect before use
Automated review checks relevance, not safety or endorsement. Read the source instructions before using this skill.
SKILL.md
The saved excerpt is a snapshot from review. The external source remains the complete and most current version.
--- name: resume-builder description: Generate beautiful, professionally designed resumes as 1-2 page PDFs. Creates clean, sophisticated layouts that balance visual appeal with readability, tailored to specific job opportunities when provided. license: Complete terms in LICENSE.txt --- # Resume Builder Skill This skill creates beautifully designed, professional resumes as PDF documents. The output prioritizes clean typography, thoughtful spacing, and visual hierarchy while maintaining the practical readability employers expect. ## Required Information Before beginning, gather: 1. **Resume Context** (REQUIRED): The user's professional background, including: - Work experience with roles, companies, dates, and accomplishments - Education background - Skills and competencies - Any additional relevant sections (certifications, projects, publications, etc.) 2. **Address Verification** (ALWAYS ASK): - Prompt the user: "What address should appear on your resume? Has this changed from any previous version?" - If they have an existing resume, confirm the address is current 3. **Job-Specific Information** (OPTIONAL): - If applying for a specific role, request the job description or posting link - Ask: "Would you like me to create a cover letter as well?" - When tailoring to a job, use web_fetch to analyze the job description and align resume content accordingly ## Design Philosophy Resumes should be **sophisticated yet accessible** - think of them as the intersection of: - **Swiss design clarity**: Clean grids, thoughtful hierarchy, generous whitespace - **Editorial polish**: Typography that's refined but never fussy - **Scannable structure**: Easy for both human readers and ATS systems ### Visual Principles **Typography**: - Use 2-3 fonts maximum from `./assets/fonts` directory - Recommended combinations: - **Professional/Corporate**: Inter (headers & body) - Clean, highly readable, excellent at all sizes - **Creative/Modern**: Special Gothic (headers) + Open Sans (body) - Distinctive yet professional - **Traditional/Academic**: Open Sans throughout - Reliable, approachable, universally compatible - Headers: Clean, confident sans-serifs (moderate weight, not ultra-bold) - Body: Highly readable sans-serif at 10-11pt - Hierarchy through size, weight, and spacing - not color chaos **Layout**: - Generous margins (0.5-0.75 inches minimum) - Clear section divisions using whitespace, not heavy lines - Consistent spacing that creates rhythm - Single column or subtle two-column for optimal readability **Color** (use sparingly): - Primarily black text on white - Optional: One accent color for headers or subtle elements - Never sacrifice readability for visual flair **Spacing**: - Every element has breathing room - No cramped text or overlapping elements - Page breaks must fall naturally between sections - If content exceeds one page, ensure page 2 is substantial (not just a few lines) ## Content Guidelines ### Language & Tone **CRITICAL**: Maintain authentic, professional language. Do NOT: - Use buzzwords excessively (synergy, rockstar, ninja, guru) - Over-inflate accomplishments with hyperbole - Write in third person or use overly formal Victorian prose - Create generic, template-sounding bullet points Instead: - Use clear, direct language with strong action verbs - Quantify achievements where possible (numbers, percentages, scale) - Be specific about technologies, methodologies, and outcomes - Let accomplishments speak for themselves without excessive adjectives ### Structure **Standard Sections** (adapt as needed): 1. **Header**: Name (prominent), contact info (email, phone, LinkedIn, location) 2. **Professional Summary** (optional, 2-3 lines maximum if included) 3. **Experience**: Company, Title, Dates, 3-5 bullet points per role 4. **Education**: Degree, Institution, Graduation year, relevant honors 5. **Skills**: Organized logically (by category if extensive) 6. **Additional Sections** aRead the full source on GitHub (opens external page)