
Agent Browser Verify
Automatically open the running dev server in agent-browser to confirm the page renders, catch console errors, and flag broken UI before you keep coding.
Install
npx skills add https://github.com/vercel-labs/vercel-plugin --skill agent-browser-verifyWhat is this skill?
- Triggers on common dev commands: next dev, npm run dev, vite, vercel dev, and similar bash patterns
- Runs agent-browser visual gut-check when a dev server starts (metadata priority 2)
- Validates page load, console errors, and key UI elements with pass/fail reporting
- Responds to prompt signals like blank page, white screen, spinner not stopping, and UI is broken
- Designed as automated verification before the agent continues implementation work
Adoption & trust: 69 installs on skills.sh; 187 GitHub stars; 3/3 security scanners passed (skills.sh audits).
Recommended Skills
Agent Browservercel-labs/open-agents
Tddmattpocock/skills
Use My Browserxixu-me/skills
Test Driven Developmentobra/superpowers
Verification Before Completionobra/superpowers
Webapp Testinganthropics/skills
Journey fit
Primary fit
Automated visual gut-checks are a ship-phase testing gate, though they fire whenever a dev server starts during Build. Browser verification, console error scanning, and pass/fail reporting map directly to QA testing, not launch SEO or operate monitoring.
Common Questions / FAQ
Is Agent Browser Verify safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.
SKILL.md
READMESKILL.md - Agent Browser Verify
# Dev Server Verification with agent-browser **You MUST verify the dev server with agent-browser after starting it.** Do not assume the page works just because the dev server process started. Many issues (blank pages, hydration errors, missing env vars, broken imports) are only visible in the browser. Run this verification before continuing with any other work: ## Quick Verification Flow ```bash # 1. Open the dev server agent-browser open http://localhost:3000 agent-browser wait --load networkidle # 2. Screenshot for visual check agent-browser screenshot --annotate # 3. Check for errors agent-browser eval 'JSON.stringify(window.__consoleErrors || [])' # 4. Snapshot interactive elements agent-browser snapshot -i ``` ## Verification Checklist Run each check and report results: 1. **Page loads** — `agent-browser open` succeeds without timeout 2. **No blank page** — snapshot shows meaningful content (not empty body) 3. **No error overlay** — no Next.js/Vite error overlay detected 4. **Console errors** — evaluate `document.querySelectorAll('[data-nextjs-dialog]')` for error modals 5. **Key elements render** — snapshot `-i` shows expected interactive elements 6. **Navigation works** — if multiple routes exist, verify at least the home route ## Error Detection ```bash # Check for framework error overlays agent