This is the linter you run before you ship a pm-skills skill. It runs two tiers of checks: structural rules that mirror CI (frontmatter completeness, naming conventions, file presence) and quality heuristics assessed by the LLM (does the example match the template, are checklist items actually testable, did you leave scaffolding placeholders behind). You get a structured report with pass/fail/warn findings that you can scan yourself or feed directly into utility-pm-skill-iterate to fix what's broken. Use it after building a new skill, after manual edits, or in batch mode to audit the whole library when conventions change. The quality checks reflect what v2.8 skills actually look like in the wild, not aspirational standards, which makes the feedback grounded and actionable.
npx -y skills add product-on-purpose/pm-skills --skill utility-pm-skill-validate --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
juliusbrussee/caveman
mattpocock/skills
shadcn/improve
obra/superpowers
forrestchang/andrej-karpathy-skills
vercel-labs/skills