AC product-management
产品管理技能套件：PRD生成、产品脑暴、产品指标复盘、用户反馈分析、用户故事拆解、竞品分析、路线图更新、需求优先级排序。 PRD生成: 帮我写个PRD, 帮我出个需求文档, 写PRD, 需求文档, 功能规格; 产品脑暴: 产品脑暴, 头脑风暴, brainstorm, 创意发散; 产品指标复盘: 产品指标复盘, 数据复盘, DAU分析, 转化漏斗; 用户反馈分析: 帮我分析下用户反馈, 帮我看看用户都在说什么, 用户声音, NPS分析; 用户故事拆解: 用户故事拆解, 用户故事, story拆分, 敏捷需求; 竞品分析: 帮我分析下竞品, 帮我做个竞品调研, 竞品跟踪, 功能对比; 路线图更新: 路线图更新, roadmap, 版本规划, 排期; 需求优先级排序: 需求优先级排序, 需求优先级, RICE, Kano模型。
产品管理技能套件：PRD生成、产品脑暴、产品指标复盘、用户反馈分析、用户故事拆解、竞品分析、路线图更新、需求优先级排序。 PRD生成: 帮我写个PRD, 帮我出个需求文档, 写PRD, 需求文档, 功能规格; 产品脑暴: 产品脑暴, 头脑风暴, brainstorm, 创意发散; 产品指标复盘: 产品指标复盘…
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 11. 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")
Process rating: all ten parameters 53/100
- 0Result and completion. Does not say what the result is
- 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
- 100Tools and files. No external tools needed
- 100Steps. 23 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1187 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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 366: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 23 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (8 of 8)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.