browse

Automate QA testing with a headless browser for element interaction and screenshots.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/TobiasPerry/aws-hackathon --skill browse-tobiasperry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/TobiasPerry/aws-hackathon/tree/main/.claude/skills/gstack/browse
Command: npx skills add https://github.com/TobiasPerry/aws-hackathon --skill browse-tobiasperry

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bun, perl, curl, and includes scripts (resource) components.

What problem does it solve?

Automate and accelerate QA testing by steering a fast headless browser to navigate, interact with pages, verify states, and diff results across runs. Capture annotated screenshots, check responsive layouts, test forms and uploads, and handle dialogs to dogfood deployments with evidence.

Core Features & Use Cases

  • Navigate any URL with a fast headless browser and interact with elements to reproduce user flows.
  • Diff outcomes across steps, diff screenshots, and verify page state for regressions.
  • Take annotated screenshots and validate responsive layouts for quick bug reporting and deployment verification.

Quick Start

Run a quick test by navigating to a URL and taking a screenshot to verify behavior.

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 responsive web layouts?

Automate QA testing by launching a fast headless browser to navigate URLs, interact with elements, and capture annotated screenshots. This verifies responsive layouts and reproduces user flows to dogfood deployments with visual evidence.

Can I capture screenshots and diff web pages to check for regressions?

Yes, you can capture annotated screenshots and diff outcomes across steps to verify page state for regressions. Diffing screenshots across runs highlights visual and state changes quickly for bug reporting.

What do I need to run headless browser automation for forms and uploads?

You need the bun, perl, and curl dependencies installed to run headless browser automation. This environment launches the browser to test forms, handle uploads, and manage dialogs during QA workflows.

Does this web-automation tool support state verification and element interaction?

Yes, the web-automation tool supports element interaction and state verification across user flows. It navigates any URL to reproduce user actions, verify page states, and handle dialogs with robust error handling.

Why use a headless browser for deployment verification instead of manual checks?

Using a headless browser for deployment verification accelerates QA by automating navigation and state checks deterministically. It captures annotated screenshots as evidence, replacing manual checks with diffable, reproducible results.

Are there limitations when diffing screenshots across different browser runs?

While diffing screenshots detects visual regressions robustly, dynamic content or animations may cause false positives. Deterministic browser execution mitigates this, but complex responsive layouts might still require targeted state verification.