Mmcp.market

review-resume skill

by phuryn·phuryn/pm-skills·27k stars·MIT

Comprehensive PM resume review and tailoring against 10 best practices including XYZ+S formula, keyword optimization, job-specific tailoring, and structure. Use when reviewing a PM resume, preparing for job applications, or improving resume impact.

A100/100content scan

Is the review-resume skill safe?

Clean: nothing in its files matched our rules. We read 1 file in the folder on 2026-09-28.

No findings.

Install the review-resume skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description.

git clone --depth 1 https://github.com/phuryn/pm-skills.git /tmp/pm-skills
mkdir -p ~/.claude/skills
cp -r /tmp/pm-skills/pm-toolkit/skills/review-resume ~/.claude/skills/review-resume
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

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 (firstname.lastname@domain.com is ideal)
  • Flag any casual or unprofessional-looking emails

Guidance:

  • If current email is unprofessional, create a Gmail account with your professional name
  • Use format: firstname.lastname@gmail.com or your custom domain
  • Avoid: randomnickname123@gmail.com, cutesurfer@yahoo.com

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:

More skills from phuryn/pm-skills

  • Aab-test-analysisAnalyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
  • Aanalyze-feature-requestsAnalyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.
  • Aansoff-matrixGenerate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.
  • Abeachhead-segmentIdentify the first beachhead market segment for a product launch. Evaluates segments against burning pain, willingness to pay, winnable market share, and referral potential. Use when choosing a first market, targeting an initial customer segment, or planning market entry strategy.
  • Abrainstorm-experiments-existingDesign experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.
  • Abrainstorm-experiments-newDesign lean startup experiments (pretotypes) for a new product. Creates XYZ hypotheses and suggests low-effort validation methods like landing pages, explainer videos, and pre-orders. Use when validating a new product idea, creating pretotypes, or testing market demand.
  • Abrainstorm-ideas-existingBrainstorm product ideas for an existing product using multi-perspective ideation from PM, Designer, and Engineer viewpoints. Use when generating new feature ideas, brainstorming solutions for an identified opportunity, or ideating with a product trio.
  • Abrainstorm-ideas-newBrainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation.
  • Abrainstorm-okrsBrainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
  • Abusiness-modelGenerate a Business Model Canvas with all 9 building blocks. Use when creating a business model, documenting how a business creates value, or analyzing an existing business model.
  • Acode-reviewReview code for actionable defects. Correctness is the core; performance and security are optional sub-cases of the same engine. Anchors on agreements between participants across a boundary, forces a violating execution, and refutes every candidate before reporting. Use when asked to review changes, find bugs, audit a codebase, or check whether a fix is safe.
  • Acohort-analysisPerform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.

All agent skills → · MCP servers