browse

Operate a headless browser for automated QA testing and evidence collection.

Updated Mar 27, 2026

Search Tags:#automation #testing #screenshots #qa #playwright #browser #headless

Ready to run

npx skills add https://github.com/vebesz/vstack --skill browse-vebesz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/vebesz/vstack/tree/main/browse
Command: npx skills add https://github.com/vebesz/vstack --skill browse-vebesz

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Fast headless browser for QA testing and site dogfooding. Navigate any URL, interact with elements, verify page state, diff before/after actions, take annotated screenshots, check responsive layouts, test forms and uploads, handle dialogs, and assert element states.

Core Features & Use Cases

Navigate to pages and interact with live content in a deterministic, scriptable browser.
Diff page states before/after actions and generate evidence (screenshots, text diffs) for bug reports and audits.
Dogfood deployments and marketing sites with end-to-end checks: CRO audits, SEO verifications, copy rewrites, and content strategy validation.

Quick Start

Open a URL in a headless browser and run a simple test to verify the page loads correctly.

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 landing page deployments?▼

Automate headless browser testing by navigating to URLs, interacting with elements, and verifying page state deterministically. You can script end-to-end checks for deployments, marketing sites, and forms to ensure landing pages load correctly and function as expected.

Can I take screenshots and diff page states during automated QA testing?▼

Yes, you can take annotated screenshots and generate text diffs before and after actions. This evidence collection mechanism provides visual and state comparisons, which is ideal for bug reproduction, CRO audits, and verifying deployment changes.

Does headless browser automation require Playwright or Bun to run?▼

The environment requires Bun and Perl as dependencies. It implements a plugin-like skill interface that loads contextual tooling into memory, enabling strict URL validation and multi-tab state persistence for deterministic testing workflows.

What is the best way to verify SEO and CRO audits on marketing sites?▼

The best way to verify SEO and CRO audits is by running scriptable browser workflows that interact with live content. This method applies to marketing sites and copy rewrites, validating content strategy through repeatable, browser-backed checks.

Why use a persistent headless browser for bug reproduction?▼

A persistent headless browser ensures deterministic bug reproduction by maintaining multi-tab state persistence and robust error handling. It allows you to replicate user interactions, handle dialogs, and assert element states reliably.

When do I need strict URL validation in automated browser testing?▼

Strict URL validation is needed to ensure deterministic testing and prevent navigation errors. It enforces robust error handling during page interactions, state verification, and evidence collection across responsive layouts and forms.