browse

Drive a headless browser to automate QA page interactions, assertions, and visual diffs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

QA teams need a fast, repeatable way to exercise web apps without manual clicking. The browse skill provides a headless browser that can navigate URLs, interact with elements, verify states, and capture annotated evidence to support bug reports and deployment validation.

Core Features & Use Cases

  • Navigate to URLs and interact with page elements
  • Verify visibility, text, forms, dialogs, and responsive layouts
  • Capture annotated screenshots and diffs for evidence and comparisons
  • Reproduce user flows for regression testing and dogfooding

Quick Start

Start a headless browse session against a target URL and begin interacting with the page to verify behavior.

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?

Headless browser QA testing automates web app interactions by driving page navigation, element clicks, and state assertions without manual input. This skill navigates URLs, verifies visibility and forms, and captures annotated screenshots for bug reports.

Can I use headless browsing to reproduce user flows for regression testing?

Yes, headless browsing reproduces user flows for regression testing by scripting sequential page interactions and capturing visual diffs. This skill persists session cookies, handles errors, and validates responsive layouts across diverse sites and devices.

What is the best way to capture visual diffs during web automation?

Capturing visual diffs during web automation requires navigating a headless browser to the target URL and screenshotting the rendered state. This skill captures annotated screenshots to compare layout changes and support deployment validation evidence.

Does headless web testing support state persistence and session cookies?

Headless web testing supports state persistence by retaining session cookies and local storage across navigated pages. This skill implements cookie persistence to maintain authenticated sessions during extended feature verification and dogfooding tasks.

How do I verify responsive layouts and dialogs across different devices?

Verifying responsive layouts and dialogs across devices uses a headless browser to emulate screen sizes and assert element visibility. This skill drives page interactions to confirm forms, dialogs, and text render correctly for QA testing.