AC requirement-pre-review
从业务、研发、测试三个视角对需求文档进行系统性预评审，自动识别场景不完整、边界条件缺失、异常流程遗漏、业务规则模糊等问题，输出结构化评审报告及补充建议。当用户提交需求文档、PRD、功能说明、用户故事等内容并希望进行评审、检查、审核时，立即使用此 Skill。触发词包括但不限于："帮我评审需求"、"需求预评审"、"检查PRD"、"需求有什么问题"、"需求文档review"、"帮我看看需求"、"需求质量检查"。即使用户只是粘贴了一段需求描述，也应主动触发此 Skill 进行评审。
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.
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: 2. 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. 16 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 382 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
- +1No license
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +3Description length 240: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 16 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.
External checks
ClawHub: clean
This is a single-file requirement-review skill with no executable code, installer, persistence, credential use, or hidden data flow.
LLM: benign (high) · VirusTotal: · 29 May 2026