skills.rest
I194
I194COMMUNITY
Explore all skills by this author →
GitHub

browse

Automate Playwright/Chromium browser interactions and verify page states.

9|3|Updated Jan 29, 2022
Search Tags:#playwright#web-automation#headless-browser#qa-testing#browser-dogfooding
One-click install
npx skills add https://github.com/I194/PMTools_2.0 --skill browse-i194
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/I194/PMTools_2.0/tree/main/.claude/skills/gstack/browse
Command: npx skills add https://github.com/I194/PMTools_2.0 --skill browse-i194

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The browse skill provides a fast, repeatable way to test and dogfood web deployments by driving a real browser to navigate URLs, interact with elements, and produce evidence such as screenshots and state checks.

Core Features & Use Cases

  • Navigate URLs, interact with elements, verify page state, diff before/after actions, take annotated screenshots, check responsive layouts, test forms and uploads, handle dialogs, and assert element states.
  • Use in deployments to dogfood features, reproduce bugs with evidence, or validate end-to-end user flows.

Quick Start

Open a URL and let the browser automate navigation, interactions, and visual verifications.

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 web deployments to reproduce bugs with evidence?▼

Automated QA testing for web deployments uses a headless browser to navigate URLs, interact with elements, and produce screenshots for bug reproduction. It drives a real browser to validate end-to-end user flows and verify page state.

Does headless browser automation work for verifying responsive layouts and form uploads?▼

Headless browser automation supports verifying responsive layouts, testing forms and uploads, and handling dialogs. It interacts with web elements to assert states and check page conditions across arbitrary URLs.

Can I use Playwright to run end-to-end user-flow verification against arbitrary URLs?▼

Playwright with Chromium runtime enables end-to-end user-flow verification against arbitrary URLs. It automates browser interactions deterministically, applying to feature rollouts and bug reproductions with consistent results.

What's the best way to dogfood web features with deterministic browser results?▼

Dogfooding web features with deterministic results involves configuring a Playwright or Chromium runtime to drive a real browser. This approach navigates URLs, diffs before and after actions, and captures annotated screenshots.

Do I need to configure scripts and assets directories to automate page state checks?▼

Configuring scripts and assets directories is optional but directed by the skill configuration to support page state checks. The browser automation relies on a configured runtime and optional script resources to verify element states.

Why use a headless browser for feature rollouts instead of manual testing?▼

A headless browser for feature rollouts provides fast, repeatable testing by driving a real browser to navigate and interact. It produces visual evidence like annotated screenshots and state checks, ensuring deterministic results.

Related Skills

Explore More Software Engineering Skills→
cshyangcshyang

trigger-config

Configure Trigger.dev projects with trigger.config.ts for build extensions.

Community
Advanced
stravineststravinest

QA Workflow Skill

Automate end-to-end browser QA testing with Playwright and ArangoDB checks.

Community
Advanced
GenEducationGenEducation

browse

Validate web pages and user flows in a live browser with screenshots.

Official
Advanced
vib795vib795

browse

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

Community
Intermediate