AF 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.
Audits an existing pm-skills skill against structural conventions and quality criteria.
As a process F 50/100 · Will not run — References files that are not bundled: ../../site/src/content/docs/guides/creating-pm-skills.md, scripts/lint-skills-frontmatter.sh, scripts/check-trigger-fixtures.mjs
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../../site/src/content/docs/guides/creating-pm-skills.md - warning
missing-refreference to a missing file: scripts/lint-skills-frontmatter.sh - warning
missing-refreference to a missing file: scripts/check-trigger-fixtures.mjs - warning
missing-refreference to a missing file: scripts/check-output-eval-assets.mjs - warning
missing-refreference to a missing file: scripts/check-reciprocal-boundary-pointers.mjs - warning
missing-refreference to a missing file: scripts/check-heading-canon.mjs
Process rating: all ten parameters 50/100
- 0Tools and files. 6 referenced file(s) missing: ../../site/src/content/docs/guides/creating-pm-skills.md, scripts/lint-skills-frontmatter.sh, scripts/check-trigger-fixtures.mjs
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 2 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 60Failures and branches. 2 branches
- 100Steps. 41 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3339 tokens
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- -5TODO / placeholder text left in the skill
- +2Single-language instructions
- +3Description length 304: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 41 items
- +3Output format is stated explicitly
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.