browse

Drive a headless Chromium browser to load pages, interact with elements, and verify states.

5|1|Updated Feb 12, 2026

Search Tags:#automation #screenshots #verification #headless #browse #chromium #qa-testing

Ready to run

npx skills add https://github.com/drt0927/tw-overlay --skill browse-drt0927

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/drt0927/tw-overlay/tree/main/.gemini/skills/gstack-browse
Command: npx skills add https://github.com/drt0927/tw-overlay --skill browse-drt0927

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA teams need a persistent, headless browser to run reliable web tests without manual setup.

Core Features & Use Cases

Navigate to a URL and interact with elements to verify page state.
Capture annotated screenshots, perform diffs, and validate UI responses across layouts.
Reproduce user flows, validate dialogs, forms, and state persistence for regression testing.

Quick Start

Use browse to navigate to a URL and capture an annotated screenshot 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 headless browser QA testing for web applications?▼

Headless browser QA testing automates a headless Chromium backend to load pages, perform DOM interactions, and verify page states for feature validation and regression checks across web apps.

Can I capture annotated screenshots during automated UI verification?▼

Yes, automated UI verification supports capturing annotated screenshots, performing visual diffs, and validating UI responses across responsive layouts, forms, and dialogs.

Does headless Chromium support reproducing user flows for regression testing?▼

Headless Chromium supports reproducing user flows by driving deterministic commands to interact with elements, validate dialogs, and check state persistence for regression testing.

What is the best way to validate forms and dialogs without manual browser setup?▼

Validating forms and dialogs without manual setup uses a persistent headless browser to execute deterministic commands, interact with DOM elements, and assert expected UI states automatically.

Are there limitations when using a headless browser for responsive layout testing?▼

Headless browser responsive layout testing applies to feature validation and UI verification, but requires deterministic commands and state persistence configurations to ensure reliable regression checks.