browse

Automate QA flows in a headless browser with Playwright.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/pcaokhai/gradion-response-report-api --skill browse-pcaokhai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/pcaokhai/gradion-response-report-api/tree/main/.claude/skills/gstack/browse
Command: npx skills add https://github.com/pcaokhai/gradion-response-report-api --skill browse-pcaokhai

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a persistent, scriptable browser to automate QA tasks, reproduce user flows, and collect evidence for bug reports and deployments.

Core Features & Use Cases

  • Headless navigation and deterministic interactions (clicks, fills, form submissions) for testing.
  • State capture, diffs, and annotated screenshots to validate UI changes and regressions.
  • Evidence generation and logging (console, network, performance) for debugging and audits.

Quick Start

Open a page, perform a sequence of interactions, and capture evidence (screenshots, logs) for QA.

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 for feature deployments using a headless browser?▼

You can automate QA testing by running scriptable headless browser interactions to reproduce user flows, test feature deployments, and validate form workflows across specified URLs.

Can I capture screenshots and console logs for bug reports with Playwright?▼

Yes, you can capture annotated screenshots and generate logs for console, network, and performance metrics to validate UI changes and provide evidence for bug reports.

Do I need Bun installed to run automated browser interactions?▼

Yes, you need Bun installed to execute the scripts that drive the Playwright-backed command surface for dependency management, diffs, and logging.

What is the best way to test responsive layouts across different URLs?▼

The best way to test responsive layouts is to navigate target URLs in a headless browser, perform deterministic interactions, and capture state diffs and snapshots for validation.

How does headless browser automation help reproduce user interactions for UI regressions?▼

Headless browser automation reproduces user interactions like clicks and form fills deterministically, capturing state and annotated screenshots to validate UI changes and detect regressions.