browse

Drive a headless browser for QA browsing and dogfooding workflows.

Updated Dec 26, 2025
One-click install
npx skills add https://github.com/tony30552001/Genpic-master --skill browse-tony30552001
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/tony30552001/Genpic-master/tree/main/.agents/skills/gstack/browse
Command: npx skills add https://github.com/tony30552001/Genpic-master --skill browse-tony30552001

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Navigating and testing modern web applications requires reliable, repeatable browser interactions and evidence collection.

Core Features & Use Cases

  • Automates headless browser sessions for QA testing, feature verification, and bug reproduction.
  • Supports navigation, interaction, screenshots, diffs, and state checks across pages and dialogs.
  • Use to dogfood a user flow, verify deployments, or capture evidence with annotated visuals.

Quick Start

Open a URL, interact with elements, and verify results by taking annotated screenshots and diffs.

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 sessions for QA testing and feature verification?

Automate headless browser sessions for QA testing by driving navigation, element interaction, and state validation across pages, forms, and dialogs. This enables repeatable feature verification and bug reproduction in modern web apps.

Can I capture screenshots and perform UI regression checks during automated testing?

Yes, you can capture annotated screenshots and perform visual diffing during automated testing. This supports UI regression checks by providing visual evidence of state changes across pages and dialogs.

What is the best way to dogfood user flows and verify web app deployments?

Dogfood user flows and verify deployments by automating end-to-end browsing workflows with a headless browser. This applies safe defaults and error handling to navigate pages, interact with elements, and validate results.

Does headless browser automation support state validation across complex dialogs and forms?

Headless browser automation supports state validation across complex dialogs and forms. It drives element interactions and verifies results to ensure feature correctness and collect evidence in modern web applications.

Are there limitations when using headless browsing for bug reproduction and evidence collection?

Headless browsing for bug reproduction and evidence collection operates with safe defaults and error handling. It is designed for modern web apps, applying to feature verification and UI regression checks across pages and dialogs.