BF nl2ms-ui
根据自然语言通过midscene的api生成midscene脚本,可以生成web端、Android端、iOS端和PC端的midscene脚本。当用户提及生成脚本,android脚本、iOS脚本、web脚本、PC脚本时使用。
根据自然语言通过midscene的api生成midscene脚本,可以生成web端、Android端、iOS端和PC端的midscene脚本。当用户提及生成脚本,android脚本、iOS脚本、web脚本、PC脚本时使用。
As a process F 35/100 · Will not run — References files that are not bundled: references/midscene-api, references/common-scenarios.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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Dangerous commands
cmd-privilegereferences/examples-web-ts.md:34Privilege escalation / world-writable permissions (detector / deny-list definition; test fixture / example file)args: ["--no-sandbox", "--disable-setuid-sandbox"],
detectorfixture
Files scanned: 9. 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/midscene-api - warning
missing-refreference to a missing file: references/common-scenarios.md
Process rating: all ten parameters 35/100
Will not run. References files that are not bundled: references/midscene-api, references/common-scenarios.md
- 0Tools and files. 2 referenced file(s) missing: references/midscene-api, references/common-scenarios.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. 26 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 404 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)
- +3Description length 111: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Structure: 9 headings
- +3Step-by-step instructions: 26 items
- +4Reference files are cited in the instructions (8 of 8)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 60.