Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →automateyournetwork/browser-viz-verify
Verifies that a NetClaw-generated visualization HTML file (three.js, canvas, drawio, UML, markmap) actually renders correctly — screenshot, console-error check, and an optional Lighthouse audit. Use immediately after generating any browser-based visualization output, to close the QA gap that otherwise requires a human to manually open the file. Never touches an external site or the authenticated browser profile.
Passed 9 of 16 test cases with the skill, and 3 of 16 without it.
and 12 more in the full report
9 fixed4 passed either way9 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
Checking local diagram `/var/tmp/network_tree.html`. The page renders completely with zero console warnings or errors. What is the required outcome verdict string?
| Checked | Without skill | With skill |
|---|---|---|
| Sets verdict value to rendered_clean | Missed | Passed |
The instructions your model reads when the skill loads.
NetClaw ships several skills that generate browser-based visualization outputs — threejs-network-viz, canvas-network-viz, drawio-diagram, uml-diagram, markmap-viz. Until now, confirming that a generated file actually rendered correctly (no blank canvas, no JavaScript errors, no broken layout) required a human to manually open it in a browser. This skill closes that gap: it opens the file itself in a controlled, headless Chrome session, takes a screenshot, reads the console for errors, and optionally runs a Lighthouse audit — then reports a clear verdict.
This skill never navigates to a remote URL and never touches the persistent authenticated browser profile used by browser-gui-inspect. It only ever opens local file:// paths. See specs/048-chrome-devtools-browser-inspection/ for the full spec, research, and design behind this skill.
This skill uses tools provided by the chrome-devtools-mcp server (official Chrome DevTools team package, chrome-devtools-mcp on npm), spawned locally via npx -y chrome-devtools-mcp@latest over stdio transport. See mcp-servers/chrome-devtools-mcp/README.md.
None. chrome-devtools-mcp takes all configuration as CLI flags, not env vars. This skill always runs headless against a local file — it never needs --headless=false or the persistent profile's authenticated sessions.
Input:
file_path (required) — absolute path to the generated visualization HTML filerun_audit (optional, default false) — whether to also run a Lighthouse auditBefore opening a browser session, verify file_path exists on disk. If it does not, stop and return:
verdict: "file_not_found"
Do not attempt to open a browser session for a path that doesn't exist.
Tool: new_page
Args: { "url": "file://<file_path>" }
test cases passed, vs 3 / 16 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.