browse

Automate browser QA tasks with navigation, element interaction, and page validation.

Updated Apr 22, 2026

Search Tags:#automation #testing #qa #playwright #browser #screenshot

Ready to run

npx skills add https://github.com/diiviikk5/rezops --skill browse-diiviikk5

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/diiviikk5/rezops/tree/main/browse
Command: npx skills add https://github.com/diiviikk5/rezops --skill browse-diiviikk5

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill provides a fast, persistent browser environment to automate QA tasks such as navigating to URLs, interacting with elements, taking screenshots, and verifying page state without manual clicks.

Core Features & Use Cases

Persistent headless browser with command-based interactions for navigating, clicking, filling forms, and capturing screenshots.
Snapshot, diffing, and validation workflows that enable regression testing and evidence collection.
Use cases include feature validation, bug reproduction with evidence, and dogfooding: quickly testing user flows across URLs and devices.

Quick Start

Open a page, then run a sequence like goto, snapshot, and screenshot to begin automated QA workflows.

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?▼

Automate QA testing by using a headless browser to navigate URLs, interact with elements, and validate page state. It executes command-based actions for clicking, filling forms, and capturing screenshots without manual intervention.

Can I take screenshots and capture evidence for bug reproduction?▼

Yes, you can take screenshots and capture snapshots during browser automation. It supports diffing and validation workflows to collect evidence for bug reproduction and verify feature regression across test scenarios.

Does this browser automation skill work with Playwright?▼

Yes, it requires a Playwright-backed environment to run automated QA tasks. It leverages Playwright to maintain persistent headless sessions and execute element interactions across local and remote pages.

What is the best way to start an automated browser testing workflow?▼

Start automated browser testing by opening a page and running a command sequence like goto, snapshot, and screenshot. This initiates navigation, captures page state, and records visual evidence for validation.

Can I maintain a persistent session across multiple page interactions?▼

Yes, you can maintain a persistent headless browser session across multiple interactions. It supports element references and sequential commands, allowing continuous navigation and form interactions across varied test scenarios.

How do I validate page state and run regression tests on URLs?▼

Validate page state by navigating to URLs and using snapshot and diffing workflows to check for regressions. It integrates with test fixtures and assets to execute deterministic validation tasks across local and remote pages.