BF ai-test-engineer
AI测试工程师全生命周期技能集合。覆盖需求分析→测试设计→AI协作→自动化→执行监控→质量度量→专项测试7大阶段共48个专家级测试技能模块，使初级测试人员输出专家级测试用例。触发词：测试用例、测试设计、测试策略、测试分析、测试报告、接口测试、性能测试、安全测试、自动化测试、AI测试、质量度量、缺陷分析、回归测试、兼容性测试、测试评审、测试估算、探索性测试、CI/CD测试、测试数据、测试环境、测试覆盖率、测试效率、质量模型、测试ROI。
AI测试工程师全生命周期技能集合。覆盖需求分析→测试设计→AI协作→自动化→执行监控→质量度量→专项测试7大阶段共48个专家级测试技能模块，使初级测试人员输出专家级测试用例。触发词：测试用例、测试设计、测试策略、测试分析、测试报告、接口测试、性能测试、安全测试、自动化测试、AI测试、质量度量、缺陷分析、回归测试、兼容…
As a process F 35/100 · Will not run — References files that are not bundled: references/phaseX-xxx.md
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 12. 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") - warning
missing-refreference to a missing file: references/phaseX-xxx.md - note
frontmatter-keyunknown frontmatter key "agent_created"
Process rating: all ten parameters 35/100
- 0Tools and files. 1 referenced file(s) missing: references/phaseX-xxx.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. 35 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1033 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 219: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 35 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (7 of 7)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.