review-resume
by phurynreview-resume is a Product Manager resume review skill that gives structured, personalized feedback on impact, keyword alignment, and role fit. Use it to review an existing resume, tailor it to a target job posting, and improve interview readiness with concrete edits and examples.
This skill scores 78/100, which means it is a solid listing candidate with useful PM-resume review workflow value. Directory users should expect a reasonably triggerable, well-structured skill that can guide more specific resume feedback than a generic prompt, though it lacks supporting files and explicit install/help scaffolding.
- Clear use case and trigger: the frontmatter says to use it for reviewing a PM resume or tailoring it to a job posting.
- Strong operational guidance: the SKILL.md defines inputs ($RESUME, optional $JOB_POSTING) and a step-by-step response structure.
- Substantial workflow content: the body is large and structured with multiple headings and signals for scope, workflow, constraints, and practical review steps.
- No supporting scripts, references, or resources, so users must trust the embedded instructions alone.
- No install command or repo-level help assets, which makes adoption slightly less self-serve for directory users.
Overview of review-resume skill
What review-resume does
The review-resume skill helps you review and tailor a Product Manager resume with structured, job-focused feedback. It is built for people who want more than a generic critique: the review-resume skill checks the resume against PM-specific best practices, including structure, impact, keyword alignment, and tailoring to a target role.
Who it is best for
Use review-resume if you are applying for PM roles, rewriting an existing PM resume, or trying to improve how your experience reads to recruiters and hiring managers. It is especially useful when you already have a resume draft and want targeted edits, not a blank-page resume generator.
What makes it different
The main value of review-resume is specificity. Instead of broad advice, it expects the resume text and can optionally use a job posting to make suggestions more relevant. That makes it a better fit than a general prompt when you need feedback tied to the actual content you wrote.
How to Use review-resume skill
Install review-resume
Install with:
npx skills add phuryn/pm-skills --skill review-resume
For a successful review-resume install, confirm the skill is placed under pm-toolkit/skills/review-resume and that your agent can load the SKILL.md frontmatter and body. There are no extra scripts or helper folders in this repo, so the skill depends mainly on the prompt instructions inside SKILL.md.
Give it the right input
The review-resume usage pattern is simple: provide the resume text as $RESUME, and include $JOB_POSTING when you want tailoring against a specific role. The better the input, the better the critique.
A weak input looks like: “Review my PM resume.”
A stronger input looks like: “Review my resume for a senior PM role at a B2B SaaS company. Focus on impact bullets, keyword coverage, and whether my leadership reads senior enough. Here is the resume text and the job posting.”
Use a two-step workflow
A practical review-resume guide is to first run the skill on the plain resume, then rerun it with the target posting once you know the biggest gaps. That avoids over-tuning to a job description before the base story is clear.
For best results:
- Paste the full resume text, not screenshots or fragments.
- Add the job posting only if you are tailoring.
- Ask for direct quotes and replacement bullets where possible.
- Keep the target level explicit: PM, senior PM, group PM, or product leader.
Read the core file first
Start with SKILL.md, because this repository currently contains a single skill file and no supporting rule sets or references. The most useful parts are the purpose statement, input arguments, and response structure. Those sections tell you how the model is expected to behave and what content it needs to produce useful feedback.
review-resume skill FAQ
Is review-resume only for Product Managers?
Yes, this review-resume skill is aimed at PM resumes. It is tuned to PM best practices, so it is strongest when the candidate experience includes product strategy, roadmaps, discovery, metrics, or cross-functional leadership. If you are applying for design, engineering, or operations roles, the feedback may be less aligned.
Do I need a job posting to use it?
No. The review-resume skill can review a resume on its own. A job posting simply improves tailoring, especially for keyword alignment and role fit. If you do have a target role, include it; if not, the skill can still surface structural and content issues.
Is this better than a normal prompt?
Usually, yes, because the skill gives the model a defined review framework instead of a vague “make this better” request. That reduces guesswork and helps the output stay focused on practical resume edits rather than general career advice.
Is it beginner-friendly?
Yes, if you already have a resume draft. It is not meant to teach resume writing from scratch; it is meant to diagnose and improve an existing PM resume. Beginners get the most value when they submit a complete resume and ask for clear, prioritized fixes.
How to Improve review-resume skill
Give sharper evidence
The biggest quality lever for review-resume for Technical Writing-style precision is not more text; it is more evidence. If your bullets are vague, the skill can only recommend stronger wording in general terms. If your resume includes scope, outcomes, metrics, and product context, it can give concrete replacements.
Tell it what kind of PM you are
Make your target role explicit so the review can judge seniority and emphasis correctly. A resume for platform PM, growth PM, or B2B PM should not be reviewed the same way as one for consumer product or startup generalist roles. State the role, level, and industry up front.
Ask for rewrite-ready output
If you want actionable edits, ask for:
- the top 5 issues blocking interviews,
- rewritten bullets for your weakest experience,
- missing keywords from the job posting,
- and a concise summary of what to cut.
This makes the output more useful than a long critique and helps you iterate faster.
Re-run after each revision
Use the first pass to fix structure and clarity, then rerun review-resume on the updated version. Common failure modes are thin impact metrics, overly long bullets, and mismatch between claimed seniority and actual evidence. Iterating once or twice usually improves the signal more than trying to perfect the prompt on the first try.