How do I install the Web Verify skill?

Run npx skillmds@latest add jeffweisbein/web-verify in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Web Verify safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Web Verify?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Web Verify free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Web Verify?

jeffweisbein (@jeffweisbein) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Web Verify by jeffweisbein — Agent Skill

Name: Web Verify
Author: jeffweisbein

Web Verify

Browser-driven smoke test. Drive a real browser through a deployed web app, capture screenshots + console/network errors, return deterministic pass/fail. Use after a deploy to prove the live app actually works (not just returns 200), or to verify a preview URL before merge. The teeth behind the ship-loop smoke step.

jeffweisbein Updated Sep 22, 2026

File contents

web-verify

Runs a real Chromium browser through a flow spec against a live or preview URL and returns pass/fail with screenshot evidence. This is what catches render bugs, broken auth redirects, dead buttons, and client-side exceptions that a curl check sails past.

Lives at managed/tools/web-verify. One-time setup: cd managed/tools/web-verify && npm install.

Run a flow

node managed/tools/web-verify/verify.mjs managed/tools/web-verify/flows/<flow>.json

Point it at a preview deploy instead of prod with --base:

node managed/tools/web-verify/verify.mjs flows/<flow>.json --base https://preview.example.com

Logged-in flow (reuses a Chrome profile set via WV_AUTH_PROFILE):

WV_AUTH_PROFILE="$HOME/path/to/chrome-profile" node .../verify.mjs flows/<flow>.json --auth

If your agent's compute lives on a remote box, run the same command over SSH there.

Reading the result

Exit 0 = pass, exit 1 = fail. Check $?.
Result JSON prints to stdout and saves to runs/<name>-<ts>/result.json.
Key fields: ok, failures[], pageErrors[], consoleErrors[], networkErrors[], screenshots[].
Screenshots are the evidence — pull the FAIL-*.png or final frame back to show what the page looked like.

Adding a flow for an app

Drop a JSON spec in flows/. Schema + step reference in README.md. Start from flows/example-home.json (public) or flows/example-login.json (authed). Keep assertions on stable copy or test ids, not brittle layout selectors. Minimum useful smoke: goto the page, one or two expectText on hero copy, a screenshot.

Ship-loop integration

The ship-loop's smoke step should call web-verify against the deployed URL after the host reports ready:

Deploy lands ("Ready").
node verify.mjs flows/<app>.json --base <deployed-url>
Exit 0 → report success + attach the final screenshot. Exit 1 → block the "done" claim, surface failures[] + the FAIL-* screenshot.

---name: web-verifydescription: Browser-driven smoke test. Drive a real browser through a deployed web app, capture screenshots + console/network errors, return deterministic pass/fail. Use after a deploy to prove the live app actually works (not just returns 200), or to verify a preview URL before merge. The teeth behind the ship-loop smoke step.---# web-verifyRuns a real Chromium browser through a **flow spec** against a live or preview URL andreturns pass/fail with screenshot evidence. This is what catches render bugs, brokenauth redirects, dead buttons, and client-side exceptions that a `curl` check sails past.Lives at `managed/tools/web-verify`. One-time setup: `cd managed/tools/web-verify && npm install`.## Run a flow```bashnode managed/tools/web-verify/verify.mjs managed/tools/web-verify/flows/<flow>.json```Point it at a preview deploy instead of prod with `--base`:```bashnode managed/tools/web-verify/verify.mjs flows/<flow>.json --base https://preview.example.com```Logged-in flow (reuses a Chrome profile set via `WV_AUTH_PROFILE`):```bashWV_AUTH_PROFILE="$HOME/path/to/chrome-profile" node .../verify.mjs flows/<flow>.json --auth```If your agent's compute lives on a remote box, run the same command over SSH there.## Reading the result- **Exit 0** = pass, **exit 1** = fail. Check `$?`.- Result JSON prints to stdout and saves to `runs/<name>-<ts>/result.json`.- Key fields: `ok`, `failures[]`, `pageErrors[]`, `consoleErrors[]`, `networkErrors[]`, `screenshots[]`.- Screenshots are the evidence — pull the `FAIL-*.png` or `final` frame back to show what the page looked like.## Adding a flow for an appDrop a JSON spec in `flows/`. Schema + step reference in `README.md`. Start from`flows/example-home.json` (public) or `flows/example-login.json` (authed). Keepassertions on **stable copy or test ids**, not brittle layout selectors. Minimum usefulsmoke: `goto` the page, one or two `expectText` on hero copy, a `screenshot`.## Ship-loop integrationThe ship-loop's smoke step should call web-verify against the deployed URL after thehost reports ready:1. Deploy lands ("Ready").2. `node verify.mjs flows/<app>.json --base <deployed-url>`3. Exit 0 → report success + attach the `final` screenshot. Exit 1 → block the "done" claim, surface `failures[]` + the `FAIL-*` screenshot.

Frequently asked questions