skills.rest
jeisenback
jeisenbackCOMMUNITY
Explore all skills by this author →
GitHub

browse

Operate a persistent headless browser to automate web QA workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automate browser-based QA tasks by providing a persistent headless browser and a rich command surface.

Core Features & Use Cases

  • Stateful headless browser sessions for repeatable QA flows, including navigation, interaction, and state preservation.
  • Rich command surface to perform page actions, capture screenshots, diff outputs, and generate accessibility snapshots for bug reports.
  • Use cases include verifying deployments, reproducing bugs with visual evidence, and dogfooding user flows in CI or dev environments.

Quick Start

Start the browser, navigate to a page, run interactions, and capture evidence with screenshots or diffs.

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 with a headless browser to verify web app features?▼

Automate QA testing by starting a persistent headless browser, navigating to live web pages, running interactions, and capturing screenshots as visual evidence for feature verification.

Can I preserve browser state across multiple navigation steps for regression checks?▼

Yes, the headless browser maintains stateful sessions that preserve state across navigation and interaction steps, enabling repeatable QA flows and reliable regression checks.

How do I capture visual evidence like screenshots or diffs when reproducing bugs?▼

Capture visual evidence for bug reproduction by navigating to the target page, triggering the interaction, and using the command surface to generate screenshots, accessibility snapshots, or diffs.

What's the best way to dogfood user flows in a development environment?▼

Dogfood user flows by deploying a persistent headless browser to navigate and interact with your live web application, verifying deployments through automated stateful sessions.

Does this browser automation tool work without external dependencies?▼

Yes, the browser automation skill operates with zero external dependencies, providing a self-contained command surface for navigation, interaction, and evidence capture.

Why use a stateful headless browser instead of stateless page requests for testing?▼

A stateful headless browser preserves session data across interactions, allowing complex multi-step QA workflows and accurate bug reproduction that stateless page requests cannot achieve.

Related Skills

Explore More Software Engineering Skills→
ManzuetiManzueti

browse

Automate web application navigation, interaction, and verification with a headless browser.

Community
Advanced
tilework-techtilework-tech
149

webapp-testing

Automate web application end-to-end testing with Python Playwright.

Official
Advanced
anouar1991anouar1991
1

visual-regression-cinema

Record browser interactions and generate a filmstrip of visual transitions.

Community
Advanced
giuseppe-trisciuogliogiuseppe-trisciuoglio
322

unit-test-wiremock-rest-api

Mock REST API endpoints with WireMock and JUnit 5 for unit tests.

Community
Intermediate