browse

Automate web interactions and capture screenshots in a headless browser.

Updated Jun 4, 2026
One-click install
npx skills add https://github.com/burgebj/gstack --skill browse-burgebj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/burgebj/gstack/tree/main/browse
Command: npx skills add https://github.com/burgebj/gstack --skill browse-burgebj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, puppeteer, and includes scripts (resource) and assets (resource) components.

What problem does it solve?

This Skill provides a fast headless browser for QA testing and site dogfooding, allowing users to interact with web pages, verify page states, take screenshots, and more.

Core Features & Use Cases

  • Web Page Navigation and Interaction: Navigate to any URL, interact with elements, and verify page states.
  • Screenshot and Screenshot Comparison: Take screenshots of web pages or compare pages before and after actions.
  • Responsive Layout Testing: Test responsive layouts across different screen sizes and devices.
  • Form Testing: Test form submissions, file uploads, and other interactive elements.
  • Dialog and Modal Testing: Handle dialogs and modals on web pages.
  • Use Case: When you need to test a feature, verify a deployment, dogfood a user flow, or file a bug with evidence.

Quick Start

Use the browse skill to navigate to a URL: browse goto https://yourapp.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 QA and site dogfooding?

Headless browser testing for QA and site dogfooding is automated by navigating to URLs, interacting with elements, and verifying page states. You can capture screenshots, test responsive layouts, and submit forms without a graphical interface.

Can I capture screenshots and test responsive layouts across different screen sizes?

Yes, you can capture screenshots and test responsive layouts across different screen sizes. The headless browser environment handles web interactions, captures page states, and compares screenshots before and after actions.

Do I need Playwright or Puppeteer to run headless browser automation?

Yes, you need Playwright or Puppeteer to run headless browser automation. These dependencies provide the underlying automation framework required to handle web interactions, form submissions, and modal dialogs.

What's the best way to test form submissions and handle modal dialogs automatically?

The best way to test form submissions and handle modal dialogs is using a headless browser environment with Playwright or Puppeteer. These tools automate interactive elements, file uploads, and dialog handling for QA testing.

Does headless browser testing work for verifying deployments and filing bugs with evidence?

Headless browser testing works for verifying deployments and filing bugs with evidence by navigating user flows and capturing screenshots. It validates page states and documents visual errors for bug reports.