BD test-reviewer
Review test design and readiness, 测试评审。Use when: Test Spec/Test Case Package 完成后，需要审查独立测试范围内的覆盖、追溯、执行证据与遗留风险，作为发布准备前的测试门禁。
Review test design and readiness, 测试评审。Use when: Test Spec/Test Case Package 完成后，需要审查独立测试范围内的覆盖、追溯、执行证据与遗留风险，作为发布准备前的测试门禁。
As a process D 35/100 · Unfinished process — References files that are not bundled: ../../references/workflow-execution.md, ../../references/review-assurance.md, ../../references/document-amendments.md
How to improve
- 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: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../../references/workflow-execution.md - warning
missing-refreference to a missing file: ../../references/review-assurance.md - warning
missing-refreference to a missing file: ../../references/document-amendments.md
Process rating: all ten parameters 35/100
- 0Tools and files. 3 referenced file(s) missing: ../../references/workflow-execution.md, ../../references/review-assurance.md, ../../references/document-amendments.md
- 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
- 100Steps. 80 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1688 tokens
- 100Running it twice. No mutating operations
- low 12 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (3 tags): a typed call is more reliable
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 122: enough signal without eating the budget
- +4Structure: 19 headings
- +3Step-by-step instructions: 80 items
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (2 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.