browse

Automates web page navigation, interaction, and state validation with visual evidence.

6|2|Updated Oct 18, 2021
One-click install
npx skills add https://github.com/jerrywu001/jerrywu001 --skill browse-jerrywu001
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/jerrywu001/jerrywu001/tree/main/.claude/skills/browse
Command: npx skills add https://github.com/jerrywu001/jerrywu001 --skill browse-jerrywu001

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you verify that a website actually works the way you expect by navigating pages, interacting with UI elements, and capturing evidence (like annotated screenshots and diffs) instead of relying on guesswork.

Core Features & Use Cases

  • Fast QA browser for end-to-end checks: Load URLs, interact with elements, and confirm page state (visible/hidden/enabled/disabled, form fields, dialogs).
  • Evidence generation for bugs and deployments: Take annotated screenshots, plain screenshots, unified diffs before/after actions, and collect console/network signals.
  • Real-world testing workflows: Validate user flows (login, form submission), responsive layouts, file uploads, and multi-environment comparisons (staging vs production).

Quick Start

Use the browse skill to dogfood and screenshot a login flow by running: go to https://yourapp.com/login, take an interactive snapshot, fill the email and password fields, submit, then generate a diff and an annotated screenshot.

Frequently Asked Questions about browse

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

FAQPage Schema
How do I automate headless browser navigation to capture visual evidence for bug reports?

Automate headless browser navigation to capture visual evidence by loading URLs, interacting with elements, and generating annotated screenshots and unified diffs for bug reports. This approach validates page state and collects console and network signals.

Can I validate form submission and login flows using a headless browser?

You can validate form submission and login flows using a headless browser by filling fields, submitting data, and confirming the resulting page state. It supports persistent browser sessions to reliably test real-world user workflows end to end.

What's the best way to test responsive layouts across staging and production environments?

Testing responsive layouts across staging and production environments is best done by automating headless browser navigation to compare page states. You capture screenshots and unified diffs before and after actions to verify layout consistency.

Does headless browser testing support file uploads and dialog interactions?

Headless browser testing supports file uploads and dialog interactions by automating element selection via accessibility snapshots. You interact with UI components and validate their visible, hidden, enabled, or disabled states to confirm functional behavior.

How do I capture console and network signals during UI automation testing?

Capture console and network signals during UI automation testing by executing commands within a controlled headless browser session. The session monitors page interactions and collects telemetry data to provide behavioral evidence for QA testing.