agent-browser-verify

Automate visual verification of dev servers by checking page load, console errors, and UI elements.

246|42|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/vercel/vercel-plugin --skill agent-browser-verify-vercel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-browser-verify
Source: https://github.com/vercel/vercel-plugin/tree/main/skills/agent-browser-verify
Command: npx skills add https://github.com/vercel/vercel-plugin --skill agent-browser-verify-vercel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automated browser verification for dev servers ensures that when a local server starts, the UI loads correctly, there are no console errors, and key UI elements render before continuing.

Core Features & Use Cases

  • Dev-Server Gut-Check: opens the app in a browser, waits for the page to load, and captures a quick visual pass.
  • Error Detection: checks for console errors and runtime overlays.
  • UI Validation: confirms essential UI elements are present and usable.
  • Automated Reporting: returns pass/fail status to guide subsequent steps.

Quick Start

Start the dev server and run the agent-browser-verify flow against the local URL to perform a visual gut-check and ensure the page loads without errors.

Frequently Asked Questions about agent-browser-verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate visual verification for a running dev server?

Automated browser verification opens your dev server in a browser, waits for the page to load, checks for console errors, and confirms key UI elements render correctly before returning a pass or fail status.

What is a browser gut-check and when do I need it?

A browser gut-check is an automated visual verification step that opens your local app to validate page loads and capture runtime errors. You need it during local development and CI checks to ensure pages render correctly.

How do I check for console errors and UI validation during local development?

Automated browser verification checks for console errors and runtime overlays during local development by opening the app in a browser, confirming essential UI elements are present, and returning a pass or fail status.

Can I use automated browser verification for CI checks across common frameworks?

Yes, automated browser verification validates that pages render correctly across common frameworks and routes during CI checks by enforcing dev server triggers, executing a visual gut-check, and reporting pass or fail results.

Do I need a specific dev server setup to run automated browser verification?

You need a running dev server at a local URL. The automated verification flow enforces triggers for starting the dev server and then runs the browser gut-check against that local URL to validate page loads and UI elements.

What is the best way to validate that a local server starts and the UI loads correctly?

Automated browser verification is the best way to validate that a local server starts and the UI loads correctly, as it checks page load status, detects console errors, and confirms essential UI elements render before allowing subsequent steps.