[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76VT6QCJ875WBDENT10BBVW":3,"skill-same:01M76VT6QCJ875WBDENT10BBVW":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M76VT6QCJ875WBDENT10BBVW","Resume ATS Optimizer",null,"Optimize resumes for Applicant Tracking Systems, check ATS compatibility, and analyze keyword match","davidcoachdev\u002Fdcfiles","davidcoachdev","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F69812733?v=4","01M758C4BR16TAV1N47W319E9V","David H. Caycedo Blum.","01M758C4CCZA2ZYGA0BGMXCDRH",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fopencode\u002Fskills\u002Fresume-ats-optimizer\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: Resume ATS Optimizer\ndescription: Optimize resumes for Applicant Tracking Systems, check ATS compatibility, and analyze keyword match\nlicense: Apache-2.0\nmetadata:\n  author: gentleman-programming\n  version: \"1.0\"\n---\n\n# Resume ATS Optimizer\n\n## When to Use This Skill\n\nUse this skill when the user wants to:\n- Optimize their resume for Applicant Tracking Systems (ATS)\n- Check if their resume will pass automated screening\n- Understand why their applications aren't getting responses\n- Fix formatting issues that break ATS parsers\n- Mentions keywords like: \"ATS\", \"not getting interviews\", \"resume not working\", \"optimize resume\"\n\nAlso use when the user provides a resume file and mentions they're applying to jobs.\n\n## Core Capabilities\n\n- Parse resume and test ATS compatibility\n- Identify formatting issues that break ATS parsers\n- Generate ATS-friendly formatting recommendations\n- Evaluate file format and naming conventions\n- Audit section headers and contact info layout\n\n## The ATS Problem\n\n75% of resumes are rejected by Applicant Tracking Systems before a human ever sees them. Companies use ATS to:\n- Filter out unqualified candidates automatically\n- Search for specific keywords from job requirements\n- Parse resumes into structured data\n- Rank candidates by keyword match percentage\n\nCommon reasons resumes fail ATS:\n1. Poor formatting (tables, columns, headers\u002Ffooters)\n2. Missing keywords from job description\n3. Inconsistent section headers\n4. Non-standard fonts or special characters\n5. Text embedded in images\n6. Incorrect file format\n\n## ATS Compatibility Checklist\n\n### File Format\n- ✅ Use .docx or .pdf (not .pages, .odt)\n- ✅ PDF must be text-based, not scanned image\n- ✅ File name: \"FirstName_LastName_Resume.pdf\"\n\n### Font & Formatting\n- ✅ Standard fonts: Arial, Calibri, Georgia, Times New Roman\n- ✅ Font size: 10-12pt for body, 14-16pt for headers\n- ✅ No text boxes, tables, or columns\n- ✅ No headers\u002Ffooters (put contact info in body)\n- ✅ No images, graphics, or charts\n- ✅ Consistent date formats (MM\u002FYYYY)\n- ✅ Standard bullet points (•, -, *)\n\n### Section Headers\nUse standard, recognizable headers:\n- ✅ \"Professional Experience\" or \"Work Experience\" (not \"Where I've Been\")\n- ✅ \"Education\" (not \"Academic Background\")\n- ✅ \"Skills\" (not \"Core Competencies\")\n- ✅ \"Summary\" or \"Professional Summary\"\n\n### Contact Information\n```\nJohn Smith\nemail@example.com | (555) 123-4567 | LinkedIn: linkedin.com\u002Fin\u002Fjohnsmith\nSan Francisco, CA\n```\n\nNOT in header\u002Ffooter, and avoid:\n- ❌ Tables for contact info\n- ❌ Special characters in email\n- ❌ Multiple phone numbers\n- ❌ Full mailing address (city\u002Fstate is enough)\n\n## Common ATS Failure Patterns\n\n### Pattern 1: Creative Formatting\n```\n❌ PROBLEM:\n[Two-column layout with graphics]\n[Skill bars and proficiency charts]\n[Text in colored boxes]\n\n✅ SOLUTION:\n- Single column layout\n- Text-only skills list\n- Simple bullet points\n```\n\n### Pattern 2: Unconventional Section Names\n```\n❌ PROBLEM:\n\"My Journey\" (instead of Experience)\n\"What I Bring to the Table\" (instead of Skills)\n\"Academic Pursuits\" (instead of Education)\n\n✅ SOLUTION:\nUse standard headers ATS recognizes\n```\n\n### Pattern 3: Missing Keywords\n```\n❌ PROBLEM:\nJob requires: \"Python, SQL, Data Visualization\"\nResume says: \"Programming, databases, making charts\"\n\n✅ SOLUTION:\nUse exact terminology from job description\n```\n\n### Pattern 4: Keyword Stuffing\n```\n❌ PROBLEM:\nSkills: Python, Python programming, Python developer, Python expert, Python specialist, Advanced Python...\n\n✅ SOLUTION:\nSkills: Python, SQL, JavaScript, React, Node.js\n(Then incorporate naturally in bullets)\n```\n\n## Industry-Specific Considerations\n\n### Tech Resumes\n- Emphasize programming languages and frameworks\n- Include GitHub, portfolio links in Skills section (not header)\n- Certifications and courses matter highly\n\n### Business\u002FFinance\n- Focus on software proficiency (Excel, SAP, Salesforce)\n- Certifications critical (CPA, CFA, PMP)\n- Industry keywords (P&L, ROI, KPI)\n\n### Healthcare\n- Licenses and certifications required\n- Specific systems (Epic, Cerner, MEDITECH)\n- Compliance keywords (HIPAA, Joint Commission)\n\n### Marketing\n- Platform expertise (HubSpot, Salesforce, Google Analytics)\n- Channel keywords (SEO, PPC, email marketing)\n- Metrics and results-driven language\n\n## Edge Cases & Special Situations\n\n### Career Changers\n- Focus on transferable skills\n- Use keywords from TARGET industry, not just current\n- May need two resume versions for ATS\n\n### Recent Graduates\n- Education section becomes priority for keywords\n- Include relevant coursework, projects\n- Internships count as experience - use those keywords\n\n### Executive Level\n- ATS still matters for senior roles\n- Focus on strategic keywords\n- Include board experience, P&L size, team size\n\n### Gaps in Employment\n- Use years only (not months) if it helps\n- Include freelance\u002Fconsulting with keywords\n- Volunteer work can include relevant keywords\n\n## Implementation Checklist\n\nWhen helping user optimize for ATS:\n\n1. ✅ Scan current resume for ATS compatibility issues\n2. ✅ Analyze job description for required keywords\n3. ✅ Calculate current match score\n4. ✅ Identify specific missing keywords\n5. ✅ Suggest exact placements for new keywords\n6. ✅ Flag formatting problems\n7. ✅ Provide before\u002Fafter examples\n8. ✅ Re-score after suggested changes\n9. ✅ Verify file format and naming\n10. ✅ Test with ATS simulator if possible\n\n## Success Metrics\n\nAfter optimization, the resume should:\n- Score 80%+ match for target job descriptions\n- Pass ATS parsing test (all sections recognized)\n- Have zero formatting errors\n- Include all critical keywords 2-4x each\n- Read naturally (not keyword-stuffed)\n- Be ready to submit immediately\n\n## Formatting Fundamentals\n\n### The Dual Audience Challenge\n\nYour resume must work for:\n1. **ATS (Applicant Tracking Systems)** - Robots that parse text\n2. **Human Readers** - Recruiters who scan quickly\n\n**The Solution:** Clean, simple formatting that satisfies both.\n\n\n## Document Setup\n\n### Page Length\n- **Entry Level (0-5 years):** 1 page\n- **Mid-Level (5-15 years):** 1-2 pages\n- **Senior\u002FExecutive (15+ years):** 2 pages (max 3 for executives)\n\n### Margins\n- **Recommended:** 0.5\" - 1\" all sides\n- **Minimum:** 0.5\" (don't go smaller)\n- **Maximum:** 1\" (don't waste space)\n\n### Font Selection\n\n**Safe, ATS-Friendly Fonts:**\n- **Sans-serif:** Arial, Calibri, Helvetica, Verdana\n- **Serif:** Times New Roman, Georgia, Garamond\n\n**Font Sizes:**\n- **Name:** 16-20pt\n- **Section Headers:** 12-14pt\n- **Body Text:** 10-12pt\n- **Minimum readable:** 10pt\n\n### Spacing\n- **Line spacing:** 1.0 to 1.15\n- **Space after paragraphs:** 6-12pt\n- **Section spacing:** 12-16pt between sections\n\n\n## ATS-Safe Formatting Rules\n\n### DO:\n- ✅ Use standard fonts\n- ✅ Use simple bullet points (•, -, *)\n- ✅ Use bold and italic sparingly\n- ✅ Use standard section headers\n- ✅ Save as .docx or text-based .pdf\n- ✅ Put contact info in body (not header)\n- ✅ Use single column layout\n- ✅ Use consistent formatting throughout\n\n### DON'T:\n- ❌ Use tables (except simple ones for contact info)\n- ❌ Use text boxes\n- ❌ Use columns (multi-column layouts)\n- ❌ Use headers\u002Ffooters for important info\n- ❌ Use images or graphics\n- ❌ Use unusual fonts\n- ❌ Use skill bars or progress indicators\n- ❌ Use special characters or emojis\n- ❌ Use color for essential information\n\n\n## Section Organization\n\n### Standard Section Order\n\n```\n1. Contact Information\n2. Professional Summary (optional)\n3. Skills\u002FTechnical Skills\n4. Professional Experience\n5. Education\n6. Certifications (if relevant)\n7. Additional (volunteer, languages, etc.)\n```\n\n### Section Header Formatting\n\n**ATS-Recognized Headers:**\n- PROFESSIONAL EXPERIENCE or WORK EXPERIENCE\n- EDUCATION\n- SKILLS or TECHNICAL SKILLS\n- PROFESSIONAL SUMMARY or SUMMARY\n- CERTIFICATIONS\n- PROJECTS\n\n**Format Options:**\n```\nPROFESSIONAL EXPERIENCE\n━━━━━━━━━━━━━━━━━━━━━━\n\nor\n\nProfessional Experience\n_______________________\n\nor\n\nPROFESSIONAL EXPERIENCE\n```\n\n\n## Contact Information Layout\n\n### Recommended Format\n```\nJOHN SMITH\njohn.smith@email.com | (555) 123-4567 | linkedin.com\u002Fin\u002Fjohnsmith\nSan Francisco, CA\n```\n\n### Alternative Format\n```\nJOHN SMITH\nSan Francisco, CA\njohn.smith@email.com | (555) 123-4567\nLinkedIn: linkedin.com\u002Fin\u002Fjohnsmith | GitHub: github.com\u002Fjohnsmith\n```\n\n### What to Include\n- ✅ Full name\n- ✅ Professional email\n- ✅ Phone number\n- ✅ City, State (no full address needed)\n- ✅ LinkedIn URL\n- ✅ Portfolio\u002FGitHub (if relevant)\n\n### What to Exclude\n- ❌ Full street address\n- ❌ Photo\n- ❌ Date of birth\n- ❌ Marital status\n- ❌ Multiple phone numbers\n- ❌ Personal social media\n\n\n## Experience Section Formatting\n\n### Standard Format\n```\nCOMPANY NAME | City, ST\nJob Title | Month Year - Month Year\n\n• Achievement bullet with metrics and results\n• Achievement bullet with metrics and results\n• Achievement bullet with metrics and results\n```\n\n### Alternative Format\n```\nJob Title\nCOMPANY NAME, City, ST                    Month Year - Month Year\n\n• Achievement bullet with metrics and results\n• Achievement bullet with metrics and results\n```\n\n### Date Formatting\n- **Consistent format:** Use same format throughout\n- **Recommended:** Month Year (Jan 2020 - Present)\n- **Also acceptable:** MM\u002FYYYY (01\u002F2020 - Present)\n- **Avoid:** Full dates (January 15, 2020)\n\n### Bullet Point Guidelines\n- **Length:** 1-2 lines each\n- **Format:** Start with action verb, end with result\n- **Quantity:** 3-6 bullets per role (more for recent, fewer for old)\n- **Symbol:** Use standard bullets (•, -, *)\n\n\n## Skills Section Formatting\n\n### Option 1: Simple List\n```\nSKILLS\nPython, JavaScript, SQL, React, Node.js, AWS, Docker, Git, Agile, JIRA\n```\n\n### Option 2: Categorized\n```\nTECHNICAL SKILLS\nLanguages: Python, JavaScript, TypeScript, SQL\nFrameworks: React, Node.js, Django, Flask\nTools: AWS, Docker, Kubernetes, Git, Jenkins\n```\n\n### Option 3: Columns (Careful with ATS)\n```\nSKILLS\nLanguages        Frameworks       Tools\nPython           React            AWS\nJavaScript       Node.js          Docker\nSQL              Django           Git\n```\n\n**Note:** Multi-column layouts may cause ATS issues. Test before using.\n\n\n## Education Section Formatting\n\n### Standard Format\n```\nEDUCATION\nBachelor of Science in Computer Science\nUniversity of California, Berkeley | 2018\nGPA: 3.8\u002F4.0 (include if 3.5+)\n```\n\n### With Honors\u002FDetails\n```\nEDUCATION\nMBA, Finance & Strategy | Stanford Graduate School of Business | 2020\n• Graduated with Distinction\n• Relevant Coursework: Corporate Finance, M&A Strategy\n```\n\n\n## Visual Hierarchy Principles\n\n### Hierarchy Order\n1. **Name** - Largest, most prominent\n2. **Section Headers** - Clear divisions\n3. **Job Titles\u002FCompany Names** - Easy to scan\n4. **Bullet Points** - The details\n\n### Creating Hierarchy\n- Use font SIZE to create levels\n- Use **BOLD** for emphasis (names, titles, headers)\n- Use CAPS for section headers\n- Use consistent spacing to separate sections\n\n\n## White Space Management\n\n### Good White Space:\n- Between sections (clear separation)\n- After headings (visual breathing room)\n- Between bullets (don't cram)\n- Around margins (frame the content)\n\n### Bad White Space:\n- Huge gaps between sections\n- Inconsistent spacing\n- Half-empty pages\n- Excessive margins eating space\n\n\n## Common Formatting Mistakes\n\n### Mistake 1: Wall of Text\n**Problem:** Dense paragraphs with no bullets\n**Solution:** Use bullet points, keep paragraphs short\n\n### Mistake 2: Inconsistent Formatting\n**Problem:** Different fonts, sizes, or styles throughout\n**Solution:** Pick one format and stick to it\n\n### Mistake 3: Trying to Be Creative\n**Problem:** Fancy designs that break ATS\n**Solution:** Save creativity for portfolio, not resume\n\n### Mistake 4: Too Much Information\n**Problem:** Cramming everything onto one page\n**Solution:** Edit ruthlessly, prioritize relevance\n\n### Mistake 5: Not Enough Information\n**Problem:** Half-page resume with massive margins\n**Solution:** Add detail, reduce margins (to 0.5\")\n\n\n## File Format Guidelines\n\n### For Online Applications\n- **.docx** - Best for ATS parsing\n- **.pdf** - Good if created from Word (not scanned)\n\n### For Email\u002FDirect Send\n- **.pdf** - Preserves formatting\n\n### File Naming\n```\nFirstName_LastName_Resume.pdf\nJohnSmith_Resume_ProductManager.pdf\n```\n\n**Avoid:**\n- resume_final_v2_updated_FINAL.docx\n- resume (1).pdf\n- Untitled document.docx\n\n\n## Current Issues\n- [ ] [Issue 1]\n- [ ] [Issue 2]\n- [ ] [Issue 3]\n\n## Before\u002FAfter Preview\n\n### Before:\n[Description or example of current formatting]\n\n### After:\n[Description or example of improved formatting]\n\n\n## Quick Formatting Checklist\n\nBefore submitting any resume:\n- ✅ One page (or two if warranted)\n- ✅ Standard font (10-12pt body)\n- ✅ Consistent formatting throughout\n- ✅ Clear section headers\n- ✅ Appropriate white space\n- ✅ No tables, text boxes, or columns\n- ✅ Contact info in body (not header)\n- ✅ Saved as .docx or .pdf\n- ✅ Proper file name\n- ✅ Proofread for consistency\n\n> **Split from:** original 1930-line file. Partner skill: `ats-keyword-strategy` for keyword optimization, quantification metrics, and resume tailoring.\n","# Resume ATS Optimizer\n\n## When to Use This Skill\n\nUse this skill when the user wants to:\n- Optimize their resume for Applicant Tracking Systems (ATS)\n- Check if their resume will pass automated screening\n- Understand why their applications aren't getting responses\n- Fix formatting issues that break ATS parsers\n- Mentions keywords like: \"ATS\", \"not getting interviews\", \"resume not working\", \"optimize resume\"\n\nAlso use when the user provides a resume file and mentions they're applying to jobs.\n\n## Core Capabilities\n\n- Parse resume and test ATS compatibility\n- Identify formatting issues that break ATS parsers\n- Generate ATS-friendly formatting recommendations\n- Evaluate file format and naming conventions\n- Audit section headers and contact info layout\n\n## The ATS Problem\n\n75% of resumes are rejected by Applicant Tracking Systems before a human ever sees them. Companies use ATS to:\n- Filter out unqualified candidates automatically\n- Search for specific keywords from job requirements\n- Parse resumes into structured data\n- Rank candidates by keyword match percentage\n\nCommon reasons resumes fail ATS:\n1. Poor formatting (tables, columns, headers\u002Ffooters)\n2. Missing keywords from job description\n3. Inconsistent section headers\n4. Non-standard fonts or special characters\n5. Text embedded in images\n6. Incorrect file format\n\n## ATS Compatibility Checklist\n\n### File Format\n- ✅ Use .docx or .pdf (not .pages, .odt)\n- ✅ PDF must be text-based, not scanned image\n- ✅ File name: \"FirstName_LastName_Resume.pdf\"\n\n### Font & Formatting\n- ✅ Standard fonts: Arial, Calibri, Georgia, Times New Roman\n- ✅ Font size: 10-12pt for body, 14-16pt for headers\n- ✅ No text boxes, tables, or columns\n- ✅ No headers\u002Ffooters (put contact info in body)\n- ✅ No images, graphics, or charts\n- ✅ Consistent date formats (MM\u002FYYYY)\n- ✅ Standard bullet points (•, -, *)\n\n### Section Headers\nUse standard, recognizable headers:\n- ✅ \"Professional Experience\" or \"Work Experience\" (not \"Where I've Been\")\n- ✅ \"Education\" (not \"Academic Background\")\n- ✅ \"Skills\" (not \"Core Competencies\")\n- ✅ \"Summary\" or \"Professional Summary\"\n\n### Contact Information\n```\nJohn Smith\nemail@example.com | (555) 123-4567 | LinkedIn: linkedin.com\u002Fin\u002Fjohnsmith\nSan Francisco, CA\n```\n\nNOT in header\u002Ffooter, and avoid:\n- ❌ Tables for contact info\n- ❌ Special characters in email\n- ❌ Multiple phone numbers\n- ❌ Full mailing address (city\u002Fstate is enough)\n\n## Common ATS Failure Patterns\n\n### Pattern 1: Creative Formatting\n```\n❌ PROBLEM:\n[Two-column layout with graphics]\n[Skill bars and proficiency charts]\n[Text in colored boxes]\n\n✅ SOLUTION:\n- Single column layout\n- Text-only skills list\n- Simple bullet points\n```\n\n### Pattern 2: Unconventional Section Names\n```\n❌ PROBLEM:\n\"My Journey\" (instead of Experience)\n\"What I Bring to the Table\" (instead of Skills)\n\"Academic Pursuits\" (instead of Education)\n\n✅ SOLUTION:\nUse standard headers ATS recognizes\n```\n\n### Pattern 3: Missing Keywords\n```\n❌ PROBLEM:\nJob requires: \"Python, SQL, Data Visualization\"\nResume says: \"Programming, databases, making charts\"\n\n✅ SOLUTION:\nUse exact terminology from job description\n```\n\n### Pattern 4: Keyword Stuffing\n```\n❌ PROBLEM:\nSkills: Python, Python programming, Python developer, Python expert, Python specialist, Advanced Python...\n\n✅ SOLUTION:\nSkills: Python, SQL, JavaScript, React, Node.js\n(Then incorporate naturally in bullets)\n```\n\n## Industry-Specific Considerations\n\n### Tech Resumes\n- Emphasize programming languages and frameworks\n- Include GitHub, portfolio links in Skills section (not header)\n- Certifications and courses matter highly\n\n### Business\u002FFinance\n- Focus on software proficiency (Excel, SAP, Salesforce)\n- Certifications critical (CPA, CFA, PMP)\n- Industry keywords (P&L, ROI, KPI)\n\n### Healthcare\n- Licenses and certifications required\n- Specific systems (Epic, Cerner, MEDITECH)\n- Compliance keywords (HIPAA, Joint Commission)\n\n### Marketing\n- Platform expertise (HubSpot, Salesforce, Google Analytics)\n- Channel keywords (SEO, PPC, email marketing)\n- Metrics and results-driven language\n\n## Edge Cases & Special Situations\n\n### Career Changers\n- Focus on transferable skills\n- Use keywords from TARGET industry, not just current\n- May need two resume versions for ATS\n\n### Recent Graduates\n- Education section becomes priority for keywords\n- Include relevant coursework, projects\n- Internships count as experience - use those keywords\n\n### Executive Level\n- ATS still matters for senior roles\n- Focus on strategic keywords\n- Include board experience, P&L size, team size\n\n### Gaps in Employment\n- Use years only (not months) if it helps\n- Include freelance\u002Fconsulting with keywords\n- Volunteer work can include relevant keywords\n\n## Implementation Checklist\n\nWhen helping user optimize for ATS:\n\n1. ✅ Scan current resume for ATS compatibility issues\n2. ✅ Analyze job description for required keywords\n3. ✅ Calculate current match score\n4. ✅ Identify specific missing keywords\n5. ✅ Suggest exact placements for new keywords\n6. ✅ Flag formatting problems\n7. ✅ Provide before\u002Fafter examples\n8. ✅ Re-score after suggested changes\n9. ✅ Verify file format and naming\n10. ✅ Test with ATS simulator if possible\n\n## Success Metrics\n\nAfter optimization, the resume should:\n- Score 80%+ match for target job descriptions\n- Pass ATS parsing test (all sections recognized)\n- Have zero formatting errors\n- Include all critical keywords 2-4x each\n- Read naturally (not keyword-stuffed)\n- Be ready to submit immediately\n\n## Formatting Fundamentals\n\n### The Dual Audience Challenge\n\nYour resume must work for:\n1. **ATS (Applicant Tracking Systems)** - Robots that parse text\n2. **Human Readers** - Recruiters who scan quickly\n\n**The Solution:** Clean, simple formatting that satisfies both.\n\n\n## Document Setup\n\n### Page Length\n- **Entry Level (0-5 years):** 1 page\n- **Mid-Level (5-15 years):** 1-2 pages\n- **Senior\u002FExecutive (15+ years):** 2 pages (max 3 for executives)\n\n### Margins\n- **Recommended:** 0.5\" - 1\" all sides\n- **Minimum:** 0.5\" (don't go smaller)\n- **Maximum:** 1\" (don't waste space)\n\n### Font Selection\n\n**Safe, ATS-Friendly Fonts:**\n- **Sans-serif:** Arial, Calibri, Helvetica, Verdana\n- **Serif:** Times New Roman, Georgia, Garamond\n\n**Font Sizes:**\n- **Name:** 16-20pt\n- **Section Headers:** 12-14pt\n- **Body Text:** 10-12pt\n- **Minimum readable:** 10pt\n\n### Spacing\n- **Line spacing:** 1.0 to 1.15\n- **Space after paragraphs:** 6-12pt\n- **Section spacing:** 12-16pt between sections\n\n\n## ATS-Safe Formatting Rules\n\n### DO:\n- ✅ Use standard fonts\n- ✅ Use simple bullet points (•, -, *)\n- ✅ Use bold and italic sparingly\n- ✅ Use standard section headers\n- ✅ Save as .docx or text-based .pdf\n- ✅ Put contact info in body (not header)\n- ✅ Use single column layout\n- ✅ Use consistent formatting throughout\n\n### DON'T:\n- ❌ Use tables (except simple ones for contact info)\n- ❌ Use text boxes\n- ❌ Use columns (multi-column layouts)\n- ❌ Use headers\u002Ffooters for important info\n- ❌ Use images or graphics\n- ❌ Use unusual fonts\n- ❌ Use skill bars or progress indicators\n- ❌ Use special characters or emojis\n- ❌ Use color for essential information\n\n\n## Section Organization\n\n### Standard Section Order\n\n```\n1. Contact Information\n2. Professional Summary (optional)\n3. Skills\u002FTechnical Skills\n4. Professional Experience\n5. Education\n6. Certifications (if relevant)\n7. Additional (volunteer, languages, etc.)\n```\n\n### Section Header Formatting\n\n**ATS-Recognized Headers:**\n- PROFESSIONAL EXPERIENCE or WORK EXPERIENCE\n- EDUCATION\n- SKILLS or TECHNICAL SKILLS\n- PROFESSIONAL SUMMARY or SUMMARY\n- CERTIFICATIONS\n- PROJECTS\n\n**Format Options:**\n```\nPROFESSIONAL EXPERIENCE\n━━━━━━━━━━━━━━━━━━━━━━\n\nor\n\nProfessional Experience\n_______________________\n\nor\n\nPROFESSIONAL EXPERIENCE\n```\n\n\n## Contact Information Layout\n\n### Recommended Format\n```\nJOHN SMITH\njohn.smith@email.com | (555) 123-4567 | linkedin.com\u002Fin\u002Fjohnsmith\nSan Francisco, CA\n```\n\n### Alternative Format\n```\nJOHN SMITH\nSan Francisco, CA\njohn.smith@email.com | (555) 123-4567\nLinkedIn: linkedin.com\u002Fin\u002Fjohnsmith | GitHub: github.com\u002Fjohnsmith\n```\n\n### What to Include\n- ✅ Full name\n- ✅ Professional email\n- ✅ Phone number\n- ✅ City, State (no full address needed)\n- ✅ LinkedIn URL\n- ✅ Portfolio\u002FGitHub (if relevant)\n\n### What to Exclude\n- ❌ Full street address\n- ❌ Photo\n- ❌ Date of birth\n- ❌ Marital status\n- ❌ Multiple phone numbers\n- ❌ Personal social media\n\n\n## Experience Section Formatting\n\n### Standard Format\n```\nCOMPANY NAME | City, ST\nJob Title | Month Year - Month Year\n\n• Achievement bullet with metrics and results\n• Achievement bullet with metrics and results\n• Achievement bullet with metrics and results\n```\n\n### Alternative Format\n```\nJob Title\nCOMPANY NAME, City, ST                    Month Year - Month Year\n\n• Achievement bullet with metrics and results\n• Achievement bullet with metrics and results\n```\n\n### Date Formatting\n- **Consistent format:** Use same format throughout\n- **Recommended:** Month Year (Jan 2020 - Present)\n- **Also acceptable:** MM\u002FYYYY (01\u002F2020 - Present)\n- **Avoid:** Full dates (January 15, 2020)\n\n### Bullet Point Guidelines\n- **Length:** 1-2 lines each\n- **Format:** Start with action verb, end with result\n- **Quantity:** 3-6 bullets per role (more for recent, fewer for old)\n- **Symbol:** Use standard bullets (•, -, *)\n\n\n## Skills Section Formatting\n\n### Option 1: Simple List\n```\nSKILLS\nPython, JavaScript, SQL, React, Node.js, AWS, Docker, Git, Agile, JIRA\n```\n\n### Option 2: Categorized\n```\nTECHNICAL SKILLS\nLanguages: Python, JavaScript, TypeScript, SQL\nFrameworks: React, Node.js, Django, Flask\nTools: AWS, Docker, Kubernetes, Git, Jenkins\n```\n\n### Option 3: Columns (Careful with ATS)\n```\nSKILLS\nLanguages        Frameworks       Tools\nPython           React            AWS\nJavaScript       Node.js          Docker\nSQL              Django           Git\n```\n\n**Note:** Multi-column layouts may cause ATS issues. Test before using.\n\n\n## Education Section Formatting\n\n### Standard Format\n```\nEDUCATION\nBachelor of Science in Computer Science\nUniversity of California, Berkeley | 2018\nGPA: 3.8\u002F4.0 (include if 3.5+)\n```\n\n### With Honors\u002FDetails\n```\nEDUCATION\nMBA, Finance & Strategy | Stanford Graduate School of Business | 2020\n• Graduated with Distinction\n• Relevant Coursework: Corporate Finance, M&A Strategy\n```\n\n\n## Visual Hierarchy Principles\n\n### Hierarchy Order\n1. **Name** - Largest, most prominent\n2. **Section Headers** - Clear divisions\n3. **Job Titles\u002FCompany Names** - Easy to scan\n4. **Bullet Points** - The details\n\n### Creating Hierarchy\n- Use font SIZE to create levels\n- Use **BOLD** for emphasis (names, titles, headers)\n- Use CAPS for section headers\n- Use consistent spacing to separate sections\n\n\n## White Space Management\n\n### Good White Space:\n- Between sections (clear separation)\n- After headings (visual breathing room)\n- Between bullets (don't cram)\n- Around margins (frame the content)\n\n### Bad White Space:\n- Huge gaps between sections\n- Inconsistent spacing\n- Half-empty pages\n- Excessive margins eating space\n\n\n## Common Formatting Mistakes\n\n### Mistake 1: Wall of Text\n**Problem:** Dense paragraphs with no bullets\n**Solution:** Use bullet points, keep paragraphs short\n\n### Mistake 2: Inconsistent Formatting\n**Problem:** Different fonts, sizes, or styles throughout\n**Solution:** Pick one format and stick to it\n\n### Mistake 3: Trying to Be Creative\n**Problem:** Fancy designs that break ATS\n**Solution:** Save creativity for portfolio, not resume\n\n### Mistake 4: Too Much Information\n**Problem:** Cramming everything onto one page\n**Solution:** Edit ruthlessly, prioritize relevance\n\n### Mistake 5: Not Enough Information\n**Problem:** Half-page resume with massive margins\n**Solution:** Add detail, reduce margins (to 0.5\")\n\n\n## File Format Guidelines\n\n### For Online Applications\n- **.docx** - Best for ATS parsing\n- **.pdf** - Good if created from Word (not scanned)\n\n### For Email\u002FDirect Send\n- **.pdf** - Preserves formatting\n\n### File Naming\n```\nFirstName_LastName_Resume.pdf\nJohnSmith_Resume_ProductManager.pdf\n```\n\n**Avoid:**\n- resume_final_v2_updated_FINAL.docx\n- resume (1).pdf\n- Untitled document.docx\n\n\n## Current Issues\n- [ ] [Issue 1]\n- [ ] [Issue 2]\n- [ ] [Issue 3]\n\n## Before\u002FAfter Preview\n\n### Before:\n[Description or example of current formatting]\n\n### After:\n[Description or example of improved formatting]\n\n\n## Quick Formatting Checklist\n\nBefore submitting any resume:\n- ✅ One page (or two if warranted)\n- ✅ Standard font (10-12pt body)\n- ✅ Consistent formatting throughout\n- ✅ Clear section headers\n- ✅ Appropriate white space\n- ✅ No tables, text boxes, or columns\n- ✅ Contact info in body (not header)\n- ✅ Saved as .docx or .pdf\n- ✅ Proper file name\n- ✅ Proofread for consistency\n\n> **Split from:** original 1930-line file. Partner skill: `ats-keyword-strategy` for keyword optimization, quantification metrics, and resume tailoring.\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"version":26},"gentleman-programming","1.0","main","5dc86f90a5cbe45db3acd917825461b3ed6937fb","config\u002F.config\u002Fopencode\u002Fskills\u002Fresume-ats-optimizer",0,"https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles","https:\u002F\u002Fgithub.com\u002Fdavidcoachdev","🌐 Apasionado por crear soluciones web escalables y eficientes. \r\n🧑‍🏫 Coach Dev.\r\n💻 Frontend Dev. \r\n🎚️Backend Dev.\r\n📊 Agile\u002FScrum.\r\n🚀100% remoto.","2026-08-26 07:28:05",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add davidcoachdev\u002Fdcfiles --skill \"Resume ATS Optimizer\"",{"tool":41,"command":42},"bunx","bunx skills add davidcoachdev\u002Fdcfiles --skill \"Resume ATS Optimizer\"",{"tool":44,"command":45},"pnpm","pnpm dlx skills add davidcoachdev\u002Fdcfiles --skill \"Resume ATS Optimizer\"","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fopencode\u002Fskills\u002Fresume-ats-optimizer\u002FSKILL.md",true,[49,55],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},".skill-meta.json","REFERENCE","参考文档",426,"https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fopencode\u002Fskills\u002Fresume-ats-optimizer\u002F.skill-meta.json",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"README.md",431,"https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fopencode\u002Fskills\u002Fresume-ats-optimizer\u002FREADME.md",[60,67,74,81,89,96],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7740FETMZY1VTYAEFY1TWY7","zustand-5","Zustand 5 state management patterns. Trigger: When managing React state with Zustand.","https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fopencode\u002Fskills\u002Fzustand-5\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M773ZZM9V68SA1AKP4WF4J29","zod-4","Zod 4 schema validation patterns. Trigger: When using Zod for validation - breaking changes from v3.","https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fopencode\u002Fskills\u002Fzod-4\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M773ZJFR90CQAY0N9QR40QVP","x-bookmark-quote-posts","Workflow para revisar bookmarks de X\u002FTwitter y convertirlos en drafts de quote posts. Accede a la sección de bookmarks vía browser headless, extrae posts recientes, y genera drafts con voz personal del usuario. No publica ni muta X — solo genera contenido para revisión. Trigger: X bookmarks, Twitter bookmarks, quote posts, bookmark automation, crear quote posts, revisar bookmarks, growth content X.","https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fopencode\u002Fskills\u002Fx-bookmark-quote-posts\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M773Z2RGV3786FV310SDB0YD","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","MIT","https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fopencode\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M773YJH3KDSW467CSS63CSRJ","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fopencode\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M773Y3S3H2CPRK5S8YFHWB5C","work-unit-commits","Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.","https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fopencode\u002Fskills\u002Fwork-unit-commits\u002FSKILL.md",[],[]]