skills.rest
psyche911
psyche911COMMUNITY
Explore all skills by this author →
GitHub

browse

Drive a headless browser to verify web app behavior and capture evidence.

Updated Jan 18, 2026
Search Tags:#automation#debugging#qa#playwright#browser-testing#headless-browser
One-click install
npx skills add https://github.com/psyche911/investor-council-app --skill browse-psyche911
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/psyche911/investor-council-app/tree/main/.claude/skills/gstack/browse
Command: npx skills add https://github.com/psyche911/investor-council-app --skill browse-psyche911

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end QA checks by driving a headless browser to verify web app behavior and capture evidence.

Core Features & Use Cases

  • Persistent headless Chromium that runs commands in ~100ms per operation.
  • Capture console, network, and dialog events for debugging and bug reports.
  • Take annotated screenshots, diff page content, and test responsive layouts for various viewports.
  • Use cases include feature verification, deployment dogfooding, and regression testing.

Quick Start

Navigate to a target URL with the browse command to begin testing.

Frequently Asked Questions about browse

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate end-to-end QA testing for web app deployments?▼

Automate end-to-end QA testing by driving a persistent headless Chromium browser to verify web app behavior and capture evidence. It supports feature validation, regression testing, and deployment dogfooding with deterministic command execution.

Can I capture console logs and network events during headless browser testing?▼

Yes, headless browser testing captures console, network, and dialog events for debugging and bug reports. This evidence helps with bug reproduction and feature validation across deployments.

How fast is headless browser automation for QA checks?▼

Headless browser automation runs commands in approximately 100ms per operation using a persistent headless Chromium instance. This provides deterministic command execution and quick setup for test automation.

Does headless browser testing support responsive layout verification for different viewports?▼

Yes, headless browser testing supports responsive layout verification for various viewports. You can take annotated screenshots, diff page content, and test how layouts render across different screen sizes.

What's the best way to reproduce bugs using a headless browser?▼

The best way to reproduce bugs with a headless browser is to drive deterministic command execution against the target URL, capturing console, network, and dialog events alongside annotated screenshots as evidence for bug reports.

Do I need any dependencies to set up headless browser test automation?▼

No external dependencies are required to set up headless browser test automation. The Skill provides quick setup with a persistent headless Chromium instance, enabling you to navigate to a target URL and begin testing immediately.

Related Skills

Explore More Software Engineering Skills→
marchattonmarchatton
5

browser-use

Automate multi-step web workflows with persistent browser sessions via the browser-use CLI.

Community
Intermediate
akiyoshiakiyoshi

qa

Automate end-to-end testing and generate structured QA reports with health scores.

Community
Advanced
yalehyaleh
21

CI/CD Optimization

Automate CI/CD pipelines with quality gates, release automation, and observability.

Community
Advanced
ZESCODEZESCODE

browser-qa

Automate visual regression testing and UI interaction verification for web applications.

Community
Advanced