browse

Name: browse
Availability: InStock
Author: andy-hnu

Automate QA browser tasks and collect annotated screenshots across responsive layouts.

Updated Mar 9, 2026

Search Tags:#testing #e2e #playwright #browser #headless #qa-automation

Ready to run

npx skills add https://github.com/Andy-HNU/AndyClaw --skill browse-andy-hnu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/Andy-HNU/AndyClaw/tree/main/skills/gstack-browse
Command: npx skills add https://github.com/Andy-HNU/AndyClaw --skill browse-andy-hnu

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Automates QA browser tasks and evidence collection.

Core Features & Use Cases

It covers navigating URLs, interacting with page elements, verifying states, diffing outcomes, and producing annotated screenshots across responsive layouts and forms.

Quick Start

Open a URL in the browser and capture a screenshot to verify the UI.

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 QA testing with Playwright?▼

Automate headless browser QA testing by using Playwright to navigate URLs, interact with page elements, verify states, and produce annotated screenshots across responsive layouts for bug reproduction and deployment validation.

Can I capture annotated screenshots across responsive layouts for bug reproduction?▼

Yes, you can capture annotated screenshots across responsive layouts during browser automation to provide visual evidence for bug reproduction and deployment validation.

Does Playwright support diffing outcomes and verifying page element states in e2e tests?▼

Playwright supports diffing outcomes and verifying page element states in e2e tests by automating browser interactions, comparing results, and collecting evidence for QA automation workflows.

What is the best way to validate UI deployments using a headless browser?▼

The best way to validate UI deployments using a headless browser involves navigating target URLs, interacting with page elements, and generating annotated screenshots to verify the application state across responsive layouts.

Do I need YAML frontmatter to run browser automation scripts for QA testing?▼

Yes, the skill requires a YAML frontmatter containing a name and description, alongside optional resources like scripts and assets, to ensure compliant tooling and repeatable QA automation.