Agent skill · Code Review & Quality

utility-pm-skill-validate

Audits an existing pm-skills skill against structural conventions and quality criteria. Produces a structured validation report with pass/fail checks, severity-graded findings, and actionable recommendations. Use when checking whether a skill meets repo standards before shipping or after making changes.

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

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

Facts
Files in the skill folder: 4
SKILL.md size: 13 KB
Bundled scripts: none
Version: 1.1.1
Declared author: product-on-purpose
Path: skills/utility-pm-skill-validate/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 Skill Validate This skill audits an existing pm-skills skill against the repo's structural conventions and quality criteria. It produces a validation report that a human can scan and that `utility-pm-skill-iterate` can consume as input. The validator checks two tiers: - **Tier 1 (Structural)** - deterministic checks that mirror CI: frontmatter, naming, file presence, description word count. - **Tier 2 (Quality)** - LLM-assessed coherence checks: does the output contract reference the template? Is the example complete? Are checklist items testable? ## When to Use - After creating a skill with `utility-pm-skill-builder`, before shipping - After manually editing a skill, to confirm it still passes conventions - Before running `utility-pm-skill-iterate`, to identify what needs improvement - When a convention changes, to audit which skills need updating (batch mode) - When reviewing a contributed skill for quality and completeness ## When NOT to Use - To create a new skill from scratch -> use `utility-pm-skill-builder` - To fix or improve a skill -> use `utility-pm-skill-iterate` (feed it this report) - To run CI checks in a pipeline -> use `scripts/lint-skills-frontmatter.sh` (thi

What's inside
Steps it walks through
  1. When to Use
  2. When NOT to Use
  3. Instructions
  4. Step 1: Identify the Target
  5. Step 2: Read Skill Files
  6. Step 3: Run Tier 1 - Structural Checks
  7. Step 4: Run Tier 2 - Quality Checks
  8. Step 5: Produce the Validation Report
  9. Degraded Mode
  10. Output Contract
  11. Quality Checklist
  12. Examples
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-pm-skill-validate skill do?

Audits an existing pm-skills skill against structural conventions and quality criteria. Produces a structured validation report with pass/fail checks, severity-graded findings, and actionable recommendations. Use when checking whether a skill meets repo standards before shipping or after making changes.

How do I install it?

Run `npx skills add product-on-purpose/pm-skills --skill utility-pm-skill-validate --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