browse

Name: browse
Availability: InStock
Author: vibrationalforce

Drive headless Chromium to load pages, simulate actions, and capture artifacts.

Updated Oct 15, 2025

Search Tags:#automation #qa #diff #playwright #screenshot #browse

Ready to run

npx skills add https://github.com/vibrationalforce/Echoelmusic --skill browse-vibrationalforce

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/vibrationalforce/Echoelmusic/tree/main/.claude/skills/gstack/browse
Command: npx skills add https://github.com/vibrationalforce/Echoelmusic --skill browse-vibrationalforce

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end web UI verification by driving a headless browser to navigate, interact with pages, and collect evidence (screenshots, diffs, logs) to accelerate QA, bug reproduction, and deployments.

Core Features & Use Cases

Navigate, interact with elements, capture annotated screenshots, and diff before/after states to verify deployments and user flows.
Inspect page state, forms, accessibility, and network activity to reproduce issues and validate fixes.
Use cases include feature verification on staging, regression checks after changes, and generating evidence packs for bug reports.

Quick Start

Run a quick smoke test of a URL and save a full-page screenshot for evidence.

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 testing for feature verification?▼

Automate headless browser testing by driving a Chromium instance to load pages, simulate user actions like clicks and form fills, and gather artifacts such as screenshots and diffs for QA verification. This harness produces repeatable results for feature checks and bug reporting.

Can I capture screenshots and diff page states with Playwright automation?▼

Yes, you can capture annotated full-page screenshots and diff before-and-after page states using Playwright automation commands. This enables visual verification of deployments and user flows for bug reproduction and evidence generation.

Does headless browser testing work for inspecting page accessibility and network activity?▼

Headless browser testing inspects page state, forms, accessibility, and network activity to reproduce issues and validate fixes. It executes commands covering navigation, snapshotting, and interaction to collect comprehensive QA evidence.

Do I need a Playwright server integration to run browser automation for regression checks?▼

Yes, you need Playwright-based server integration and a stable command surface to run browser automation for regression checks. This setup ensures deterministic execution of navigation and interaction commands to produce repeatable results.

What is the best way to generate evidence packs for bug reports from a headless browser?▼

Generate evidence packs for bug reports by running a headless browser test harness that navigates URLs, simulates user actions, and captures annotated screenshots, diffs, and logs. This validates fixes and accelerates deployment verification.

Why are my headless browser automation commands not producing repeatable results?▼

Commands may not produce repeatable results if the Playwright-based server integration lacks a stable command surface for actions like goto, click, fill, and snapshot. Consistent execution requires deterministic browser control and artifact gathering.