browse

Automate web page interactions in a headless browser for QA testing.

Updated Jun 9, 2026
One-click install
npx skills add https://github.com/ericdahl-dev/coauthor-cleaner --skill browse-ericdahl-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/ericdahl-dev/coauthor-cleaner/tree/main/.claude/skills/gstack/browse
Command: npx skills add https://github.com/ericdahl-dev/coauthor-cleaner --skill browse-ericdahl-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a headless browser for automating QA testing and site dogfooding, enabling you to perform detailed testing and analysis without the need for a GUI.

Core Features & Use Cases

  • Headless Browser: Interact with web pages, verify page state, and take screenshots without a GUI.
  • Interactive Elements Detection: Identify clickable elements, including those with no ARIA roles, and prioritize dropdowns and popovers.
  • Use Case: When testing a complex web application, use this Skill to programmatically navigate through pages, interact with elements, and take screenshots for review.

Quick Start

Use the browse skill to take a screenshot of the current page.

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 for web pages without launching a GUI?

Headless browser QA testing automates web page interactions without a GUI. This Skill uses Playwright to programmatically navigate pages, verify state, and handle dialogs for site dogfooding and responsive layout checks.

Can I take screenshots during headless browser testing to verify responsive layouts?

Yes, you can take screenshots during headless browser testing. This Skill supports capturing the current page state visually, which is ideal for verifying responsive layouts and reviewing complex web application interactions.

Does this headless browser tool require Playwright to handle interactive elements?

Yes, this headless browser requires Playwright for browser automation. It leverages Playwright to detect clickable elements, including those lacking ARIA roles, and prioritizes interactions with dropdowns and popovers.

What is the best way to test web forms and handle dialogs in an automated environment?

The best way to test web forms and handle dialogs is using a headless browser. This Skill automates these user interactions and assertions, allowing you to verify form submissions and dialog behavior without manual GUI intervention.

Are there limitations when testing web applications with no ARIA roles on interactive elements?

There are no limitations when testing web applications with no ARIA roles. This Skill's headless browser explicitly identifies clickable elements lacking ARIA roles, ensuring comprehensive coverage of interactive page components.