BF pm-review
PM PRD 评审 skill。PRD v1.0 产出后,引导 PM 组织三端(服务端/客户端/测试)+ 设计 review 并行,通过 5 轮迭代拿到可 coding 的 v3.x 终稿。触发场景:用户说"组织 review"、"PRD 评审"、"三端对齐"、或 workflow-start 路由到此 skill。
PM PRD 评审 skill。PRD v1.0 产出后,引导 PM 组织三端(服务端/客户端/测试)+ 设计 review 并行,通过 5 轮迭代拿到可 coding 的 v3.x 终稿。触发场景:用户说"组织 review"、"PRD 评审"、"三端对齐"、或 workflow-start 路由到此 skill。
As a process F 36/100 · Will not run — References files that are not bundled: ../../templates/prd-template.md, ../../lessons/by-role/pm.md
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: ../../templates/prd-template.md - warning
missing-refreference to a missing file: ../../lessons/by-role/pm.md
Process rating: all ten parameters 36/100
- 0Tools and files. 2 referenced file(s) missing: ../../templates/prd-template.md, ../../lessons/by-role/pm.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Result and completion. Does not say what the result is
- 40Consistency. Frontmatter name (pm-review) differs from the folder (workflow-dlc-pm-review)
- 100Steps. 48 steps
- 100Execution cost. Instruction body is 1241 tokens
- 100Running it twice. No mutating operations
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -225 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +3Description length 159: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 48 items
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.