skills.rest
curielmc
curielmcCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

browse

Automate browser-based QA tasks with a persistent headless browser.

Updated Feb 27, 2026
Search Tags:#automation#testing#qa#playwright#browser#headless#web
One-click install
npx skills add https://github.com/curielmc/beat-SPY --skill browse-curielmc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/curielmc/beat-SPY/tree/main/.claude/skills/gstack/browse
Command: npx skills add https://github.com/curielmc/beat-SPY --skill browse-curielmc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bun, perl, and includes scripts (resource) components.

What problem does it solve?

This Skill automates repetitive browser-based QA tasks and site dogfooding by providing a persistent headless browser that can navigate URLs, interact with elements, verify page state, and capture annotated evidence for bugs or deployments.

Core Features & Use Cases

  • Persistent headless browser that can start, maintain sessions (cookies, tabs), and perform deterministic actions.
  • Navigate to URLs, interact with elements, verify element states, diff before/after actions, and capture annotated screenshots.
  • Ideal for feature verification, deployment validation, bug reproduction, and end-to-end QA dogfooding.

Quick Start

Open a URL and perform a basic QA action to verify a feature end-to-end.

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 QA tasks for deployment validation?▼

Headless browser QA automation validates deployments by navigating URLs, interacting with elements, verifying page state, and capturing annotated screenshots for bug reproduction.

Can I maintain persistent browser sessions and tabs for end-to-end testing?▼

Persistent browser sessions maintain cookies and tabs across end-to-end testing, supporting deterministic actions, state verification, and repeatable tests for feature verification.

Do I need Bun and Perl installed to run automated web testing scripts?▼

Bun and Perl are required dependencies to execute the automated web testing scripts that drive the headless browser, handle telemetry, and manage session state.

What is the best way to capture annotated evidence for bug reproduction during web automation?▼

The best way to capture annotated evidence for bug reproduction during web automation is using a scriptable headless browser to diff before and after actions, then capture annotated screenshots.

Does headless browser automation work for visual diffs and element state verification?▼

Headless browser automation performs visual diffs and element state verification by interacting with page elements, checking states, and logging telemetry across persistent sessions.

Why use a scriptable API for site dogfooding and feature verification instead of manual testing?▼

A scriptable API automates repetitive site dogfooding and feature verification tasks, providing robust state handling and repeatable tests that manual testing cannot achieve deterministically.

Related Skills

Explore More Software Engineering Skills→
liumeixinliumeixin
4

playwright-headless-install

Install Playwright headless browser in restricted environments without root access.

Community
Intermediate
256javy256javy

gstack

Automate end-to-end QA testing with a persistent headless browser.

Community
Advanced
SoSoBurnerSoSoBurner

browse

Automate headless browser actions for QA testing using Playwright.

Community
Advanced
tutur3ututur3u
53

agent-browser

Drive the agent-browser CLI to navigate pages, fill forms, and extract data.

Official
Advanced