BF zhanfu-playwright
站斧 WebDriver 版 Playwright 自动化（Windows≥5.2.12、macOS 版本高于 5.2.10、强制有界面、通讯失败即停）。 获取 WebDriver 端口前仅 HTTP 调用 WebDriverModule；获取端口后 CDP 执行业务。 「战斧」同义「站斧」（如打开战斧=打开站斧）。 适用于站斧、战斧、ZhanFu、WebDriver、Playwright、店铺自动化、小龙虾 OpenClaw RPA。
站斧 WebDriver 版 Playwright 自动化（Windows≥5.2.12、macOS 版本高于 5.2.10、强制有界面、通讯失败即停）。 获取 WebDriver 端口前仅 HTTP 调用 WebDriverModule；获取端口后 CDP 执行业务。…
As a process F 34/100 · Will not run — References files that are not bundled: api_port.json, opening_malls.json, mall_cache.json
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: 1. 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
body-longSKILL.md body ≈ 12792 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: api_port.json - warning
missing-refreference to a missing file: opening_malls.json - warning
missing-refreference to a missing file: mall_cache.json
Process rating: all ten parameters 34/100
- 0Tools and files. 3 referenced file(s) missing: api_port.json, opening_malls.json, mall_cache.json
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 8 mutating operations with no state check
- 40Execution cost. Instruction body is 12792 tokens: crowds the task out of the window
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 103 steps
- 100Consistency. Name and required fields are in place
- low 16 top-level sections: this looks like several domains in one skill
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
- -4Absolute local paths (C:\Users, /home/…): not portable
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +3Description length 220: enough signal without eating the budget
- +4Structure: 61 headings
- +3Step-by-step instructions: 103 items
- +4Has examples (34 code blocks)
- +3All 11 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 47.