browse

Executes scripted browser interactions to automate web QA workflows.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/brianruggieri/claude-personalities --skill browse-brianruggieri
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/brianruggieri/claude-personalities/tree/main/claude/skills/gstack/browse
Command: npx skills add https://github.com/brianruggieri/claude-personalities --skill browse-brianruggieri

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates browser-based QA workflows by executing scripted interactions against web pages and recording evidence.

Core Features & Use Cases

  • Headless navigation, element interaction, and state assertions to verify user flows.
  • Diffing page output and taking annotated screenshots to document changes.
  • Responsive checks, form and upload testing, and dialog handling for robust QA workflows.

Quick Start

Install the skill and start by issuing a goto command to navigate to a URL.

Frequently Asked Questions about browse

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

FAQPage Schema
How do I automate headless browser QA testing for web apps?

Automate headless browser QA testing by executing scripted interactions against web pages and recording evidence. This approach applies to feature verification, bug repro, and regression testing across web apps, sites, and deployments.

What is the best way to capture evidence during web automation regression testing?

The best way to capture evidence during web automation regression testing is to use scripted commands that take annotated screenshots and diff page output. This documents changes and verifies user flows.

Can I use headless navigation to verify form uploads and dialog handling?

Yes, you can use headless navigation to verify form uploads and dialog handling. Robust QA workflows support responsive checks, form and upload testing, and dialog handling through deterministic scripted actions.

How do I start automating browser interactions for feature verification?

Start automating browser interactions for feature verification by issuing a goto command to navigate to a target URL. This triggers headless navigation, element interaction, and state assertions to verify user flows.

Does web automation testing support state assertions and error handling for bug repro?

Web automation testing supports state assertions and robust error handling for bug repro. It applies deterministic actions and state capture through frontmatter-defined behavior and scripted commands to verify user flows.