[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6P0Q6R4NKRY6VWPCQZD368G":3,"skill-same:01M6P0Q6R4NKRY6VWPCQZD368G":63},{"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":23,"publishedAt":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":14,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":46,"ownerDescription":47,"updatedAt":48,"install":49,"resources":62},"01M6P0Q6R4NKRY6VWPCQZD368G","resume-ats-optimizer",null,"Optimize resumes for Applicant Tracking Systems, check ATS compatibility, and analyze keyword match","shreyasbhakta\u002FCareerReboot","shreyasbhakta","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F55823227?v=4","01M6P0DV5QY0C5FEMNYKBD4YFJ","Shreyas Bhakta","01M6P0DV9YG9JPTG0VVGG866PP",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fshreyasbhakta\u002FCareerReboot\u002Fblob\u002Fmain\u002Fskills\u002Fresume-skills\u002Fskills\u002Fresume-ats-optimizer\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35],"resume ats optimizer","resume","optimizer","ats","analyze","check","tracking","compatibility","optimize","systems","match","for","2026-11-10 10:12:30",false,"---\nname: resume-ats-optimizer\ndescription: Optimize resumes for Applicant Tracking Systems, check ATS compatibility, and analyze keyword match\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- Mentions keywords like: \"ATS\", \"not getting interviews\", \"resume not working\", \"optimize resume\", \"keyword optimization\"\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- Extract and analyze keywords against job descriptions\n- Identify formatting issues that break ATS parsers\n- Calculate match scores between resume and job postings\n- Suggest keyword additions and placements\n- Generate ATS-friendly formatting recommendations\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## Keyword Optimization Process\n\n### Step 1: Extract Job Description Keywords\n\nIdentify three types of keywords:\n\n**Hard Skills (Technical)**\n- Programming languages (Python, Java, SQL)\n- Tools and platforms (Salesforce, AWS, Excel)\n- Certifications (PMP, CPA, CFA)\n- Methodologies (Agile, Six Sigma, SDLC)\n\n**Soft Skills**\n- Leadership, collaboration, communication\n- Problem-solving, analytical thinking\n- Project management, stakeholder management\n\n**Industry Terms**\n- B2B, SaaS, e-commerce\n- Enterprise, SMB, mid-market\n- ARR, MRR, churn rate\n\n### Step 2: Match Analysis\n\nFor each keyword in job description:\n1. Check if exact phrase appears in resume\n2. Check for synonyms or variations\n3. Count frequency of mention\n4. Note location (summary, experience, skills)\n\n### Step 3: Calculate Match Score\n\n```\nMatch Score = (Keywords Matched \u002F Total Required Keywords) × 100\n\nExample:\nJob has 20 required keywords\nYour resume has 15 of them\nMatch Score = 75%\n\nTarget: 80%+ for strong match\n```\n\n### Step 4: Keyword Placement Strategy\n\n**Priority 1: Professional Summary (Top of Resume)**\n- Include 5-8 most important keywords\n- Use naturally in 3-4 sentence paragraph\n- Example: \"Data Scientist with 5+ years using Python, SQL, and machine learning to drive business insights...\"\n\n**Priority 2: Skills Section**\n- List keywords explicitly\n- Group by category if needed\n- Use exact phrasing from job description\n\n**Priority 3: Experience Bullets**\n- Incorporate keywords into achievement statements\n- Don't force keywords unnaturally\n- Use variations throughout\n\n**Keyword Density Guidelines:**\n- Critical keywords: Appear 2-4 times throughout resume\n- Important keywords: Appear 1-2 times\n- Don't keyword stuff - keep it natural\n- Vary phrasing (e.g., \"led team\" and \"team leadership\")\n\n## Analysis Output Format\n\nWhen analyzing a resume, provide this structured report:\n\n```markdown\n# ATS COMPATIBILITY REPORT\n\n## Overall Score: [X]\u002F100\n\n### File Format Check ✅\u002F❌\n- Format: [DOCX\u002FPDF]\n- Text extraction: [Success\u002FFailed]\n- File size: [X KB\u002FMB]\n\n### Formatting Issues\n✅ No tables or columns detected\n❌ Contact info in header (move to body)\n⚠️  Two different font sizes in skills section\n\n### Keyword Analysis\n\nJOB REQUIREMENTS vs YOUR RESUME:\n\n**Critical Keywords (Must Have):**\n✅ Project Management - Found 3x\n✅ Agile\u002FScrum - Found 2x\n❌ Stakeholder Management - MISSING (mentioned 5x in JD)\n❌ Budget Management - MISSING (mentioned 3x in JD)\n\n**Important Keywords:**\n✅ Cross-functional teams - Found 1x\n⚠️  \"Risk management\" - You have \"risk mitigation\" (close but not exact match)\n✅ Process improvement - Found 2x\n\n**Match Score: 65%**\nTarget: 80%+ recommended\n\n### Recommended Changes\n\n**1. Add Missing Keywords:**\n\nIn Professional Summary, change:\n\"Experienced project manager with proven track record...\"\n\nTo:\n\"Experienced project manager with proven track record in stakeholder management and budget oversight...\"\n\nIn Experience section, add bullet:\n\"Managed stakeholder communication across 3 departments and executive leadership team\"\n\"Directed budget management for $2.5M project portfolio\"\n\n**2. Fix Formatting:**\n- Move contact information from header to body of resume\n- Make all skill section items same font size (currently 10pt and 11pt mixed)\n\n**3. Strengthen Existing Keywords:**\nChange \"risk mitigation\" to \"risk management\" for exact match\n\n### Estimated New Match Score: 85%\n```\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","# 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- Mentions keywords like: \"ATS\", \"not getting interviews\", \"resume not working\", \"optimize resume\", \"keyword optimization\"\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- Extract and analyze keywords against job descriptions\n- Identify formatting issues that break ATS parsers\n- Calculate match scores between resume and job postings\n- Suggest keyword additions and placements\n- Generate ATS-friendly formatting recommendations\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## Keyword Optimization Process\n\n### Step 1: Extract Job Description Keywords\n\nIdentify three types of keywords:\n\n**Hard Skills (Technical)**\n- Programming languages (Python, Java, SQL)\n- Tools and platforms (Salesforce, AWS, Excel)\n- Certifications (PMP, CPA, CFA)\n- Methodologies (Agile, Six Sigma, SDLC)\n\n**Soft Skills**\n- Leadership, collaboration, communication\n- Problem-solving, analytical thinking\n- Project management, stakeholder management\n\n**Industry Terms**\n- B2B, SaaS, e-commerce\n- Enterprise, SMB, mid-market\n- ARR, MRR, churn rate\n\n### Step 2: Match Analysis\n\nFor each keyword in job description:\n1. Check if exact phrase appears in resume\n2. Check for synonyms or variations\n3. Count frequency of mention\n4. Note location (summary, experience, skills)\n\n### Step 3: Calculate Match Score\n\n```\nMatch Score = (Keywords Matched \u002F Total Required Keywords) × 100\n\nExample:\nJob has 20 required keywords\nYour resume has 15 of them\nMatch Score = 75%\n\nTarget: 80%+ for strong match\n```\n\n### Step 4: Keyword Placement Strategy\n\n**Priority 1: Professional Summary (Top of Resume)**\n- Include 5-8 most important keywords\n- Use naturally in 3-4 sentence paragraph\n- Example: \"Data Scientist with 5+ years using Python, SQL, and machine learning to drive business insights...\"\n\n**Priority 2: Skills Section**\n- List keywords explicitly\n- Group by category if needed\n- Use exact phrasing from job description\n\n**Priority 3: Experience Bullets**\n- Incorporate keywords into achievement statements\n- Don't force keywords unnaturally\n- Use variations throughout\n\n**Keyword Density Guidelines:**\n- Critical keywords: Appear 2-4 times throughout resume\n- Important keywords: Appear 1-2 times\n- Don't keyword stuff - keep it natural\n- Vary phrasing (e.g., \"led team\" and \"team leadership\")\n\n## Analysis Output Format\n\nWhen analyzing a resume, provide this structured report:\n\n```markdown\n# ATS COMPATIBILITY REPORT\n\n## Overall Score: [X]\u002F100\n\n### File Format Check ✅\u002F❌\n- Format: [DOCX\u002FPDF]\n- Text extraction: [Success\u002FFailed]\n- File size: [X KB\u002FMB]\n\n### Formatting Issues\n✅ No tables or columns detected\n❌ Contact info in header (move to body)\n⚠️  Two different font sizes in skills section\n\n### Keyword Analysis\n\nJOB REQUIREMENTS vs YOUR RESUME:\n\n**Critical Keywords (Must Have):**\n✅ Project Management - Found 3x\n✅ Agile\u002FScrum - Found 2x\n❌ Stakeholder Management - MISSING (mentioned 5x in JD)\n❌ Budget Management - MISSING (mentioned 3x in JD)\n\n**Important Keywords:**\n✅ Cross-functional teams - Found 1x\n⚠️  \"Risk management\" - You have \"risk mitigation\" (close but not exact match)\n✅ Process improvement - Found 2x\n\n**Match Score: 65%**\nTarget: 80%+ recommended\n\n### Recommended Changes\n\n**1. Add Missing Keywords:**\n\nIn Professional Summary, change:\n\"Experienced project manager with proven track record...\"\n\nTo:\n\"Experienced project manager with proven track record in stakeholder management and budget oversight...\"\n\nIn Experience section, add bullet:\n\"Managed stakeholder communication across 3 departments and executive leadership team\"\n\"Directed budget management for $2.5M project portfolio\"\n\n**2. Fix Formatting:**\n- Move contact information from header to body of resume\n- Make all skill section items same font size (currently 10pt and 11pt mixed)\n\n**3. Strengthen Existing Keywords:**\nChange \"risk mitigation\" to \"risk management\" for exact match\n\n### Estimated New Match Score: 85%\n```\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",{"name":5,"description":7},"main","466b9f58403b6b473023097f5b9f3f094ebeb493","skills\u002Fresume-skills\u002Fskills\u002Fresume-ats-optimizer","https:\u002F\u002Fgithub.com\u002Fshreyasbhakta\u002FCareerReboot","https:\u002F\u002Fgithub.com\u002Fshreyasbhakta","shreyasbhakta.dev","Software Engineer | Backend & Distributed Systems | Java, Spring Boot, Kafka, Python | Agentic AI, LangGraph, RAG | Ex-Vymo, Ex-SIXT | Cybersecurity Enthusiast","2026-10-17 04:01:42",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add shreyasbhakta\u002FCareerReboot --skill resume-ats-optimizer",{"tool":55,"command":56},"bunx","bunx skills add shreyasbhakta\u002FCareerReboot --skill resume-ats-optimizer",{"tool":58,"command":59},"pnpm","pnpm dlx skills add shreyasbhakta\u002FCareerReboot --skill resume-ats-optimizer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshreyasbhakta\u002FCareerReboot\u002Fblob\u002Fmain\u002Fskills\u002Fresume-skills\u002Fskills\u002Fresume-ats-optimizer\u002FSKILL.md",true,[],[64,81,103,118,128,139],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":71,"publishedAt":36},"01M6P0SGCMXDZ5DH19S9RS4PZZ","tech-resume-optimizer","Optimize resumes for software engineering, PM, and technical roles","https:\u002F\u002Fgithub.com\u002Fshreyasbhakta\u002FCareerReboot\u002Fblob\u002Fmain\u002Fskills\u002Fresume-skills\u002Fskills\u002Ftech-resume-optimizer\u002FSKILL.md",[70],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[72,25,73,26,74,75,35,76,77,32,78,79,80],"tech resume optimizer","resume optimizer","tech","software engineering","engineering","technical","pm","roles","software",{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":92,"publishedAt":36},"01M6P0SC37HWQ8CTWA37SVPAA3","salary-negotiation-prep","Research market rates, build negotiation strategy, and create counter-offer scripts","https:\u002F\u002Fgithub.com\u002Fshreyasbhakta\u002FCareerReboot\u002Fblob\u002Fmain\u002Fskills\u002Fresume-skills\u002Fskills\u002Fsalary-negotiation-prep\u002FSKILL.md",[87],{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[93,94,95,96,97,98,99,100,101,102],"negotiation prep","prep","negotiation","salary negotiation prep","build","scripts","Market","research","create","strategy",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":110,"publishedAt":36},"01M6P0RSXGGR789TX42ZXNR09N","resume-version-manager","Track different resume versions, maintain master resume, manage tailored versions","https:\u002F\u002Fgithub.com\u002Fshreyasbhakta\u002FCareerReboot\u002Fblob\u002Fmain\u002Fskills\u002Fresume-skills\u002Fskills\u002Fresume-version-manager\u002FSKILL.md",[109],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[111,25,112,113,114,115,116,117],"manager","version","resume version manager","master","manage","maintain","track",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":125,"publishedAt":36},"01M6P0RK6FX16FYCC01T2HA2MA","resume-tailor","Customize resume for specific job postings while maintaining truthfulness","https:\u002F\u002Fgithub.com\u002Fshreyasbhakta\u002FCareerReboot\u002Fblob\u002Fmain\u002Fskills\u002Fresume-skills\u002Fskills\u002Fresume-tailor\u002FSKILL.md",[124],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[25,126,35,127],"resume tailor","customize",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":135,"publishedAt":36},"01M6P0R57S7ASRV6VAYQ4K2J9Y","resume-section-builder","Create targeted resume sections optimized for different experience levels and roles","https:\u002F\u002Fgithub.com\u002Fshreyasbhakta\u002FCareerReboot\u002Fblob\u002Fmain\u002Fskills\u002Fresume-skills\u002Fskills\u002Fresume-section-builder\u002FSKILL.md",[134],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[136,137,25,138,101,79,35],"section","builder","resume section builder",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":146,"publishedAt":36},"01M6P0R0TVRRDSTTM047HWXNCD","resume-quantifier","Find opportunities to add metrics and estimate numbers when exact data unavailable","https:\u002F\u002Fgithub.com\u002Fshreyasbhakta\u002FCareerReboot\u002Fblob\u002Fmain\u002Fskills\u002Fresume-skills\u002Fskills\u002Fresume-quantifier\u002FSKILL.md",[145],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[25,147,148,149,150,151,152],"resume quantifier","metrics","data","find","add","estimate"]