skills.rest
jm199seo
jm199seoCOMMUNITY
Explore all skills by this author →
GitHub

browse

Automate QA browser interactions to validate web workflows and capture evidence.

Updated Mar 22, 2026
Search Tags:#automation#diff#playwright#browser#screenshot#snapshot#qa-testing
One-click install
npx skills add https://github.com/jm199seo/lostark-accessory-viewer --skill browse-jm199seo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/jm199seo/lostark-accessory-viewer/tree/main/.claude/skills/gstack/browse
Command: npx skills add https://github.com/jm199seo/lostark-accessory-viewer --skill browse-jm199seo

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

The Skill provides a repeatable, headless browser for QA testing, enabling you to navigate, interact with pages, and collect evidence for bug reports.

Core Features & Use Cases

  • Navigate to URLs and interact with page elements
  • Diff state changes and capture annotated screenshots
  • Validate responsive layouts, forms, and dialogs across deployments
  • Use for feature verification, deployments, and bug reproduction with evidence

Quick Start

Open a test URL and capture an annotated 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 for web workflows?▼

Automated QA testing uses a headless Playwright environment to validate web workflows, interact with elements, and capture evidence like screenshots and diffs for bug reports.

Can I capture screenshots and diff state changes during Playwright automation?▼

Yes, Playwright automation captures annotated screenshots and diffs state changes during navigation. This provides visual evidence and validates UI modifications for bug reproduction.

Do I need a specific environment to run headless browser automation for QA testing?▼

You need a headless Playwright-enabled environment with dependencies including bun and perl. These execute scripts that validate responsive layouts, forms, and dialogs.

How do I validate responsive layouts and forms across deployments?▼

Validate responsive layouts and forms by automating browser interactions across deployments. The automation navigates URLs, checks element states, and returns diffs to verify UI consistency.

What is the best way to collect evidence for bug reproduction in web applications?▼

Collect evidence for bug reproduction by running automated headless browser scripts that return navigations, annotated screenshots, and element state checks to document the exact failure point.

Does automated browser testing work for deployment verification?▼

Automated browser testing works for deployment verification by navigating to URLs and validating page elements. It returns screenshots and diffs to confirm the deployment did not break workflows.

Related Skills

Explore More Software Engineering Skills→
quiznatquiznat

headless-browser-setup

Installs Playwright Chromium and OS libraries to fix Hermes browser access on headless Linux servers.

Community
Advanced
JaykaijackJaykaijack

browse

Automate headless Chromium browsing and UI verification with screenshots and diffs.

Community
Advanced
ComputerConnectionComputerConnection

browse

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

Community
Advanced
tsenseitsensei
3

gstack

Drive a headless browser to interact with UI and capture annotated screenshots and diffs.

Community
Advanced