browse

Automate web testing with a persistent headless Chromium browser.

1|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/gth-ai/hadriengayap.github.io --skill browse-gth-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/gth-ai/hadriengayap.github.io/tree/main/.claude/skills/gstack/browse
Command: npx skills add https://github.com/gth-ai/hadriengayap.github.io --skill browse-gth-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill solves the challenge of testing web applications and verifying user flows by providing a persistent, headless Chromium environment that can interact with pages, inspect elements, and capture visual evidence.

Core Features & Use Cases

  • Automated QA Testing: Navigate URLs, fill forms, click elements, and assert page states to verify functionality.
  • Visual Regression: Take annotated screenshots and generate diffs to identify UI changes between environments or actions.
  • Use Case: Use this skill to verify a login flow on a staging environment, check for console errors, and capture a screenshot of the dashboard to confirm successful deployment.

Quick Start

Use the browse skill to navigate to the login page, fill in the email and password fields, and click the submit button to verify the dashboard loads.

Frequently Asked Questions about browse

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

FAQPage Schema
How do I automate web testing with a persistent headless browser?

Automated web testing uses a persistent headless Chromium browser to navigate URLs, fill forms, and click elements. It maintains session state across multiple tabs to validate user flows and assert page states.

Can I capture visual snapshots for UI verification during automated QA testing?

Visual snapshots for UI verification are supported through annotated screenshots. You can capture visual evidence of web pages and generate diffs to identify UI changes between different environments or testing actions.

Does Playwright support maintaining session state for multi-tab user flow validation?

Playwright supports multi-tab user flow validation by maintaining session state in a persistent headless Chromium environment. This allows robust QA workflows that require handling dialogs and interacting across multiple browser tabs.

What's the best way to inspect network requests during automated browser testing?

Network inspection during automated browser testing is handled directly within the headless browser interface. It enables programmatic interaction with DOM elements while capturing network activity across multiple browser tabs.

Can I test responsive layouts and handle dialogs in a headless Chromium environment?

Responsive layout testing and dialog handling are both supported in the headless Chromium environment. It facilitates robust QA workflows by maintaining session state while verifying UI adaptability and managing unexpected browser dialogs.

Do I need Bun installed to run Playwright automated QA scripts?

Bun is required as a dependency to run the Playwright automated QA scripts. The skill relies on this environment to execute the headless browser interface for web testing and user flow validation.