browse

Name: browse
Availability: InStock
Author: scanbott

Automate QA browser actions and capture evidence across pages in headless mode.

Updated Apr 21, 2026

Search Tags:#automation #testing #qa #diff #browser #headless #screenshot

Ready to run

npx skills add https://github.com/scanbott/claude-skills --skill browse-scanbott

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a fast, persistent headless browser for QA testing and dogfooding. It enables navigations, interactions, and verifications across pages, capturing evidence like screenshots and diffs to accelerate bug reports and deployment validation.

Core Features & Use Cases

Automated QA flows: Navigate URLs, interact with elements, verify states, and diff before/after actions.
Evidence capture: Take annotated screenshots, diff outputs, and responsive checks to document behavior.
Dogfooding & deployment QA: Reproduce user flows end-to-end to validate features post-deploy and collect test evidence.

Quick Start

Open a URL, run a test flow, and capture evidence with a screenshot.

Frequently Asked Questions about browse

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

FAQPage Schema

How do I run automated QA tests in a headless browser?▼

Automated QA tests in a headless browser run by navigating URLs, interacting with elements, and verifying states deterministically to capture evidence like screenshots and diffs for bug reports.

What is headless browser testing used for in deployment validation?▼

Headless browser testing for deployment validation reproduces user flows end-to-end post-deploy, capturing annotated screenshots and diffs to confirm features behave correctly before release.

Can I capture screenshots and diffs during automated browser interactions?▼

Screenshots and diffs during automated browser interactions capture visual evidence of page states before and after actions, accelerating bug reporting and responsive behavior checks.

Does headless QA testing support deterministic navigation and element interaction?▼

Headless QA testing supports deterministic navigation and element interaction by targeting specific page elements, verifying resulting states, and reporting outcomes consistently across test runs.

What's the best way to verify page state changes after UI interactions?▼

Verifying page state changes after UI interactions is best done by diffing outputs before and after actions, capturing annotated screenshots to document behavior shifts and report outcomes.

When do I need a headless browser for dogfooding and QA flows?▼

A headless browser for dogfooding and QA flows is needed when you must reproduce user journeys end-to-end, interact with elements, and collect test evidence without a visible browser window.