browse

Drive a headless browser to navigate, interact, and verify web pages.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fast, reliable QA testing of web features by driving a headless browser to navigate URLs, interact with elements, verify state, and diff results with annotated evidence.

Core Features & Use Cases

  • Navigate to URLs and interact with page elements, verifying states and extracting confirmations.
  • Diff before/after actions and capture annotated screenshots to document regressions.
  • Validate responsive layouts, forms, and uploads across multiple viewports and scenarios.

Quick Start

Start by running the skill to launch the headless browser and run a test against your target URL.

Frequently Asked Questions about browse

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

FAQPage Schema
How do I automate QA testing with a headless browser to verify web page features?

Automate QA testing by driving a headless browser to navigate URLs, interact with page elements, verify states, and extract confirmations. This approach enables fast, reliable feature verification and regression testing with annotated evidence.

Can I capture annotated screenshots during regression testing to document visual diffs?

Yes, you can capture annotated screenshots to document regressions during regression testing. The browser automation tool diffs before and after actions, generating visual evidence that highlights state changes and layout failures.

Does Playwright support automated testing across multiple viewports for responsive layouts?

Playwright supports automated testing across multiple viewports to validate responsive layouts, forms, and uploads. Deterministic scripts drive the browser to verify rendering consistency and user interactions across different screen sizes.

What is the best way to reproduce bugs in a headless browser with deterministic scripts?

The best way to reproduce bugs is using deterministic scripts in a headless browser to consistently navigate, interact, and verify web page states. This method reliably replicates exact conditions, capturing annotated screenshots as evidence.

Do I need to install external dependencies to run headless browser automation for QA?

No external dependencies are required to run headless browser automation for QA. The skill operates independently, driving a fast headless browser to execute test scenarios and verify web page states without additional tool installations.

Can I extend browser test scenarios with optional references for feature verification?

Yes, you can extend browser test scenarios with optional references for feature verification. This allows you to customize deterministic scripts, adapt testing conditions, and validate complex user interactions across various web pages.