browse

Drive a persistent headless Chromium browser to automate QA testing tasks.

Updated Feb 27, 2026
One-click install
npx skills add https://github.com/abustamam/portfolio-blog --skill browse-abustamam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/abustamam/portfolio-blog/tree/main/.claude/skills/gstack/browse
Command: npx skills add https://github.com/abustamam/portfolio-blog --skill browse-abustamam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a persistent, headless Chromium browser that you can drive with commands to automate QA testing, feature verification, and bug repro without reinitializing a browser for every test run.

Core Features & Use Cases

  • Persistent browser session across commands (cookies, tabs, login state)
  • Rich QA patterns: goto, text, html, click, fill, snapshot, network/log capture, and screenshots
  • Ideal for feature verification, regression testing, and bug reproduction with automated evidence

Quick Start

Launch the skill and run a short sequence that navigates to a page, clicks a button, and captures a screenshot for validation.

Frequently Asked Questions about browse

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

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

Automate QA testing by driving a persistent headless Chromium browser that maintains cookies, tabs, and login state across commands. It supports navigation, element interaction, and state capture for debugging without reinitializing the browser for every test run.

Can I capture screenshots and network logs during bug reproduction?

Yes, you can capture screenshots and network logs during bug reproduction. The runtime supports rich QA patterns including goto, click, fill, snapshot, and network capture to generate automated evidence for debugging workflows.

Does this QA automation skill require a Playwright runtime?

Yes, this QA automation skill requires a Playwright-based runtime. It relies on Playwright to drive the headless Chromium browser, execute command dispatch, handle errors robustly, and preserve session state across multiple testing commands.

What's the best way to maintain login state across regression testing sessions?

Maintain login state across regression testing sessions by using a persistent browser session. The headless browser preserves cookies, tabs, and authentication tokens between commands, eliminating the need to reinitialize or re-authenticate for subsequent test runs.

Why does my browser session reset between feature verification commands?

Browser sessions should not reset between feature verification commands. The persistent headless browser is designed to maintain state, but if resets occur, verify your Playwright runtime configuration and error handling logic to ensure session preservation is functioning correctly.