browse

Automate headless browser actions for QA testing and site dogfooding.

Updated Feb 24, 2026

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

Ready to run

npx skills add https://github.com/gaaschk/gaasch-family --skill browse-gaaschk

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/gaaschk/gaasch-family/tree/main/.claude/skills/gstack/browse
Command: npx skills add https://github.com/gaaschk/gaasch-family --skill browse-gaaschk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

QA teams frequently need to verify web features across URLs, capture evidence, and reproduce bugs. This Skill provides a fast headless browser to navigate pages, interact with elements, diff outcomes, and generate annotated screenshots for clear bug reports.

Core Features & Use Cases

Navigate to any URL and interact with page elements
Diff before/after actions and verify state changes
Take annotated screenshots and verify responsive layouts
Test forms and uploads, handle dialogs, and assert element states
Use cases include QA verification, deployment testing, and bug repro with visual evidence

Quick Start

Test a feature by opening a URL, interacting with elements, and capturing a screenshot to verify the result.

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 and capture annotated screenshots?▼

Automate headless browser QA testing by navigating URLs, interacting with UI elements, asserting page state, and capturing annotated screenshots. It runs in Playwright-based environments with Bash tooling to deliver repeatable, auditable test results for bug reproduction and validation.

Can I diff before and after UI actions to verify state changes during deployment testing?▼

Yes, you can diff before and after actions to verify state changes during deployment testing. The Skill navigates pages, interacts with elements, and generates visual evidence to accelerate bug reproduction and validate that features work correctly.

Does this Playwright-based automation tool support testing forms, uploads, and responsive layouts?▼

Yes, this Playwright-based automation supports testing forms and uploads, handling dialogs, asserting element states, and verifying responsive layouts. It captures annotated screenshots to provide clear visual evidence for QA verification.

What is the best way to reproduce bugs with visual evidence using a headless browser?▼

The best way to reproduce bugs with visual evidence is using a fast headless browser to navigate URLs, interact with elements, and capture annotated screenshots. This delivers repeatable, auditable test results that accelerate bug validation and reporting.

Do I need a Playwright environment to run automated QA testing scripts?▼

Yes, you need a Playwright-based environment with Bash tooling to run automated QA testing scripts. The Skill relies on this setup to navigate pages, interact with UI elements, and capture annotated screenshots for auditable test results.