BD product-manager
以专业产品经理视角分析用户需求，拆解产品功能，输出结构化的产品文档（PRD、竞品分析、用户故事、需求池、数据指标等）。当用户提出产品创意、功能需求、改进建议或需要产品规划时触发。适用于APP、Web、小程序、B端系统、AI产品等全品类软件产品。
As a process D 49/100 · Unfinished process — 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.
For the model run — optional
- 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: 8. 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 49/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
- 40Consistency. Frontmatter name (product-manager) differs from the folder (product-manager-ai)
- 100Tools and files. No external tools needed
- 100Steps. 27 steps
- 100Execution cost. Instruction body is 448 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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 122: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 27 items
- +4Reference files are cited in the instructions (6 of 6)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.
External checks
ClawHub: clean
This is a text-only product-management skill that creates structured product documents and does not request hidden access, execution, credentials, or persistence.
LLM: benign (high) · VirusTotal: · 29 May 2026