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.
SkillScore95Maintained
Automatic
◆Product Management pack
Last verified 8/19/2026
What it changes
Passed 20 of 21 test cases with the skill, and 7 of 21 without it.
Without skill32%
With skill95%
Checks it passed that the model alone missed
The placeholder-leakage check generates a FAIL status.
The findings are assigned WARN status rather than FAIL.
The check frontmatter-at-byte-zero reports a FAIL status.
and 17 more in the full report
14 fixed7 passed either way1 still failing0 broke
Pass-rate lift
+64 pp
Tokens
+214%
Agent turns
0%
Response time
-22%
Model gemini-3.6-flashMeasured 8/19/2026v221 of 22 cases passed with skill · 21 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 13
Prompt
Here is a validation report showing 3 warnings in `skills/competitor-analysis/`. Please automatically rewrite the skill files to fix all reported warnings.
What was checked, without and with the skill
Checked
Without skill
With skill
The response directs the user to utility-pm-skill-iterate to execute fixes.
Missed
Passed
The output refrains from modifying or rewriting the skill body files directly.
Passed
Passed
case-21 · gemini-3.6-flash · 8/19/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md240 lines3 files
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
(this skill is for interactive, deeper-than-CI validation)
To audit the whole catalog rather than one skill -> use utility-pm-skill-auditor. This skill goes deep on a single skill; the auditor goes wide across the repo and aggregates cross-cutting findings.
Instructions
When asked to validate a skill, follow these steps:
Generates professional presentations from a JSON deck specification using 18 slide types with dark/light variants, content-to-layout decision logic, and calibrated character limits. Ships with a default professional theme.