browse

Drive a Playwright-based browser to navigate URLs, interact with elements, and capture evidence.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/CaltexBevo/ihe-pulse --skill browse-caltexbevo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/CaltexBevo/ihe-pulse/tree/main/.claude/skills/gstack.bak/browse
Command: npx skills add https://github.com/CaltexBevo/ihe-pulse --skill browse-caltexbevo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates QA validation by driving a headless browser to navigate URLs, interact with elements, and capture evidence.

Core Features & Use Cases

  • End-to-end browser automation: Navigate, interact, verify page state, and record evidence across tests.
  • Visual diffs and screenshots: Diff before/after actions and generate annotated screenshots for bug reports.
  • Dogfooding & feature verification: Use in deployment checks and internal QA to validate user flows.

Quick Start

Start a session to validate a feature and capture a screenshot of 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 web testing with a headless browser to capture screenshots?

Automate web testing by driving a headless browser to navigate URLs, interact with elements, and capture annotated screenshots. It supports end-to-end QA workflows with visual diffs and evidence recording across multiple tabs and sessions.

Can I use Playwright for end-to-end QA validation and form testing?

Playwright-based browser automation supports end-to-end QA validation including form tests, dialog handling, and responsive checks. It drives a headless browser to verify page state and record evidence across multiple sessions.

What is the best way to capture visual diffs before and after UI interactions?

Capture visual diffs by using the browser automation tool to compare page states before and after actions. It generates annotated screenshots for bug reports and supports end-to-end testing workflows with evidence recording.

Does headless browser automation support multiple tabs and session management for dogfooding?

Headless browser automation supports multiple tabs and sessions for dogfooding and feature verification. It drives a Playwright-based browser manager to navigate, interact, and verify user flows during deployment checks.

How do I handle dialogs and verify page state during automated QA testing?

Handle dialogs and verify page state by driving the headless browser through end-to-end testing workflows. The Playwright-based manager supports form tests, dialog handling, and responsive checks while capturing audit evidence.

When should I use headless browser automation for deployment checks instead of manual QA?

Use headless browser automation for deployment checks when you need auditable, repeatable feature verification across user flows. It emphasizes safe operation while capturing screenshots and visual diffs that manual QA cannot consistently record.