browse

Run a persistent headless Chromium browser to test web flows and collect evidence.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The GStack browse skill provides a fast, persistent, programmable browser to automate QA, verify deployments, and dogfood features without manual testing. It eliminates repetitive checks by letting you navigate, interact, and observe page state in a repeatable way.

Core Features & Use Cases

  • Navigate to URLs, interact with elements, verify states, diff before/after actions, and take annotated screenshots.
  • Test forms, uploads, dialogs, and responsive layouts with automated checkpoints across multi-tab sessions.
  • Use for QA pipelines, bug reproduction, and evidence collection during product validation.

Quick Start

Open a URL with goto, inspect page content with text or html, and capture evidence with screenshot.

Frequently Asked Questions about browse

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

FAQPage Schema
How do I automate QA testing with a headless browser?

Automate QA testing with a headless browser by running a persistent Chromium instance to navigate URLs, interact with elements, verify page states, and capture annotated screenshots for evidence collection.

What is the best way to capture screenshots during web testing?

The best way to capture screenshots during web testing is using an automated headless browser that navigates flows and records visual evidence at specific checkpoints across single or multiple tabs.

Can I test forms and responsive layouts across multiple tabs?

Yes, you can test forms, uploads, dialogs, and responsive layouts across multi-tab sessions by running automated checkpoints that interact with elements and verify states in both headless and headed modes.

Does this headless browser support diffing before and after actions?

Yes, the headless browser supports state diffing before and after actions, allowing you to observe page state changes interactively and verify deployment outcomes without manual checks.

When should I use a persistent headless browser for web testing?

Use a persistent headless browser for web testing when you need to automate repetitive QA pipelines, reproduce bugs, or collect product validation evidence in a repeatable way without manual testing.