Agent skill

utility-update-pm-skills

Checks for newer pm-skills releases, compares local vs. latest version, previews what would change, and updates local files after user confirmation. Generates a structured update report documenting changed files, new capabilities, and the value delta between versions. Use when you want to bring a local pm-skills installation up to date.

product-on-purposegithub.com/product-on-purposeGitHub ↗
claude-codecodexApache-2.0
Install
npx skills add product-on-purpose/pm-skills --skill utility-update-pm-skills --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 4
SKILL.md size: 14 KB
Bundled scripts: none
Version: 1.0.1
Declared author: product-on-purpose
Path: skills/utility-update-pm-skills/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 518
Language: JavaScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 --> # PM Skills Updater This skill updates a local pm-skills installation to the latest public release. It validates connectivity, compares versions, previews changes, and produces a structured report documenting what was updated and what new capabilities are available. ## When to Use - When you want to update local pm-skills to the latest release - When you want to check if a newer version is available - After a new pm-skills release is announced - When onboarding and you want to confirm you have the latest version ## When NOT to Use - To create or edit individual skills -> use `utility-pm-skill-builder` or `utility-pm-skill-iterate` - To validate skills against conventions -> use `utility-pm-skill-validate` - If you are a maintainer working directly on the pm-skills repo (use git) - To pin a specific older version (this skill always targets the latest release) ## Flags | Flag | Behavior | |------|----------| | *(none)* | Full update flow: pre-flight → preview → confirm → update → report | | `--report-only` | Pre-flight → preview → report (no files written) | | `--status` | Lightweight version check - pr

What's inside
Steps it walks through
  1. When to Use
  2. When NOT to Use
  3. Flags
  4. --status behavior
  5. Instructions
  6. Step 1: Pre-Flight
  7. Step 2: Version Comparison
  8. Step 3: Preview
  9. Step 4: Confirmation
  10. Step 5: Update
  11. Step 6: Post-Update
  12. File Scope
  13. Output Contract
  14. Quality Checklist
Ships with 3 files
  • HISTORY.md
  • references/EXAMPLE.md
  • references/TEMPLATE.md
More from pm-skills
All skills →
About this skill
What does the utility-update-pm-skills skill do?

Checks for newer pm-skills releases, compares local vs. latest version, previews what would change, and updates local files after user confirmation. Generates a structured update report documenting changed files, new capabilities, and the value delta between versions. Use when you want to bring a local pm-skills installation up to date.

How do I install it?

Run `npx skills add product-on-purpose/pm-skills --skill utility-update-pm-skills --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From product-on-purpose/pm-skills, a repository with 518 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going