browse

Controls a persistent headless Chromium browser for QA testing and site verification.

2|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/westkite1201/garden-engine --skill browse-westkite1201
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/westkite1201/garden-engine/tree/main/.claude/skills/gstack/browse
Command: npx skills add https://github.com/westkite1201/garden-engine --skill browse-westkite1201

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, playwright-core, diff, and includes scripts (resource) components.

What problem does it solve? Manually verifying that a web feature works—clicking through flows, checking console errors, capturing screenshots—is slow and hard to automate from an AI coding session. This Skill provides a fast persistent headless browser (~100ms per command) so an agent can navigate pages, interact with elements, and gather visual evidence of bugs. ## Core Features & Use Cases - Page Interaction & State Assertions: Navigate URLs, click, fill forms, upload files, handle dialogs, and assert element states (visible, enabled, checked) via accessibility-tree snapshots with @e refs. - Visual Evidence & Diffing: Take annotated or responsive screenshots, save PDFs, diff snapshots before/after actions, and compare staging vs production pages. - Session Persistence & Handoff: Cookies, tabs, and login state persist across commands; import cookies from real Chromium browsers, and hand off to a visible Chrome window for CAPTCHAs or MFA. - Use Case: After deploying a login flow, ask the agent to open the site, fill credentials, submit, verify the dashboard appears, and produce an annotated screenshot as bug-report evidence. ## Quick Start Use the browse skill to open https://staging.myapp.com, log in with test credentials, and take a screenshot of the dashboard.

Frequently Asked Questions about browse

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

FAQPage Schema
How do I test a website with a headless browser from the command line?

Use the browse CLI to run commands like goto, click, fill, and snapshot against a persistent headless Chromium server. The first call auto-starts the server in about 3 seconds, then each command takes roughly 100ms with session state preserved.

How to take annotated screenshots of web page elements?

Run snapshot with the -a flag to produce an annotated screenshot with red overlay boxes and ref labels on interactive elements. Combine with -i to limit to interactive elements and -o to set the output path.

Can I import cookies from Chrome into a headless browser session?

Yes, the cookie-import-browser command reads and decrypts cookies from installed Chromium-based browsers like Chrome, Brave, Edge, and Arc on macOS and Linux. You can filter by domain and select a specific browser profile.

Does headless browser testing work on Windows with Playwright?

Yes, but Bun cannot launch Playwright's Chromium on Windows, so the tool falls back to a Node.js server bundle with Bun API polyfills. The build script generates server-node.mjs for this compatibility path.

What to do when headless browser hits a CAPTCHA or MFA login?

Use the handoff command to open a visible Chrome window at the current page so the user can solve the CAPTCHA or complete MFA. After the user finishes, the resume command returns control to the agent with all cookies and tabs preserved.