BF skill-function-test
技能场景测试套件 —— 备份 → 蓝皮书 → 配置确认 → S1-S3场景测试 → D1-D6功能测试 → S4执行忠实度 → 修复 → bump → 双格式报告 → 结论写入test-report.md。配置驱动流程，钩子强制阻断。
技能场景测试套件 —— 备份 → 蓝皮书 → 配置确认 → S1-S3场景测试 → D1-D6功能测试 → S4执行忠实度 → 修复 → bump → 双格式报告 → 结论写入test-report.md。配置驱动流程，钩子强制阻断。
As a process F 33/100 · Will not run — References files that are not bundled: references/*.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.
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: 30. 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/*.md - note
frontmatter-keyunknown frontmatter key "data_dir" - note
frontmatter-keyunknown frontmatter key "external_data_dir" - note
frontmatter-keyunknown frontmatter key "sensitive_access" - note
frontmatter-keyunknown frontmatter key "critical_write" - note
frontmatter-keyunknown frontmatter key "permission_weight" - note
frontmatter-keyunknown frontmatter key "trigger" - note
frontmatter-keyunknown frontmatter key "trigger_negative" - note
frontmatter-keyunknown frontmatter key "h1_position" - note
frontmatter-keyunknown frontmatter key "meta_field_sync" - note
frontmatter-keyunknown frontmatter key "faq_unparsable" - note
frontmatter-keyunknown frontmatter key "faq_quality" - note
frontmatter-keyunknown frontmatter key "create_permissions_md" - note
frontmatter-keyunknown frontmatter key "trigger_quality" - note
frontmatter-keyunknown frontmatter key "data_dir_compliance"
Process rating: all ten parameters 33/100
Will not run. References files that are not bundled: references/*.md
- 0Tools and files. 1 referenced file(s) missing: references/*.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
- 30Running it twice. 1 mutating operations with no state check
- 100Steps. 18 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2022 tokens
- low The response is described with custom markup (5 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)
- +3Description length 117: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -31 of 13 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +4Structure: 19 headings
- +3Step-by-step instructions: 18 items
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (12 of 12)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.
External checks
ClawHub: suspicious
This skill is a testing suite, but it can execute and modify target skills and includes under-disclosed ways to generate misleading reports.
LLM: suspicious (high) · VirusTotal: · 25 Jun 2026