resume-formatter
Ensure ATS-friendly formatting and create clean scannable layouts
What this skill does
# Resume Formatter ## When to Use This Skill Use this skill when the user: - Needs help with resume layout and formatting - Has a messy or hard-to-read resume - Wants to ensure ATS compatibility through formatting - Needs a clean, professional design - Mentions: "format resume", "resume layout", "resume design", "clean resume", "professional format" ## Core Capabilities - Structure resumes for optimal readability - Ensure ATS compatibility through formatting - Create visual hierarchy - Optimize white space and margins - Select appropriate fonts and sizes - Balance aesthetic appeal with functionality ## Formatting Fundamentals ### The Dual Audience Challenge Your resume must work for: 1. **ATS (Applicant Tracking Systems)** - Robots that parse text 2. **Human Readers** - Recruiters who scan quickly **The Solution:** Clean, simple formatting that satisfies both. ## Document Setup ### Page Length - **Entry Level (0-5 years):** 1 page - **Mid-Level (5-15 years):** 1-2 pages - **Senior/Executive (15+ years):** 2 pages (max 3 for executives) ### Margins - **Recommended:** 0.5" - 1" all sides - **Minimum:** 0.5" (don't go smaller) - **Maximum:** 1" (don't waste space) ### Font Selection **Safe, ATS-Friendly Fonts:** - **Sans-serif:** Arial, Calibri, Helvetica, Verdana - **Serif:** Times New Roman, Georgia, Garamond **Font Sizes:** - **Name:** 16-20pt - **Section Headers:** 12-14pt - **Body Text:** 10-12pt - **Minimum readable:** 10pt ### Spacing - **Line spacing:** 1.0 to 1.15 - **Space after paragraphs:** 6-12pt - **Section spacing:** 12-16pt between sections ## ATS-Safe Formatting Rules ### DO: - ✅ Use standard fonts - ✅ Use simple bullet points (•, -, *) - ✅ Use bold and italic sparingly - ✅ Use standard section headers - ✅ Save as .docx or text-based .pdf - ✅ Put contact info in body (not header) - ✅ Use single column layout - ✅ Use consistent formatting throughout ### DON'T: - ❌ Use tables (except simple ones for contact info) - ❌ Use text boxes - ❌ Use columns (multi-column layouts) - ❌ Use headers/footers for important info - ❌ Use images or graphics - ❌ Use unusual fonts - ❌ Use skill bars or progress indicators - ❌ Use special characters or emojis - ❌ Use color for essential information ## Section Organization ### Standard Section Order ``` 1. Contact Information 2. Professional Summary (optional) 3. Skills/Technical Skills 4. Professional Experience 5. Education 6. Certifications (if relevant) 7. Additional (volunteer, languages, etc.) ``` ### Section Header Formatting **ATS-Recognized Headers:** - PROFESSIONAL EXPERIENCE or WORK EXPERIENCE - EDUCATION - SKILLS or TECHNICAL SKILLS - PROFESSIONAL SUMMARY or SUMMARY - CERTIFICATIONS - PROJECTS **Format Options:** ``` PROFESSIONAL EXPERIENCE ━━━━━━━━━━━━━━━━━━━━━━ or Professional Experience _______________________ or PROFESSIONAL EXPERIENCE ``` ## Contact Information Layout ### Recommended Format ``` JOHN SMITH [email protected] | (555) 123-4567 | linkedin.com/in/johnsmith San Francisco, CA ``` ### Alternative Format ``` JOHN SMITH San Francisco, CA [email protected] | (555) 123-4567 LinkedIn: linkedin.com/in/johnsmith | GitHub: github.com/johnsmith ``` ### What to Include - ✅ Full name - ✅ Professional email - ✅ Phone number - ✅ City, State (no full address needed) - ✅ LinkedIn URL - ✅ Portfolio/GitHub (if relevant) ### What to Exclude - ❌ Full street address - ❌ Photo - ❌ Date of birth - ❌ Marital status - ❌ Multiple phone numbers - ❌ Personal social media ## Experience Section Formatting ### Standard Format ``` COMPANY NAME | City, ST Job Title | Month Year - Month Year • Achievement bullet with metrics and results • Achievement bullet with metrics and results • Achievement bullet with metrics and results ``` ### Alternative Format ``` Job Title COMPANY NAME, City, ST Month Year - Month Year • Achievement bullet with metrics and results • Achievement bullet with metrics and results ``` ### Date Formatting - **Consistent format:** Use same format throughout - **Recommended:** Month Year (Jan 2020 - Present) - **Also acceptable:** MM/YYYY (01/2020 - Present) - **Avoid:** Full dates (January 15, 2020) ### Bullet Point Guidelines - **Length:** 1-2 lines each - **Format:** Start with action verb, end with result - **Quantity:** 3-6 bullets per role (more for recent, fewer for old) - **Symbol:** Use standard bullets (•, -, *) ## Skills Section Formatting ### Option 1: Simple List ``` SKILLS Python, JavaScript, SQL, React, Node.js, AWS, Docker, Git, Agile, JIRA ``` ### Option 2: Categorized ``` TECHNICAL SKILLS Languages: Python, JavaScript, TypeScript, SQL Frameworks: React, Node.js, Django, Flask Tools: AWS, Docker, Kubernetes, Git, Jenkins ``` ### Option 3: Columns (Careful with ATS) ``` SKILLS Languages Frameworks Tools Python React AWS JavaScript Node.js Docker SQL Django Git ``` **Note:** Multi-column layouts may cause ATS issues. Test before using. ## Education Section Formatting ### Standard Format ``` EDUCATION Bachelor of Science in Computer Science University of California, Berkeley | 2018 GPA: 3.8/4.0 (include if 3.5+) ``` ### With Honors/Details ``` EDUCATION MBA, Finance & Strategy | Stanford Graduate School of Business | 2020 • Graduated with Distinction • Relevant Coursework: Corporate Finance, M&A Strategy ``` ## Visual Hierarchy Principles ### Hierarchy Order 1. **Name** - Largest, most prominent 2. **Section Headers** - Clear divisions 3. **Job Titles/Company Names** - Easy to scan 4. **Bullet Points** - The details ### Creating Hierarchy - Use font SIZE to create levels - Use **BOLD** for emphasis (names, titles, headers) - Use CAPS for section headers - Use consistent spacing to separate sections ## White Space Management ### Good White Space: - Between sections (clear separation) - After headings (visual breathing room) - Between bullets (don't cram) - Around margins (frame the content) ### Bad White Space: - Huge gaps between sections - Inconsistent spacing - Half-empty pages - Excessive margins eating space ## Common Formatting Mistakes ### Mistake 1: Wall of Text **Problem:** Dense paragraphs with no bullets **Solution:** Use bullet points, keep paragraphs short ### Mistake 2: Inconsistent Formatting **Problem:** Different fonts, sizes, or styles throughout **Solution:** Pick one format and stick to it ### Mistake 3: Trying to Be Creative **Problem:** Fancy designs that break ATS **Solution:** Save creativity for portfolio, not resume ### Mistake 4: Too Much Information **Problem:** Cramming everything onto one page **Solution:** Edit ruthlessly, prioritize relevance ### Mistake 5: Not Enough Information **Problem:** Half-page resume with massive margins **Solution:** Add detail, reduce margins (to 0.5") ## File Format Guidelines ### For Online Applications - **.docx** - Best for ATS parsing - **.pdf** - Good if created from Word (not scanned) ### For Email/Direct Send - **.pdf** - Preserves formatting ### File Naming ``` FirstName_LastName_Resume.pdf JohnSmith_Resume_ProductManager.pdf ``` **Avoid:** - resume_final_v2_updated_FINAL.docx - resume (1).pdf - Untitled document.docx ## Output Format When formatting a resume: ```markdown # RESUME FORMATTING REVIEW ## Current Issues - [ ] [Issue 1] - [ ] [Issue 2] - [ ] [Issue 3] ## Recommended Changes ### Document Setup - Margins: [Current] → [Recommended] - Font: [Current] → [Recommended] - Font sizes: [Current] → [Recommended] ### Section Order **Current:** [Current order] **Recommended:** [New order and why] ### Visual Improvements - [Specific change 1] - [Specific change 2] ### ATS Compatibility Fixes - [Fix 1] - [Fix 2] ## Before/After Preview ### Before: [Description or example of current formatting] ### After: [Description or example of improved formatting] ``` ## Quick Formatting Checklist Before submitting any resume: - ✅ One page (or two if warrante
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.