BD control-browser
Use when opening, navigating, inspecting, testing, clicking, typing, filling, screenshotting, or verifying web pages and local HTTP targets (localhost, 127.0.0.1, ::1) inside ZCode, including browser/web-UI automation, rendered-page scraping, frontend checks, and visible page-state reading. Prefer this over Computer Use for anything that stays inside a web page, unless the user explicitly asks for Computer Use. Main agent only.
A skill for browser control within ZCode: opens pages, clicks, fills forms, takes screenshots. Promises to handle web interfaces and local HTTP servers instead of general Computer Use. Files contain 4495 tokens, one folder, no scripts. Grade B, quality 78/100, process 48/100. No critical errors, references intact. Not tested on models, no sandbox run. Supports Claude, Cursor, DeepSeek, and eight other platforms.
Verdict is 'ok', but quality is middling—something in the logic isn't quite right, implementation process is rough. Install if you need browser automation inside ZCode and can tolerate potential hiccups. Don't rely on it for production.
0.0.1, ::1) inside ZCode, including browser/web-UI automation, rendered-page scraping, frontend checks, and visible page-state reading. Prefer this over…
As a process D 48/100 · Unfinished process — References files that are not bundled: scripts/browser-client.mjs
How to improve
- 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
missing-refreference to a missing file: scripts/browser-client.mjs
Process rating: all ten parameters 48/100
- 0Tools and files. 1 referenced file(s) missing: scripts/browser-client.mjs
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 4 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 70Execution cost. Instruction body is 4495 tokens
- 100Steps. 27 steps
- 100Failures and branches. 5 branches, has a failure section
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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 431: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 27 items
- +4Has examples (7 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.