skills.rest
studyzy
studyzyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

browse

Automate end-to-end QA browser testing with Playwright and capture screenshots.

Updated Mar 21, 2026
Search Tags:#automation#screenshots#qa#diff#playwright#browser
One-click install
npx skills add https://github.com/studyzy/dev-agent-protocol --skill browse-studyzy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/studyzy/dev-agent-protocol/tree/main/.claude/skills/gstack/browse
Command: npx skills add https://github.com/studyzy/dev-agent-protocol --skill browse-studyzy

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Provides a fast, self-contained headless browser environment to automate QA testing, capture evidence, and reproduce issues without manual steps.

Core Features & Use Cases

  • Navigate to URLs, interact with elements, verify page state, diff before/after actions, and capture annotated screenshots.
  • Test forms, uploads, and dialogs; verify element states; and check responsiveness across mobile, tablet, and desktop layouts.
  • Use cases include testing new deployments, validating bug fixes, and dogfooding user flows with evidence for bugs.

Quick Start

Start by launching a session, navigate to a page, and capture a screenshot to prove the result.

Frequently Asked Questions about browse

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

FAQPage Schema
How do I automate end-to-end QA testing for web apps?▼

Automate end-to-end QA testing by using a Playwright-based headless browser to navigate URLs, interact with elements, and verify page state. This allows you to validate feature deployments and reproduce bugs without manual steps.

Can I capture screenshots and visual diffs during browser automation?▼

Yes, you can capture annotated screenshots and generate visual diffs before and after actions during browser automation. This provides concrete evidence for bug reproduction, feature verification, and deployment dogfooding.

Does this headless browser environment support testing mobile and tablet layouts?▼

Yes, the headless browser environment supports checking responsiveness across mobile, tablet, and desktop layouts. You can verify element states and validate user flows across different viewport sizes.

What do I need to run a Playwright-based headless browser for QA testing?▼

You need a self-contained environment with Bun, Perl, and Curl installed to run this Playwright-based headless browser. These dependencies support the command API and script references required for session automation.

How do I test forms, uploads, and dialogs in a headless browser?▼

Test forms, uploads, and dialogs by launching a session in the headless browser and using the command API to interact with these elements. You can verify element states and capture screenshots to prove the results.

Related Skills

Explore More Software Engineering Skills→
XinheLIUXinheLIU

browse

Operate a persistent headless Chromium browser for QA testing and site dogfooding.

Community
Advanced
olaafrossiolaafrossi
10

gstack

Automate QA browser sessions with a persistent headless browser.

Community
Advanced
Michae2xlMichae2xl

e2e-testing

Automate end-to-end web application testing with Playwright and Page Object Model.

Community
Advanced
Luqman-Ud-DinLuqman-Ud-Din

qa-detect-network-errors

Capture HTTP error responses and failed network requests during Playwright browser navigation.

Community
Intermediate