browse

Automate web application testing with a persistent headless Chromium browser.

1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/a29paul/hexlens --skill browse-a29paul
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/a29paul/hexlens/tree/main/.claude/skills/gstack/browse
Command: npx skills add https://github.com/a29paul/hexlens --skill browse-a29paul

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Manual web testing is slow, inconsistent, and hard to document. This Skill provides a persistent headless Chromium browser that automates navigation, interaction, and visual verification in milliseconds, turning QA and bug reporting into fast, repeatable workflows.

Core Features & Use Cases

  • Automated Browser Testing: Navigate URLs, fill forms, click elements, and assert page states with simple commands across multiple tabs.
  • Visual Evidence & Debugging: Capture annotated screenshots, responsive layouts, console logs, and network traffic to document bugs or verify deployments.
  • Use Case: A developer testing a checkout flow can navigate to staging, fill the form, take a screenshot of the confirmation page, and export a PDF — all without leaving the terminal.

Quick Start

Use the browse skill to navigate to your staging site, take an annotated screenshot of the checkout page, and verify that the submit button is visible.

Frequently Asked Questions about browse

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

FAQPage Schema
How do I automate form validation and take screenshots using a headless browser?

Automate form validation and screenshot capture by using a persistent headless Chromium browser driven by Playwright. This setup executes navigation, interaction, and visual verification commands in milliseconds, allowing rapid QA testing directly from the terminal.

Can I use Playwright to check responsive layouts and monitor console errors?

Yes, Playwright supports responsive layout checks and console error monitoring within a headless Chromium environment. This Skill automates these QA workflows, capturing annotated screenshots and network traffic to verify deployments or document bugs.

Does this headless browser automation tool support multi-tab batch execution?

Yes, the headless browser automation tool supports multi-tab batch execution for QA workflows. It leverages a persistent Chromium instance to apply testing commands across multiple tabs, executing form validation, navigation, and visual verification tasks rapidly.

Can I import cookies from a real browser into a headless Playwright session?

Yes, you can import cookies from a real browser into the headless Playwright session. This allows the persistent Chromium browser to maintain authenticated states, enabling accurate testing of secure staging environments and login-protected checkout flows.

What is the best way to document web application bugs during terminal-based QA testing?

The best way to document web application bugs during QA testing is to use a persistent headless Chromium browser. It automatically captures annotated screenshots, responsive layouts, console logs, and network traffic, turning manual testing into fast, repeatable workflows.

Do I need Playwright installed to run headless browser automation for visual verification?

Yes, Playwright is a required dependency for running this headless browser automation and visual verification. The Skill relies on Playwright and playwright-core to drive the persistent Chromium instance for form validation, responsive testing, and screenshot capture.