browser-test-agent

Automate web browser interactions and quality assurance testing for local development environments.

Updated Jul 18, 2026

Search Tags:#automation #testing #qa #playwright #browser #web

Ready to run

npx skills add https://github.com/arthrod/conejo-skills --skill browser-test-agent

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: browser-test-agent
Source: https://github.com/arthrod/conejo-skills/tree/main/skills/browser-test-agent
Command: npx skills add https://github.com/arthrod/conejo-skills --skill browser-test-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires agent-browser, playwright, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill solves the challenge of verifying web application integrity by automating browser interactions, catching UI regressions, and diagnosing dev-server failures before they reach production.

Core Features & Use Cases

Dev-Server Verification: Automatically probes local dev servers to detect blank pages, console errors, and hydration issues.
Multi-Engine Automation: Provides a choice between a fast Rust-based CLI (agent-browser) for quick checks and a robust Playwright toolkit for complex, multi-context testing.
Use Case: After running a local development server, use this skill to perform a visual gut-check, verify that key interactive elements are rendered, and ensure no error overlays are blocking the user experience.

Quick Start

Use the browser-test-agent to verify the local development server at http://localhost:3000 and report any console errors or UI failures.

Frequently Asked Questions about browser-test-agent

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

FAQPage Schema

How do I automate browser testing to check my local dev server for UI failures?▼

Automate browser testing by probing your local dev server to detect blank pages, console errors, and hydration issues. The skill performs accessibility-tree snapshots and interactive element validation to verify UI integrity.

Can I use Playwright for multi-context web automation and dev-server health checks?▼

Yes, Playwright is supported as a robust toolkit for complex, multi-context web automation. The skill uses Playwright integration to execute interactive element validation and verify key UI components are rendered correctly.

What is the best way to catch web UI regressions before they reach production?▼

The best way to catch UI regressions is automating browser interactions to perform visual gut-checks and verify rendered elements. This diagnostic workflow probes local development environments to ensure no error overlays block the user experience.

Does browser QA testing work with Chrome CDP for accessibility-tree snapshots?▼

Yes, browser QA testing requires Chrome CDP or Playwright integration to execute accessibility-tree snapshots. This allows the automation to validate interactive elements and diagnose dev-server failures effectively.

When should I use a Rust-based CLI over Playwright for web automation?▼

Use a Rust-based CLI for quick web automation checks, while Playwright is better for complex, multi-context testing. The skill provides a multi-engine choice between the fast agent-browser CLI and the robust Playwright toolkit.

Why are my local dev server pages blank when I run automated browser checks?▼

Automated browser checks detect blank pages by probing local dev servers for hydration issues and console errors. The diagnostic workflow reports these UI failures and error overlays to help diagnose the underlying server problem.