resume-ats-optimizer

paramchoudhary/resumeskills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/paramchoudhary/resumeskills --skill resume-ats-optimizer
0 commentsdiscussion
summary

Resume optimization for Applicant Tracking Systems with keyword matching and compatibility analysis.

  • Parses resumes for ATS compatibility, identifies formatting issues (tables, headers/footers, non-standard fonts), and flags file format problems that break automated screening
  • Extracts and analyzes keywords from job descriptions across hard skills, soft skills, and industry terms, then calculates match scores between resume and posting
  • Provides structured compatibility reports with sp
skill.md

Resume ATS Optimizer

When to Use This Skill

Use this skill when the user wants to:

  • Optimize their resume for Applicant Tracking Systems (ATS)
  • Check if their resume will pass automated screening
  • Understand why their applications aren't getting responses
  • Mentions keywords like: "ATS", "not getting interviews", "resume not working", "optimize resume", "keyword optimization"

Also use when the user provides a resume file and mentions they're applying to jobs.

Core Capabilities

  • Parse resume and test ATS compatibility
  • Extract and analyze keywords against job descriptions
  • Identify formatting issues that break ATS parsers
  • Calculate match scores between resume and job postings
  • Suggest keyword additions and placements
  • Generate ATS-friendly formatting recommendations

The ATS Problem

75% of resumes are rejected by Applicant Tracking Systems before a human ever sees them. Companies use ATS to:

  • Filter out unqualified candidates automatically
  • Search for specific keywords from job requirements
  • Parse resumes into structured data
  • Rank candidates by keyword match percentage

Common reasons resumes fail ATS:

  1. Poor formatting (tables, columns, headers/footers)
  2. Missing keywords from job description
  3. Inconsistent section headers
  4. Non-standard fonts or special characters
  5. Text embedded in images
  6. Incorrect file format

ATS Compatibility Checklist

File Format

  • ✅ Use .docx or .pdf (not .pages, .odt)
  • ✅ PDF must be text-based, not scanned image
  • ✅ File name: "FirstName_LastName_Resume.pdf"

Font & Formatting

  • ✅ Standard fonts: Arial, Calibri, Georgia, Times New Roman
  • ✅ Font size: 10-12pt for body, 14-16pt for headers
  • ✅ No text boxes, tables, or columns
  • ✅ No headers/footers (put contact info in body)
  • ✅ No images, graphics, or charts
  • ✅ Consistent date formats (MM/YYYY)
  • ✅ Standard bullet points (•, -, *)

Section Headers

Use standard, recognizable headers:

  • ✅ "Professional Experience" or "Work Experience" (not "Where I've Been")
  • ✅ "Education" (not "Academic Background")
  • ✅ "Skills" (not "Core Competencies")
  • ✅ "Summary" or "Professional Summary"

Contact Information

John Smith
[email protected] | (555) 123-4567 | LinkedIn: linkedin.com/in/johnsmith
San Francisco, CA

NOT in header/footer, and avoid:

  • ❌ Tables for contact info
  • ❌ Special characters in email
  • ❌ Multiple phone numbers
  • ❌ Full mailing address (city/state is enough)

Keyword Optimization Process

Step 1: Extract Job Description Keywords

Identify three types of keywords:

Hard Skills (Technical)

  • Programming languages (Python, Java, SQL)
  • Tools and platforms (Salesforce, AWS, Excel)
  • Certifications (PMP, CPA, CFA)
  • Methodologies (Agile, Six Sigma, SDLC)

Soft Skills

  • Leadership, collaboration, communication
  • Problem-solving, analytical thinking
  • Project management, stakeholder management

Industry Terms

  • B2B, SaaS, e-commerce
  • Enterprise, SMB, mid-market
  • ARR, MRR, churn rate

Step 2: Match Analysis

For each keyword in job description:

  1. Check if exact phrase appears in resume
  2. Check for synonyms or variations
  3. Count frequency of mention
  4. Note location (summary, experience, skills)

Step 3: Calculate Match Score

Match Score = (Keywords Matched / Total Required Keywords) × 100

Example:
Job has 20 required keywords
Your resume has 15 of them
Match Score = 75%

Target: 80%+ for strong match

Step 4: Keyword Placement Strategy

Priority 1: Professional Summary (Top of Resume)

  • Include 5-8 most important keywords
  • Use naturally in 3-4 sentence paragraph
  • Example: "Data Scientist with 5+ years using Python, SQL, and machine learning to drive business insights..."

Priority 2: Skills Section

  • List keywords explicitly
  • Group by category if needed
  • Use exact phrasing from job description

Priority 3: Experience Bullets

  • Incorporate keywords into achievement statements
  • Don't force keywords unnaturally
  • Use variations throughout

Keyword Density Guidelines:

  • Critical keywords: Appear 2-4 times throughout resume
  • Important keywords: Appear 1-2 times
  • Don't keyword stuff - keep it natural
  • Vary phrasing (e.g., "led team" and "team leadership")

Analysis Output Format

When analyzing a resume, provide this structured report:

# ATS COMPATIBILITY REPORT

## Overall Score: [X]/100

### File Format Check ✅/❌
- Format: [DOCX/PDF]
- Text extraction: [Success/Failed]
- File size: [X KB/MB]

### Formatting Issues
✅ No tables or columns detected
❌ Contact info in header (move to body)
⚠️  Two different font sizes in skills section

### Keyword Analysis

JOB REQUIREMENTS vs YOUR RESUME:

**Critical Keywords (Must Have):**
✅ Project Management - Found 3x
✅ Agile/Scrum - Found 2x
❌ Stakeholder Management - MISSING (mentioned 5x in JD)
❌ Budget Management - MISSING (mentioned 3x in JD)

**Important Keywords:**
✅ Cross-functional teams - Found 1x
⚠️  "Risk management" - You have "risk mitigation" (close but not exact match)
✅ Process improvement - Found 2x

**Match Score: 65%**
Target: 80%+ recommended

### Recommended Changes

**1. Add Missing Keywords:**

In Professional Summary, change:
"Experienced project manager with proven track record..."

To:
"Experienced project manager with proven track record in stakeholder management and budget oversight..."

In Experience section, add bullet:
"Managed stakeholder communication across 3 departments and executive leadership team"
"Directed budget management for $2.5M project portfolio"

**2. Fix Formatting:**
- Move contact information from header to body of resume
- Make all skill section items same font size (currently 10pt and 11pt mixed)

**3. Strengthen Existing Keywords:**
Change "risk mitigation" to "risk management" for exact match

### Estimated New Match Score: 85%

Common ATS Failure Patterns

Pattern 1: Creative Formatting

❌ PROBLEM:
[Two-column layout with graphics]
[Skill bars and proficiency charts]
[Text in colored boxes]

✅ SOLUTION:
- Single column layout
- Text-only skills list
- Simple bullet points

Pattern 2: Unconventional Section Names

❌ PROBLEM:
"My Journey" (instead of Experience)
"What I Bring to the Table" (instead of Skills)
"Academic Pursuits" (instead of Education)

✅ SOLUTION:
Use standard headers ATS recognizes

Pattern 3: Missing Keywords

❌ PROBLEM:
Job requires: "Python, SQL, Data Visualization"
Resume says: "Programming, databases, making charts"

✅ SOLUTION:
Use exact terminology from job description

Pattern 4: Keyword Stuffing

❌ PROBLEM:
Skills: Python, Python programming, Python developer, Python expert, Python specialist, Advanced Python...

✅ SOLUTION:
Skills: Python, SQL, JavaScript, React, Node.js
(Then incorporate naturally in bullets)

Industry-Specific Considerations

Tech Resumes

  • Emphasize programming languages and frameworks
  • Include GitHub, portfolio links in Skills section (not header)
  • Certifications and courses matter highly

Business/Finance

  • Focus on software proficiency (Excel, SAP, Salesforce)
  • Certifications critical (CPA, CFA, PMP)
  • Industry keywords (P&L, ROI, KPI)

Healthcare

  • Licenses and certifications required
  • Specific systems (Epic, Cerner, MEDITECH)
  • Compliance keywords (HIPAA, Joint Commission)

Marketing

  • Platform expertise (HubSpot, Salesforce, Google Analytics)
  • Channel keywords (SEO, PPC, email marketing)
  • Metrics and results-driven language

Edge Cases & Special Situations

Career Changers

  • Focus on transferable skills
  • Use keywords from TARGET industry, not just current
  • May need two resume versions for ATS

Recent Graduates

  • Education section becomes priority for keywords
  • Include relevant coursework, projects
  • Internships count as experience - use those keywords

Executive Level

  • ATS still matters for senior roles
  • Focus on strategic keywords
  • Include board experience, P&L size, team size

Gaps in Employment

  • Use years only (not months) if it helps
  • Include freelance/consulting with keywords
  • Volunteer work can include relevant keywords

Implementation Checklist

When helping user optimize for ATS:

  1. ✅ Scan current resume for ATS compatibility issues
  2. ✅ Analyze job description for required keywords
  3. ✅ Calculate current match score
  4. ✅ Identify specific missing keywords
  5. ✅ Suggest exact placements for new keywords
  6. ✅ Flag formatting problems
  7. ✅ Provide before/after examples
  8. ✅ Re-score after suggested changes
  9. ✅ Verify file format and naming
  10. ✅ Test with ATS simulator if possible

Success Metrics

After optimization, the resume should:

  • Score 80%+ match for target job descriptions
  • Pass ATS parsing test (all sections recognized)
  • Have zero formatting errors
  • Include all critical keywords 2-4x each
  • Read naturally (not keyword-stuffed)
  • Be ready to submit immediately
how to use resume-ats-optimizer

How to use resume-ats-optimizer on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add resume-ats-optimizer
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/paramchoudhary/resumeskills --skill resume-ats-optimizer

The skills CLI fetches resume-ats-optimizer from GitHub repository paramchoudhary/resumeskills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/resume-ats-optimizer

Reload or restart Cursor to activate resume-ats-optimizer. Access the skill through slash commands (e.g., /resume-ats-optimizer) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.663 reviews
  • Naina Verma· Dec 24, 2024

    I recommend resume-ats-optimizer for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Sofia Rao· Dec 20, 2024

    resume-ats-optimizer reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Pratham Ware· Dec 4, 2024

    I recommend resume-ats-optimizer for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Yash Thakker· Nov 23, 2024

    Useful defaults in resume-ats-optimizer — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Kabir Khan· Nov 15, 2024

    Useful defaults in resume-ats-optimizer — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • William Verma· Nov 11, 2024

    resume-ats-optimizer is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Naina Smith· Nov 7, 2024

    resume-ats-optimizer reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Kabir Haddad· Oct 26, 2024

    I recommend resume-ats-optimizer for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Dhruvi Jain· Oct 14, 2024

    resume-ats-optimizer is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Ishan Diallo· Oct 6, 2024

    resume-ats-optimizer is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

showing 1-10 of 63

1 / 7