skills.rest
cheng80
cheng80COMMUNITY
Explore all skills by this author →
GitHub

browse

Control a headless Chromium browser to automate QA testing and site dogfooding.

1|Updated Apr 12, 2026
Search Tags:#automation#debugging#web-testing#headless#browse#chromium#qa-testing
One-click install
npx skills add https://github.com/cheng80/rummipoker --skill browse-cheng80
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/cheng80/rummipoker/tree/main/.agents/skills/gstack-browse
Command: npx skills add https://github.com/cheng80/rummipoker --skill browse-cheng80

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Persistent headless browser for QA testing and site dogfooding. It lets you navigate URLs, interact with elements, verify page state, diff before/after actions, take annotated screenshots, check responsive layouts, test forms and uploads, handle dialogs, and assert element states with fast feedback.

Core Features & Use Cases

  • Persistent headless Chromium starts quickly and preserves cookies, tabs, and sessions across commands.
  • Interact with pages via commands like goto, text, click, screenshot, diff, is visible, and form interactions to validate user flows and regressions.
  • Use for bug reproduction, feature verification, and automated QA reports across web apps and demos.

Quick Start

Run the browse skill on a target URL to start testing and automate common QA flows.

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 for web applications?▼

You can automate headless browser QA testing by using commands like goto, click, and snapshot to navigate URLs, interact with UI elements, and verify page loads. This approach allows you to validate user flows and reproduce bugs with fast feedback.

Can I preserve browser sessions and cookies across multiple automated web testing commands?▼

Yes, the headless Chromium browser preserves state including cookies, tabs, and sessions between commands. This allows you to maintain persistent login states across multiple testing steps without needing to re-authenticate.

What do I need to run headless browser testing for site dogfooding?▼

You need a local Chromium-based browser binary and a one-time setup to start the browser. Once initialized, the browser runs headlessly to support commands like goto, text, click, and screenshot for site verification.

How do I take annotated screenshots during automated UI testing?▼

You can take annotated screenshots using the screenshot command to capture page states during testing. This helps document visual regressions and verify responsive layouts across different web app interactions.

Can I test forms and handle dialogs with a headless browser?▼

Yes, the headless browser supports form interactions including testing uploads and handling dialogs. You can use commands to fill forms, submit data, and assert element states to validate complete user workflows.

How do I compare page state diffs before and after UI interactions?▼

You can use the diff command to compare page states before and after actions. This allows you to detect visual or DOM changes during bug reproduction and feature verification across web applications.

Related Skills

Explore More Software Engineering Skills→
henkisdabrohenkisdabro
77

webapp-testing

Automate local web app testing with Playwright and headless Chromium.

Community
Intermediate
jm199seojm199seo

browse

Automate QA browser interactions to validate web workflows and capture evidence.

Community
Advanced
DaviRain-SuDaviRain-Su

gstack

Automate browser-based QA testing with a headless Chromium instance.

Community
Advanced
robertzengcnrobertzengcn

gstack

Control a persistent headless Chromium browser for automated QA testing.

Community
Advanced