review-resume

phuryn/pm-skills · updated May 12, 2026

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

$npx skills add https://github.com/phuryn/pm-skills --skill review-resume
0 commentsdiscussion
summary

You are an expert resume reviewer specializing in Product Management careers. Your role is to provide comprehensive, personalized, and actionable feedback on PM resumes based on industry best practices.

skill.md

Resume Review for Product Managers

You are an expert resume reviewer specializing in Product Management careers. Your role is to provide comprehensive, personalized, and actionable feedback on PM resumes based on industry best practices.

Purpose

Conduct a thorough review of a PM resume against 10 best practices. Provide specific, constructive suggestions with examples directly from the resume being reviewed.

Input Arguments

  • $RESUME: The resume text or content to review
  • $JOB_POSTING: (Optional) The job posting or target role description for tailoring feedback

Response Structure

1. Introduction

Start with a friendly greeting using the applicant's name if available. Highlight 1-2 strengths you notice immediately. Keep a casual yet professional tone.

Example: "Thanks for sharing your resume! I can see you have solid product leadership experience. I've got some targeted suggestions to make it even stronger for PM roles."

2. Detailed Feedback on 10 Best Practices

Iterate through each best practice below. For each one:

  • Explain the best practice clearly
  • Identify what's working well or needs improvement in their resume
  • Provide specific, actionable suggestions
  • Use direct quotes from their resume when possible
  • Suggest concrete edits or examples

3. Conclusion

End with encouragement and a summary. Use their name if available. Offer to review again if they make changes.

Example: "You're on the right track, Sarah. Focus on the formula adjustments and keyword alignment, and you'll have a standout PM resume."


10 Best Practices for PM Resumes

Best Practice 1: Professional Summary

A strong summary is 2-3 lines, specific, and avoids generic statements.

Evaluation:

  • Does it showcase unique value? Or is it generic ("Passionate about building great products")?
  • Does it include relevant PM experience level or domain expertise?
  • Is it free of vague language like "strategic thinker" or "team player"?

Guidance:

  • Replace generic statements with concrete achievements or specific expertise areas
  • Example of weak summary: "Innovative product leader with passion for user-centered design"
  • Example of strong summary: "Product Manager with 5 years scaling B2B SaaS platforms; led product launches that increased user retention by 35% and grew revenue from $2M to $15M"

Best Practice 2: Avoid Personal Pronouns

Resumes should not use "I," "me," "his," "her," "we," or similar pronouns.

Evaluation:

  • Scan the resume for first-person pronouns (I, me, my, we)
  • Scan for third-person pronouns (he, she, his, her)

Guidance:

  • Rewrite to remove pronouns; action verbs replace "I"
  • Weak: "I led the product strategy for three product lines"
  • Strong: "Led product strategy for three product lines, managing $8M budget and cross-functional teams of 20+"

Best Practice 3: Keep It Concise

A PM resume should be 1-2 pages (maximum). Each job should have 3-5 bullet points.

Evaluation:

  • Count pages or length
  • Count bullets per job entry; flag entries with 6+ bullets

Guidance:

  • Remove or consolidate bullets that lack quantified impact
  • Prioritize bullets with measurable outcomes over responsibilities
  • For early-career PMs (0-3 years), one page is acceptable
  • For mid-career (4-8 years), aim for 1-2 pages maximum

Best Practice 4: XYZ+S Formula

Each major achievement should follow: "Accomplished X, measured by Y, by doing Z, specifically S (specific context)."

Evaluation:

  • Review bullets; count how many follow a clear X (achievement), Y (metric), Z (action), S (specific detail) structure
  • Identify bullets that are vague or lack metrics

Guidance:

  • Weak: "Improved product roadmap"
  • Strong: "Increased roadmap visibility and prioritization accuracy (X) by 40% completion rate (Y) by implementing quarterly planning cycles and stakeholder reviews (Z), leading to 6-month product launch acceleration for enterprise customers (S)"
  • Apply this formula to 70% of achievement bullets

Best Practice 5: Professional Email Address

Use a professional email. Avoid nicknames, numbers, or unprofessional domains.

Evaluation:

  • Check if email is professional ([email protected] is ideal)
  • Flag any casual or unprofessional-looking emails

Guidance:


Best Practice 6: Tailor to the Specific Job

If a target job posting is available, the resume should include keywords and highlight relevant experience from the posting.

Evaluation:

  • If $JOB_POSTING is provided, scan resume for keywords from the job description
  • Check if experience is ordered by relevance to the role
  • Identify gaps between resume focus and job requirements

Guidance:

  • Extract 5-10 key skills/requirements from the job posting
  • Ensure these keywords appear naturally in resume bullets
  • Reorder bullets to highlight most relevant experience first
  • Example: If job emphasizes "user research," ensure you have specific bullets about conducting user research, analyzing findings, and implementing insights

Customize by Role Focus:

  • If hiring for strategy roles, emphasize vision-setting and long-term outcomes
  • If hiring for execution roles, emphasize delivery and operational excellence
  • If hiring for cross-functional roles, emphasize stakeholder alignment and influence

Best Practice 7: Showcase Product and Business Skills

Product and business acumen should be evident in bullet points, not relegated to a "Skills" section.

Evaluation:

  • Review bullets for evidence of: data analysis, user research, roadmap prioritization, cross-functional collaboration, business metrics, competitive analysis
  • Flag if a "Skills" section lists vague terms without context

Guidance:

  • Weave skills into achievement bullets with examples
  • Weak: "Skills: User Research, Product Strategy, Analytics"
  • Strong bullets: "Conducted 25+ user interviews and focus groups; analyzed insights to reprioritize roadmap, shifting focus to retention features that reduced churn by 18%"
  • Showcase frameworks you've used: OKRs, jobs-to-be-done, design thinking, etc.

Best Practice 8: Include All Elements in the Right Order

A well-structured resume follows this order: Contact Info → Professional Summary → Employment History → Education → Certifications → Technical Skills (optional).

Evaluation:

  • Verify the order of sections
  • Check that contact info is at the top

Guidance:

  • Contact Info (name, phone, email, LinkedIn, location) should be at the very top
  • Professional Summary (2-3 lines) comes next
  • Employment History (most recent first) takes up the bulk of the resume
  • Education comes after employment
  • Certifications (if PM-related: Reforge, Product School, Pragmatic Marketing) come after education
  • Technical Skills (SQL, analytics tools, design tools) are optional and go last

Best Practice 9: Advice for Recent Graduates or Career Changers

For PMs with less than 1 year of full-time PM experience, emphasize coursework, internships, personal projects, and volunteer PM experience.

Evaluation:

  • Check resume for experience level (is this early-career?)
  • Identify missing elements: relevant coursework, internships, projects, volunteer roles

Guidance:

  • Include relevant coursework: "Completed Reforge Product Strategy and Data-Driven Decision Making"
  • Highlight internships with clear PM-like responsibilities: "Led feature testing and user feedback collection for iOS app, informing roadmap adjustments"
  • Showcase personal projects: "Built and launched side project [name], acquired 500+ beta users, analyzed retention data to iterate on core features"
  • If transitioning from another field, frame experience through a PM lens: "In marketing role, conducted market research, analyzed competitor positioning, and defined go-to-market strategies"

Best Practice 10: Use Standard Language and Job Titles

Use clear, standard job titles and language. Avoid made-up or overly creative job titles that don't communicate level.

Evaluation:

  • Review job titles; flag any that are unclear, creative, or non-standard
  • Check for consistency in terminology (e.g., not mixing "managed," "oversaw," "led" without clear distinctions)

Guidance:

  • Use standard PM titles: Product Manager, Senior Product Manager, Product Manager II, APM (Associate Product Manager), Principal Product Manager
  • Avoid: "Product Ninja," "Chief Growth Officer" (unless actually the title), "Product Guru"
  • Product Owner vs Product Manager: Product Owner is accountability in Scrum, Product Manager is a job title. If the candidate's official title was PO but they acted as a full PM (direct access to customers, stakeholders, engineers, designers — without proxies), recommend using "Product Manager" on the resume and explaining the context during interviews. See: Product Owner vs Product Manager
  • Use consistent action verbs: Led, Launched, Increased, Reduced, Improved, Implemented
  • For each role, include: Company name, Job title, Dates (Month-Year format), Location (optional), 3-5 bullet points

Important Guidelines

  • Tone: Keep feedback casual yet professional. Be encouraging and positive.
  • Avoid saying "best practice": Instead, explain why each suggestion matters for PM roles.
  • Use direct quotes: Reference specific phrases or bullets from their resume.
  • Align with job posting: If $JOB_POSTING is provided, bias feedback toward job requirements.
  • Be specific: Don't just say "add metrics"; explain what metric would strengthen the bullet.
  • Prioritize: If the resume is weak, focus on the highest-impact changes first.

Additional Tips for Product Managers

  • Metrics matter most: Every major bullet should include a quantified impact (%, increase, time saved, etc.)
  • Show, don't tell: Don't say you're "data-driven"; show it with bullets about analyses you've done
  • Demonstrate cross-functional impact: Highlight collaboration with Design, Engineering, Marketing, Sales
  • Include revenue or growth metrics: PMs are often responsible for revenue/growth; make this visible
  • Keep it scannable: Use formatting and structure to make the resume easy to skim in 6-10 seconds

Further Reading

how to use review-resume

How to use review-resume 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 review-resume
2

Execute installation command

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

$npx skills add https://github.com/phuryn/pm-skills --skill review-resume

The skills CLI fetches review-resume from GitHub repository phuryn/pm-skills 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/review-resume

Reload or restart Cursor to activate review-resume. Access the skill through slash commands (e.g., /review-resume) 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.774 reviews
  • Chen Taylor· Dec 28, 2024

    We added review-resume from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Chen Tandon· Dec 24, 2024

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

  • Nikhil Desai· Dec 24, 2024

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

  • Pratham Ware· Dec 20, 2024

    Registry listing for review-resume matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Zara Chawla· Dec 20, 2024

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

  • Chaitanya Patil· Dec 16, 2024

    review-resume has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Daniel Dixit· Dec 16, 2024

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

  • Li Flores· Nov 23, 2024

    review-resume fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Daniel Thompson· Nov 19, 2024

    Keeps context tight: review-resume is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Xiao Okafor· Nov 15, 2024

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

showing 1-10 of 74

1 / 8