browse

Automate QA tasks on web pages with a headless browser and ARIA snapshots.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates browser-based QA tasks by offering a persistent headless browser, ARIA snapshot parsing, and a ref-driven interaction model for AI agents.

Core Features & Use Cases

  • Headless browser for QA and site dogfooding; supports navigation, element inspection, forms, and accessibility.
  • ARIA snapshot parsing with generated @ref identifiers for stable, reproducible automation.
  • Snapshot diffing, annotated screenshots, and ref-based interactions to automate QA workflows across pages.

Quick Start

Run a quick QA session against your site to validate pages, take ARIA snapshots, and export results.

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 using a headless browser?

Automate QA testing using a headless browser by navigating web pages, inspecting elements, and validating forms. This applies to automated testing, accessibility verification, and regression checks across pages and sessions.

What are ARIA snapshots and how do they work for web automation?

ARIA snapshots parse web page accessibility trees to generate stable @ref identifiers for elements. These ref-driven identifiers enable reproducible automation and strict validation for AI agents.

Does Playwright work with ARIA snapshots for automated testing?

Playwright works with ARIA snapshots by providing a backed locator map that supports ref-based interactions. This integration satisfies strict validation, diffing, and interaction requirements across testing sessions.

How do I run accessibility verification and regression checks across web pages?

Run accessibility verification and regression checks across web pages by taking ARIA snapshots and applying ref-based interactions. Snapshot diffing and annotated screenshots validate page states across sessions.

Why use a ref-driven interaction model for web automation?

Use a ref-driven interaction model for web automation to ensure stable, reproducible element targeting. Generated @ref identifiers from ARIA snapshots prevent brittle selectors and maintain strict validation.