skills.rest
martin-hsu-test
martin-hsu-testCOMMUNITY
Explore all skills by this author →
GitHub

browse

Automate end-to-end QA interactions in a headless browser to validate web app behavior.

1|Updated Apr 8, 2026
Search Tags:#automation#qa#web-testing#browser#headless#browse#bug-reporting
One-click install
npx skills add https://github.com/martin-hsu-test/gstack-gemini-slim --skill browse-martin-hsu-test
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/martin-hsu-test/gstack-gemini-slim/tree/main/.gemini/skills/gstack-browse
Command: npx skills add https://github.com/martin-hsu-test/gstack-gemini-slim --skill browse-martin-hsu-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA teams need a repeatable, scriptable way to exercise web apps without manual browser clicks.

Core Features & Use Cases

  • Navigate to URLs, interact with elements, and verify page state in deterministic runs.
  • Diff before/after actions and capture annotated screenshots for clear bug reports.
  • Validate responsive layouts, test forms and uploads, handle dialogs, and assert element states across environments.

Quick Start

Open a URL, interact with elements, and verify the resulting page state to validate a feature end-to-end.

Frequently Asked Questions about browse

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

FAQPage Schema
How do I automate web app QA testing without manual browser clicks?▼

Automating web app QA testing requires a headless browser to navigate URLs, interact with elements, and verify page state deterministically. This approach scripts feature validation and user-flow dogfooding without manual interaction.

How do I capture annotated screenshots for bug reporting during end-to-end testing?▼

Capturing annotated screenshots for bug reporting involves diffing before and after actions within a headless browser session. This highlights visual changes and verifies element states to provide clear, reproducible bug reports.

Do I need a local Chromium-based environment to run headless browser automation?▼

Yes, you need a local Chromium-based environment. It provides the deterministic commands, session persistence, and ready-made QA patterns required to execute headless browser automation and validate web app behavior.

Can I validate responsive layouts and handle dialogs in headless web testing?▼

Validating responsive layouts and handling dialogs in headless web testing is achievable by navigating URLs and interacting with elements. It asserts element states across environments to ensure consistent web app behavior.

What is the best way to script user-flow dogfooding for feature validation?▼

The best way to script user-flow dogfooding is using deterministic headless browser commands. This automates end-to-end interactions, captures annotated screenshots, and verifies states across layouts for reliable feature validation.

Why does headless browser testing require session persistence for QA automation?▼

Headless browser testing requires session persistence to maintain state across multiple interactions during QA automation. It ensures deterministic runs when navigating URLs, interacting with elements, and verifying page states.

Related Skills

Explore More Software Engineering Skills→
ShmurdocShmurdoc

setup-browser-cookies

Import authenticated Chromium session cookies into headless Playwright sessions.

Community
Intermediate
2460124601

browse

Automate QA testing by controlling a persistent headless Chromium instance.

Community
Advanced
MathiasPaulenkoMathiasPaulenko

WaveXis Session Recording

Capture and replay browser interactions as YAML sessions via the WaveXis CLI.

Community
Advanced
johan-Rmjohan-Rm

hyperframes-cli

Orchestrate web-based video composition development, validation, and AWS Lambda rendering.

Community
Advanced