agent-browser-verify

Automate visual and functional verification of web development servers via browser state and console output.

2|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/NagyVikt/codex-plugins --skill agent-browser-verify-nagyvikt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-browser-verify
Source: https://github.com/NagyVikt/codex-plugins/tree/main/plugins/vercel/skills/agent-browser-verify
Command: npx skills add https://github.com/NagyVikt/codex-plugins --skill agent-browser-verify-nagyvikt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the common issue of silent failures in web development where a server process starts successfully, but the actual page is broken, blank, or throwing console errors.

Core Features & Use Cases

  • Visual Gut-Check: Automatically captures screenshots and snapshots of the rendered UI to ensure the page is not blank or stuck.
  • Error Detection: Evaluates the browser console and DOM for error overlays, hydration issues, or missing content.
  • Workflow Integration: Provides a structured diagnostic path to correlate browser-side failures with server-side logs, helping developers debug faster.

Quick Start

Use the agent-browser-verify skill to perform a full visual and functional check on the currently running development server.

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 frontend dev server?

Detect frontend console errors by evaluating the browser console output and scanning the DOM for error overlays or hydration issues. This skill correlates these client-side errors with backend logs to accelerate web debugging.

What is the best way to debug silent failures where a web server runs but the page is blank?

Debug silent web server failures by running an automated visual gut-check that captures screenshots of the rendered UI. This verification process detects blank pages, stuck loading states, and missing content immediately after server startup.

Do I need browser automation tools to verify UI elements and error overlays?

Yes, browser automation tools are required to validate UI elements, inspect the DOM for error overlays, and capture screenshots. This skill relies on browser automation to perform functional and visual checks on running development servers.

How do I correlate client-side hydration issues with backend server logs?

Correlate client-side hydration issues with backend logs by following a structured diagnostic path. The skill evaluates browser console errors and maps them to server-side logs, helping developers pinpoint the root cause of frontend rendering failures.

What are the limitations of automated browser state inspection for frontend debugging?

Automated browser state inspection is limited to evaluating the rendered DOM, browser console output, and UI snapshots. It cannot detect underlying infrastructure failures or network latency issues unless they trigger visible client-side errors.