BD requirement-impact-check
需求文档变动影响检查。当用户想要对照主需求文档的变动来检查相关文档是否受影响时使用此 skill。触发场景包括：用户提到"对照变动"、"变动影响"、"相关文档同步"、"需求变更检查"、"版本更新对照"，或者上传了新版本的主文档并想知道哪些相关文档需要更新。即使用户只是说"这部分改了，其他地方要不要跟着改"，只要涉及多份相互关联文档的变动同步分析，都应使用此 skill。
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: 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 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 (requirement-impact-check) differs from the folder (generic-requirement-impact-check)
- 100Tools and files. No external tools needed
- 100Steps. 30 steps
- 100Execution cost. Instruction body is 603 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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +3Description length 186: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 30 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.
External checks
ClawHub: clean
This is a plain instruction-only skill for checking whether related requirement documents need updates after a main document changes.
LLM: benign (high) · VirusTotal: · 29 May 2026