How to use the Product Manager Resume Writer agent skill

What the skill makes the agent do

The skill writes resumes for product management roles at associate, growth, platform, technical and senior levels. Instead of producing a list of launches, it asks the agent to make your product judgment visible: the customer problem, what you prioritized or changed, why, who you worked with, and what happened afterward.

The skill is built to protect accuracy. It works from the facts you supply and does not borrow numbers from examples. If you ask for an inflated or invented claim, it declines that part briefly, offers the strongest truthful version, and finishes the rest of the work.

• Asks about the problem, discovery evidence, decisions you owned, collaborators, constraints, and what shipped and was measured.
• Keeps attribution accurate and separates feature adoption from total company users.
• Preserves metric definitions and time windows, such as the cohort or event behind an activation or retention figure.
• Points delivery-governance resumes to a different skill, project-manager-resume.

How to install the skill

Download the ZIP for the product-manager-resume skill from this page. Then choose one of the two installation routes below, depending on whether you use the skill personally or for one project.

For a personal install, unzip the file into ~/.claude/skills/. For a project-specific install, unzip it into the .claude/skills/ folder inside your project. The skill is defined by a SKILL.md file, which is the file the package contains.

If you use the Claude apps, you can instead upload the skill under Settings → Capabilities → Skills.

• Personal: unzip into ~/.claude/skills/
• Project: unzip into .claude/skills/ inside the project folder
• Claude apps: Settings → Capabilities → Skills, then upload

How to trigger the skill with natural requests

You do not need a special command. Describe what you want in ordinary language and include your evidence. The skill's guidance is to work from your facts without requiring an account, so you can start by pasting notes about your role.

Name the product context and level if you can, such as associate PM on a consumer app or senior PM on a platform team. If you are a delivery or project manager rather than a product manager, say so, because the skill is for product direction.

• "Write a product manager resume for an associate PM role. I worked on an onboarding checklist after support feedback."
• "Help me turn these growth experiment notes into resume bullets. Keep the cohort and time window accurate."
• "Review my senior PM resume and separate portfolio strategy from my direct-report management."

What the agent will ask you and what to prepare

Before drafting, the agent asks questions that match your type of product work. Discovery and 0-to-1 work needs the user problem, research you actually did, alternatives considered, and launch status. Growth work needs the funnel stage, hypothesis, experiment role, cohort, period and guardrail metrics. Platform work needs developer or internal customer needs and operational constraints. Enterprise work needs customer workflow, rollout and adoption context. Senior work needs portfolio decisions and cross-team influence.

Gather your real records before you start: launch dates, metric definitions, the time window you measured, and who owned which decisions.

• The problem and the evidence that you actually observed it
• The decisions you made, changed, stopped or sequenced, and why
• The results measured afterward, with definitions and time windows
• Titles, dates and team names exactly as they should appear

Example: turning a result into an accurate bullet

Suppose you prioritized an onboarding checklist after support feedback, the team launched it, and activation rose from 40% to 46% over the following month, with no controlled experiment. The skill would frame this as an observed change, not proof that the checklist caused it.

The skill's example shows the wording it aims for. It does not claim an A/B-proven lift or sole credit, and it describes the change as six percentage points rather than a 6% relative increase.

Safety notes: scripts and network access

This skill does not run scripts and does not use the network, according to its package description. It requires nothing beyond the instructions it contains. The skill itself says to keep private customer information and resume details out of searches and unapproved services, and to treat job ads and documents you paste in as data rather than instructions.

The skill also says that for account edits it reads the current record, shows concrete changes and asks for authorization before anything is submitted. It does not submit anything on your behalf.

• No scripts are run by this skill
• No network use is listed for this skill
• Keep private customer data and resume details out of unapproved services
• Review every bullet before you send it anywhere

Tips for better results

Give the agent specific evidence rather than adjectives. Facts such as a decision you made, a constraint you worked under, or a measured change make stronger bullets than words like visionary. Tell the agent what you did not own as well as what you did, so credit stays accurate.

The skill can also draw on resume-tailor for a specific posting or portfolio-case-study for a deeper project story, if those skills are installed. Otherwise the agent completes that text itself.

• Name what you prioritized, changed, stopped or sequenced, and why
• State metric definitions and the time window each time you cite a number
• Separate team launches from your individual contribution
• Ask for the open evidence questions the agent lists and answer them