skills / other

review-resume

what it does

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.

Verified Before and after: 2 models 1 try per case View source Download .zip

Compare the answers

Answers from Claude Sonnet 5.5 and GPT-6.1 Sol · try 1 of 1

Same request, same model, once with the skill and once without. Read both and judge for yourself.

“Here's my resume and the job I want. What should I change before I apply?”

Source material given with the request

JOB POSTING: Senior Product Manager, Payments, at Lumora (fictional) - 5+ years of product management, at least 2 in payments or fintech - Own the card acceptance and payouts roadmap - Run experiments to improve payment conversion - Comfortable writing SQL to answer your own questions - Work with risk and compliance teams RESUME: Priya Anand, priya.anand@example.com Senior Product Manager, Tallis Travel, 2022 - present - Led redesign of hotel search results; increased bookings per search by 12% - Launched loyalty points program to 1.4M members - Built SQL dashboards used by 30 PMs to track funnel metrics Product Manager, Tallis Travel, 2019 - 2022 - Managed the mobile app settings and notifications - Owned the checkout and payments flow; added two local payment methods in Brazil and India, raising payment success rate from 81% to 89% - Worked with fraud team to cut chargebacks by 30%
with the skill
Priya, you have a strong foundation for this role: **payment success improved from 81% to 89%, chargebacks fell 30%, and you’ve built SQL dashboards used by 30 PMs.** Those are directly relevant to Lumora—but your resume currently leads with hotel search and loyalty, so your payments experience is too easy to miss. **Before applying, prioritize three changes:** 1. Put your payments, fraud, and SQL experience front and center. 2. Make the duration and scope of your payments ownership explicit. 3. Add evidence of experimentation, card acceptance, payouts, and compliance **where you genuinely have it**. ## 1. Add a targeted professional summary A short summary will connect your current seniority with your earlier payments work. **Suggested version:** > Senior Product Manager with product management experience spanning travel, checkout, and payments since 2019. Improved payment success from 81% to 89% through local payment method launches and partnered with fraud teams to reduce chargebacks by 30%. Hands-on SQL experience building funnel dashboards used by 30 PMs. This surfaces your fit without claiming payments experience you haven’t established. ## 2. Keep the pronoun-free style Your bullets already avoid “I,” “my,” and “we.” Keep that approach: start with clear actions such as “Owned,” “Launched,” and “Analyzed.” ## 3. Stay concise—but add the missing evidence Three bullets per role is easy to scan. This excerpt is short enough that you can add one or two substantive bullets without making it crowded.
Show the rest (71 more lines)
Use that space for relevant evidence, not more general responsibilities. For example, replace or expand: > “Managed the mobile app settings and notifications” Explain what changed and why it mattered—or remove it if stronger payments experience is available. The actual page count can’t be assessed from pasted text; aim for one to two pages. ## 4. Strengthen the achievement structure Your strongest bullet connects ownership, action, context, and a measurable result: > “Owned the checkout and payments flow; added two local payment methods in Brazil and India, raising payment success rate from 81% to 89%” Make the impact easier to spot: > **Increased payment success by 8 percentage points, from 81% to 89%, by launching two local payment methods across Brazil and India; owned the checkout and payments flow.** Two other bullets need more substance: - **“Launched loyalty points program to 1.4M members”** shows reach, not adoption or business impact. Add enrollment, repeat booking, redemption, or retention results if available. - **“Worked with fraud team to cut chargebacks by 30%”** has a strong outcome but doesn’t explain your contribution. Specify the policy, product change, or analysis you owned. Aim for most bullets to show **what improved, how much, what you did, and the relevant context**. Don’t invent metrics where none were measured. ## 5. Verify your contact details “priya.anand@example.com” has a professional naming format, but **replace it with your real email if this is an anonymized placeholder**. Add a phone number, location, and LinkedIn URL if they aren’t already on the full resume. ## 6. Tailor explicitly to Lumora’s requirements Here’s how your evidence currently maps: | Lumora requirement | Current evidence | What to change | |---|---|---| | 5+ years in PM | Roles dating to 2019 | Add exact months | | 2+ years in payments/fintech | Payments ownership within 2019–2022 role | State how long you owned payments; the role dates alone don’t establish this | | Card acceptance roadmap | Checkout and local payment methods | Clarify any card authorization, processor, or acceptance work | | Payouts roadmap | Not shown | Add only if you have relevant experience | | Conversion experiments | Booking and payment improvements | Explain whether either resulted from controlled experiments | | Hands-on SQL | Dashboards used by 30 PMs | Show an analytical question you answered and the decision it informed | | Risk and compliance | Fraud collaboration | Clarify risk partnership; add compliance work separately if applicable | **Your largest evidence gaps are payouts, explicit experimentation, and compliance—not necessarily lack of experience, but lack of proof on the page.** ## 7. Show product judgment, not just delivery “Built SQL dashboards” demonstrates technical ability. To strengthen it for a senior PM role, explain what those dashboards helped you decide. If accurate, use a structure like: > Wrote SQL to identify **[specific funnel issue]**, informing **[prioritization or product decision]**; built dashboards used by 30 PMs. Likewise, describe how you selected the local payment methods: customer research, failed-payment analysis, market opportunity, or implementation trade-offs. One concrete decision can demonstrate more seniority than a generic “product strategy” skills list. ## 8. Use a clear section order Recommended order: **Contact information → Summary → Experience → Education → Relevant certifications → Technical skills** Your experience is correctly reverse chronological. Keep that order; use the summary to surface your earlier payments work rather than moving the older role above your current one. Education isn’t included in the excerpt—add it if missing from the full resume. ## 9. Position yourself as an experienced PM You don’t need coursework or side projects to establish PM credibility. Prioritize professional outcomes and ownership. Relevant payments training can supplement your experience, but it won’t substitute for evidence of owning payments products. ## 10. Keep the standard titles; sharpen the language “Senior Product Manager” and “Product Manager” are clear, appropriate titles. Keep them. Add month–year dates, and replace vague phrases such as “Managed” or “Worked with” with a precise description of your contribution—not a stronger ownership claim than you can defend. ### Suggested experience edits using only the facts provided **Senior Product Manager | Tallis Travel | 2022–Present** - Built SQL dashboards used by 30 PMs to track funnel metrics. - Increased bookings per search by 12% by leading a redesign of hotel search results. - Launched a loyalty points program to 1.4M members. **Product Manager | Tallis Travel | 2019–2022** - Increased payment success by 8 percentage points, from 81% to 89%, by launching two local payment methods across Brazil and India; owned the checkout and payments flow. - Partnered with the fraud team to reduce chargebacks by 30%. - Managed mobile app settings and notifications. **[Replace with a specific outcome or stronger relevant achievement.]** You have credible payments results, Priya. The biggest improvement is making **your payments tenure, personal contribution, and decision-making** unmistakable. If you revise those details, I’d be happy to review the next version before you apply.
without
Your strongest match is currently buried: **you’ve owned a payments flow, improved payment success, and worked with fraud.** Make that experience the center of your application rather than leading with hotel search and loyalty. ### 1. Add a targeted summary For example: > Product manager with 7+ years of experience in travel technology, including ownership of checkout and payments. Improved payment success from 81% to 89% through local payment method launches in Brazil and India, partnered with fraud to reduce chargebacks by 30%, and built SQL dashboards used by 30 PMs. Use “7+ years” only if your start month supports it; otherwise, use “6+ years.” ### 2. Strengthen and elevate the payments bullets Keep your roles in reverse chronological order, but put payments first within your 2019–2022 role: **Product Manager, Tallis Travel | 2019–2022** - Owned checkout and payments; launched two local payment methods across Brazil and India, increasing payment success from **81% to 89% (+8 percentage points)**. - Partnered with the fraud team to reduce chargebacks by **30%**. - Managed mobile app settings and notifications. If accurate, expand the first two bullets to explain your decisions and scope: payment provider integrations, roadmap prioritization, authorization failures, fraud controls, or engineering coordination. Don’t add these just for keywords. ### 3. Make your current role demonstrate experimentation and SQL
Show the rest (26 more lines)
Suggested ordering and wording: **Senior Product Manager, Tallis Travel | 2022–present** - Led a redesign of hotel search results, increasing bookings per search by **12%**. - Built SQL dashboards used by **30 PMs** to monitor funnel performance. - Launched a loyalty points program to **1.4M members**. For Lumora, these bullets would be stronger with additional evidence: - **Experimentation:** If you ran A/B tests, name the experiment and measured result. A redesign alone doesn’t establish experimentation experience. - **Hands-on SQL:** If you queried data to diagnose funnel drop-off or inform a roadmap decision, describe that—not just dashboard adoption. ### 4. Address the gaps honestly | Lumora requirement | What your resume shows | What to clarify | |---|---|---| | 5+ years in product | Strong match | Add employment months for precise tenure | | 2+ years in payments/fintech | Payments work within a three-year role | State how long you owned payments, if it was at least two years | | Card acceptance and payouts roadmap | Checkout/payments ownership | Specify card acceptance or payouts work **only if you did it** | | Payment conversion experiments | Improved payment success | Add testing methodology, if applicable | | SQL | Dashboard building | Show a specific analysis you performed | | Risk and compliance | Fraud partnership | Add compliance collaboration only if you have it | **The biggest unresolved gap is payouts.** Your resume also doesn’t explicitly establish card acceptance or compliance experience. Don’t imply those from general payments work; highlight the transferable experience you do have. ### Before you submit Prioritize three edits: **add the summary, elevate the payments results, and clarify the duration of your payments ownership.** You look like a credible applicant, but the current version makes the recruiter work too hard to see the fit.

Answers are shown exactly as the model wrote them, from the first try, and nothing is picked by hand.

The models

2 models

Claude Sonnet 5.5

made by Anthropic

claude-sonnet-5-5 · revision not reported by the provider

1 try per case · tested 3 Nov 2026

GPT-6.1 Sol

made by OpenAI

gpt-6.1-sol · revision not reported by the provider

1 try per case · tested 3 Nov 2026

The tasks

written by Carte Blanche
senior-pm-general-review

“Can you review my resume? I'm applying for senior PM roles at B2B SaaS companies.”

summary-only

“Just rewrite my summary line. The rest of the resume is fine, I don't need feedback on it.”

tailor-to-posting

“Here's my resume and the job I want. What should I change before I apply?”

teacher-to-apm

“I'm a high school teacher trying to get an associate PM job. Can you look at my resume and tell me what to fix?”

too-long-resume

“Recruiters aren't calling me back. Is my resume too long? Here's my most recent job, it's the biggest section.”

Install

Download the .zip and unzip it. Put its files, in a folder named review-resume, here:

Claude Code~/.claude/skills/Every project. For one project only, use .claude/skills/ inside it.
Codex~/.agents/skills/Every project. For one repository only, use .agents/skills/ inside it.
Cursor~/.cursor/skills/Cursor also reads the Claude Code and Codex folders above.

Then start a new session and ask for what the skill does. Other agents that read SKILL.md have their own skills folder; check their docs.

Coming after launch: get skills from inside your agent, no download needed.