Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
phuryn avatar

Review Resume

  • 2k installs
  • 24.9k repo stars
  • Updated July 3, 2026
  • phuryn/pm-skills

review-resume is an agent skill for "Comprehensive PM resume review and tailoring against 10 best practices including XYZ+S formula, keyword optimization, j

About

The review-resume skill "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." It covers $RESUME : The resume text or content to review. Key workflows include $JOB_POSTING : Optional The job posting or target role description for tailoring feedback. Developers invoke review-resume when the task matches the triggers and reference files in SKILL.md for grounded, stepwise execution. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation.

  • $RESUME : The resume text or content to review
  • $JOB_POSTING : Optional The job posting or target role description for tailoring feedback
  • Explain the best practice clearly
  • Identify what's working well or needs improvement in their resume
  • Provide specific, actionable suggestions

Review Resume by the numbers

  • 2,008 all-time installs (skills.sh)
  • +91 installs in the week ending Aug 5, 2026 (Skillselion tracking)
  • Ranked #56 of 853 Sales & Marketing skills by installs in the Skillselion catalog
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
At a glance

review-resume capabilities & compatibility

Capabilities
$resume : the resume text or content to review · $job_posting : optional the job posting or targe · explain the best practice clearly · identify what's working well or needs improvemen · provide specific, actionable suggestions
Use cases
documentation
From the docs

What review-resume says it does

Conduct a thorough review of a PM resume against 10 best practices. Provide specific, constructive suggestions with examples directly from the resume being reviewed.
SKILL.md
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.
SKILL.md
npx skills add https://github.com/phuryn/pm-skills --skill review-resume

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs2k
repo stars24.9k
Security audit3 / 3 scanners passed
Last updatedJuly 3, 2026
Repositoryphuryn/pm-skills

What problem does review-resume solve for developers using the documented workflows?

"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

Who is it for?

Developers working with review-resume patterns described in the skill documentation.

Skip if: Skip when docs are empty or the task is outside the skill documented scope.

When should I use this skill?

Use when "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 P

What you get

Actionable review-resume guidance grounded in SKILL.md workflows and reference files.

  • structured feedback report
  • tailored bullet rewrite suggestions
  • keyword optimization recommendations

By the numbers

  • Reviews PM resumes against 10 industry best practices
  • Uses the XYZ+S formula for impact-oriented bullet structure

Files

SKILL.mdMarkdownGitHub ↗

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:

  • 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

Related skills

How it compares

Use Review Resume for PM-specific resume critique with XYZ+S and keyword tailoring rather than general writing or engineering resume skills.

FAQ

Who is review-resume for?

Developers and software engineers working with review-resume patterns described in the skill documentation.

When should I use review-resume?

When "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 P.

Is review-resume safe to install?

Review the Security Audits panel on this page before installing in production.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.