BF user-test-toolkit
为 AI 时代的 Vibe Coding 页面量身打造的用户测试工具链。无需修改业务代码，只要把 tracker.js 引入任意页面，即可自动采集用户的操作轨迹、犹豫点、困惑行为、停留热区；配合 survey.js，能在用户真实使用流程中嵌入式触发任务引导、微问卷检查点（Checkpoint）、SUS/EV/NPS 标准量表和 SAM 情绪评估，所有数据上报到你的服务端。适用于：可用性测试、用户研究、埋点采集、A/B 效果验证。创新点：埋点和问卷均与业务流零侵入融合，不是事后补发，而是用户"正在做事的时候"自动感知、自动触发。
As a process F 35/100 · Will not run — References files that are not bundled: assets/test-video.mov
ProcedureSoftware developmentInfrastructuretype and topics are labelled automatically from the skill text
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: 9. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Unexpected scalar at node end at line 2, column 263: …用于：可用性测试、用户研究、埋点采集、A/B 效果验证。创新点：埋点和问卷均与业务流零侵入融合，不是事后补发，而是用户"正在做事的时候"自动感知、自动触发。" ^^^^^^^^^^^^^^^^^^^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: assets/test-video.mov
Process rating: all ten parameters 35/100
Will not run. References files that are not bundled: assets/test-video.mov
- 0Tools and files. 1 referenced file(s) missing: assets/test-video.mov
- 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. 10 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1943 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 266: enough signal without eating the budget
- +4Structure: 23 headings
- +3Step-by-step instructions: 10 items
- +4Has examples (11 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 60.
External checks
ClawHub: suspicious
This is a legitimate user-testing toolkit, but it can collect and send detailed behavior and survey data without built-in privacy controls.
LLM: suspicious (high) · VirusTotal: · 29 May 2026