browse

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

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/fullya99/simple-blog-page --skill browse-fullya99
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/fullya99/simple-blog-page/tree/main/.claude/skills/gstack/browse
Command: npx skills add https://github.com/fullya99/simple-blog-page --skill browse-fullya99

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, diff, bun.

What problem does it solve? Manually verifying that a web page loads correctly, that a user flow works end to end, or that a deployment matches staging requires opening a browser, clicking around, and capturing evidence. This Skill gives an AI agent a fast persistent headless Chromium instance (~100ms per command after startup) to navigate, interact, inspect, and screenshot any web page on demand. ## Core Features & Use Cases - Page verification and inspection: Navigate to any URL, extract text/HTML/links/forms, check console errors, network requests, performance timings, and assert element states (visible, enabled, checked, focused). - Interactive flow testing: Snapshot pages to get @e/@c element refs, then click, fill, select, upload files, handle dialogs, and diff before/after snapshots to verify exactly what changed. - Visual evidence and responsive checks: Capture annotated screenshots, PDFs, and mobile/tablet/desktop responsive screenshots, or diff text content between two environments (e.g., staging vs production). - Session reuse: Import cookies from JSON files or from installed Chromium browsers (Chrome, Arc, Brave, Edge, Comet) via a local cookie-picker UI to test authenticated flows. - Use Case: After deploying a new login page, run goto, snapshot -i, fill credentials, click submit, then snapshot -D and is visible ".dashboard" to confirm the flow works, and save an annotated screenshot as bug-report evidence. ## Quick Start Ask the agent to open your app's URL with the browse skill, fill in the login form, submit it, and verify the dashboard appears with a screenshot.

Frequently Asked Questions about browse

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

FAQPage Schema
How do I test a login flow with a headless browser?▼

Navigate with goto, run snapshot -i to list interactive elements, fill the username and password fields using their @e refs, click the submit button, then use snapshot -D to diff the result and is visible to assert the success state appeared.

How to take annotated screenshots for bug reports?▼

Run snapshot -i -a -o /tmp/annotated.png to produce a screenshot with labeled interactive element refs, or use screenshot /tmp/bug.png for a plain full-page capture. Combine with the console command to attach JavaScript error logs as evidence.

Can I import cookies from Chrome into a Playwright session?▼

Yes, the cookie-import-browser command reads and decrypts cookies from installed Chromium browsers (Chrome, Arc, Brave, Edge, Comet) on macOS using Keychain access, or you can use the local cookie-picker web UI to select domains to import.

Does the headless browser keep state between commands?▼

Yes, a persistent server keeps cookies, tabs, and login sessions alive between commands, so each call takes about 100ms after the initial ~3s startup. The server shuts down automatically after 30 minutes of idle time.

Why did my click command fail with an element not found error?▼

Element refs become stale after page navigation, so run snapshot again to get fresh @e refs before interacting. Timeouts also occur when selectors match multiple elements or the target is not yet interactable.

How do I compare staging and production websites?▼

Use the diff command with two URLs, for example diff https://staging.app.com https://prod.app.com. It fetches both pages, extracts clean text, and outputs a line-by-line unified diff of the content differences.