skills.rest
24601
24601COMMUNITY
Explore all skills by this author →
Website𝕏@moltar81435GitHub

browse

Automate QA testing by controlling a persistent headless Chromium instance.

Updated Mar 28, 2026
Search Tags:#qa#playwright#screenshot#form-testing#visual-regression#headless-browser#cookie-import
One-click install
npx skills add https://github.com/24601/gastack-pre-fork --skill browse-24601
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/24601/gastack-pre-fork/tree/main/browse
Command: npx skills add https://github.com/24601/gastack-pre-fork --skill browse-24601

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Quickly verify that web features work end-to-end without a human driving a browser. It replaces slow, manual checks with a persistent headless Chromium session that can navigate pages, interact with elements, capture evidence, and surface failures as reproducible artifacts for QA, reviewers, and bug reports.

Core Features & Use Cases

  • Persistent headless Chromium that starts once and services ~100ms commands, preserving cookies, tabs, and storage between calls.
  • Comprehensive QA commands for navigation, snapshots with @ref selectors, annotated screenshots, visual diffs, responsive screenshots, form fills, uploads, dialog handling, console/network capture, and PDF/export.
  • Handoff and recovery: hand off to a headed browser for CAPTCHA or MFA, resume after user action, and recreate contexts to apply user-agent or header changes.
  • Privacy & robustness: argument filtering for secrets, encrypted key handling for cookie import, locked-state DB copy fallback, and non-blocking telemetry with opt-in.
  • Use cases: verify a deployment, reproduce a bug with annotated screenshots and console logs, test file uploads and forms, compare staging vs prod, and run onboarding dogfooding flows.

Quick Start

Ask the skill to "open https://yourapp.com, snapshot the page, click through the user flow, and save an annotated screenshot for a bug report."

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

Automate QA testing by using a persistent headless Chromium instance backed by Playwright to navigate pages, interact with elements, and capture evidence with ~100ms commands. This preserves cookies and storage between calls for continuous feature verification checks.

Can I capture annotated screenshots and visual diffs for bug reports using a headless browser?▼

Yes, you can capture annotated screenshots and visual diffs for bug reports using the headless browser. It generates reproducible artifacts by taking responsive screenshots and comparing staging against production layouts to surface visual failures.

How do I handle CAPTCHA or MFA interruptions during automated form testing?▼

Handle CAPTCHA or MFA during automated form testing by handing off the persistent headless session to a headed browser. You can manually complete the user action and then resume the automated testing flow afterward.

Does this Playwright CLI tool support importing cookies and filtering secrets for secure testing?▼

Yes, the Playwright CLI tool supports encrypted key handling for cookie import and privacy-aware argument filtering to strip secrets. It also uses a locked-state database copy fallback to ensure secure and robust testing environments.

What dependencies do I need to run headless browser commands for deployment checks?▼

You need the bun, node, perl, and curl dependencies installed to run headless browser commands for deployment checks. These executables provide the runtime environment required to execute the Playwright-backed CLI scripts and manage the Chromium instance.

Why use a persistent headless Chromium session instead of starting a new browser for each test?▼

A persistent headless Chromium session starts once and services ~100ms commands, preserving tabs, cookies, and storage between calls. This avoids the overhead of restarting the browser, making it significantly faster for continuous form and upload testing.

Related Skills

Explore More Software Engineering Skills→
a29paula29paul
1

gstack

Automate website testing and deployment verification with persistent headless browser control.

Community
Advanced
JaykaijackJaykaijack

browse

Automate headless Chromium browsing and UI verification with screenshots and diffs.

Community
Advanced
MacPhobosMacPhobos

Playwright E2E Testing Skill

Create and run Playwright end-to-end tests for web applications.

Community
Intermediate
DangQuangSEDangQuangSE
19

playwright-skill

Automate browser interactions, API testing, and visual regression with Playwright.

Community
Advanced