browse

Automate headless browser QA workflows for web applications across deployments.

Updated Mar 16, 2026

Search Tags:#automation #testing #screenshots #qa #playwright #browser #headless

Ready to run

npx skills add https://github.com/shihwesley/shihwesleys-harness --skill browse-shihwesley

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/shihwesley/shihwesleys-harness/tree/main/skills/gstack/browse
Command: npx skills add https://github.com/shihwesley/shihwesleys-harness --skill browse-shihwesley

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines QA testing by providing a fast, headless browser to navigate URLs, interact with elements, verify page state, and capture evidence for bug reports and deployments.

Core Features & Use Cases

Navigate to URLs and perform interactions (click, fill, type, upload)
Take annotated screenshots and diff page states to document regressions
Validate responsive layouts and form behavior across deployments

Quick Start

Open a URL and run a quick test sequence using goto https://example.com

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 testing for web applications?▼

Automate headless browser testing by navigating to URLs, performing interactions like click and fill, and capturing screenshots to verify page state. You can execute commands like goto, snapshot, and diff to validate feature behavior and document regressions across deployments.

Can I capture visual diffs and screenshots for QA regression checks?▼

Yes, you can capture visual diffs and screenshots for QA regression checks. The skill executes diff and screenshot commands to compare page states, document visual changes, and provide annotated evidence for bug reports across different deployments.

Does this tool support form submissions and responsive layout verification?▼

Yes, this tool supports form submissions and responsive layout verification. You can fill forms, upload files, and validate responsive layouts to ensure web application behavior remains consistent across various deployments and screen dimensions.

How do I maintain session state when running automated QA workflows?▼

Maintain session state during automated QA workflows by executing sequential commands within the headless browser engine. The skill preserves session state across interactions like goto, text, html, and snapshot, enabling continuous feature verification without losing context.

What is the best way to document bugs using a headless browser?▼

The best way to document bugs using a headless browser is to navigate to the URL, interact with elements using ref-based selectors, and capture annotated screenshots or diffs. This provides visual evidence of the page state for bug reports.

Do I need any specific dependencies to run headless browser automation?▼

No specific dependencies are required to run headless browser automation. The skill operates independently with its own headless browser engine to execute commands, navigate URLs, and perform testing workflows without external component installations.