browse

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

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Jaykaijack/openclaw-backup --skill browse-jaykaijack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/Jaykaijack/openclaw-backup/tree/main/skills/gstack/browse
Command: npx skills add https://github.com/Jaykaijack/openclaw-backup --skill browse-jaykaijack

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Rapidly verify web UIs and user flows without a full browser, removing repetitive manual QA steps by providing fast, scriptable headless browsing with reproducible visual evidence for bugs and deployments.

Core Features & Use Cases

  • Persistent Headless Chromium: keep cookies, storage, and tabs across commands to reproduce flows and login states.
  • Snapshot + Refs: accessible-tree snapshots that produce @e/@c refs for reliable, ref-based interactions.
  • Visual Evidence & Diffing: take annotated screenshots, responsive previews, and unified diffs before/after actions for bug reports.
  • Interaction Automation: navigation, clicks, fills, uploads, dialog handling, viewport control, and form testing at ~100ms per command.
  • Cookie Import & Picker: decrypt and import Chromium cookies (macOS flows) and deliver them into Playwright contexts for session reproduction.
  • Handoff & Resumption: escalate to a headed browser for CAPTCHAs or MFA, then resume automated workflows with preserved state.

Quick Start

Ask the skill to navigate to a URL and produce an annotated interactive snapshot by running a goto to your site followed by snapshot -i -a.

Frequently Asked Questions about browse

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

FAQPage Schema
How do I automate headless browsing for QA testing and capture UI screenshots?

Automate headless browsing for QA testing by using a persistent headless Chromium session to navigate web applications, interact with elements, and capture annotated screenshots as visual evidence for bug reports.

Can I use Playwright locators for automated UI verification in a headless browser?

Playwright locators are supported for automated UI verification, utilizing accessible-tree snapshots that produce @e/@c refs to enable reliable, ref-based element selection and interaction within the headless browser.

What is the best way to handle cookies and session state for web application testing?

Handle cookies and session state for web application testing by importing decrypted Chromium cookies into Playwright contexts, keeping storage and tabs persistent across commands to reproduce login states and user flows.

How do visual diff screenshots help with deployment verification and bug reporting?

Visual diff screenshots assist deployment verification by capturing annotated screenshots and unified diffs before and after actions, providing reproducible visual evidence that highlights UI changes for bug reports.

Does headless browser automation work for handling CAPTCHAs and MFA prompts?

Headless browser automation handles CAPTCHAs and MFA by escalating to a headed browser for manual intervention, then resuming automated workflows with the previously preserved session state intact.

Do I need bun and node installed to run headless browser UI verification scripts?

You need bun and node installed to execute the headless browser UI verification scripts, as these dependencies are required to automate navigation, form testing, and snapshot generation.