BC pmstudio-nfr
Detailed completeness audit of all project documents. Use when someone asks "are we ready for production", "audit our docs", "readiness check", "nfr tracker", or "what's missing". Do NOT use for a quick command listing — use /pmstudio instead. Scans every document for section-level completeness, reports staleness, and gives prioritized gap-closure recommendations.
Detailed completeness audit of all project documents.
As a process C 50/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
How to improve
- 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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Risky intent
intent-offensive-securityreferences/category-checklists.md:91Offensive-security / dual-use content (legitimate for authorised testing; review intended use)## Pentest — Penetration Testing
-
low Risky intent
intent-offensive-securityreferences/category-checklists.md:96Offensive-security / dual-use content (legitimate for authorised testing; review intended use)[ ] Pentest scope defined
-
low Risky intent
intent-offensive-securityreferences/category-checklists.md:97Offensive-security / dual-use content (legitimate for authorised testing; review intended use)[ ] Pentest conducted (report received)
Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "domain"
Process rating: all ten parameters 50/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 2 mutating operations with no state check
- 40Consistency. Frontmatter name (pmstudio-nfr) differs from the folder (nfr-tracker)
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 60Failures and branches. 2 branches
- 100Steps. 24 steps
- 100Execution cost. Instruction body is 1291 tokens
- 100Progress reporting. Reports progress
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
- +3Output format is not stated: the model decides each time
- -42 reference files, but SKILL.md never points to them: the model will not open them
- +1No license
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +4Description says when NOT to use the skill
- +3Description length 366: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 24 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.