browse

Control a Playwright-based headless browser to navigate, inspect, and verify web pages.

107|19|Updated Mar 23, 2026

Search Tags:#automation #diff #playwright #browser #headless #snapshot #qa-testing

Ready to run

npx skills add https://github.com/mr-daedalium/ostack --skill browse-mr-daedalium

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a fast, persistent headless browser engine to automate QA tasks, capture evidence, and repeat tests across deployments.

Core Features & Use Cases

Navigate to URLs and interact with elements
Diff before/after actions and take annotated screenshots
Snapshot ARIA trees for accessibility validation and exportable refs
Test forms, uploads, and responsive layouts, with built-in logging for console and network activity
Use for feature verification, bug reproduction, and regression testing in CI

Quick Start

Launch the browse skill to run automated QA sessions by navigating pages, interacting with UI, and capturing evidence.

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 QA testing for web app deployments?▼

Automate headless browser QA testing by controlling a Playwright-based engine to navigate URLs, interact with elements, and verify web pages. It supports scripted actions like goto, click, fill, screenshot, and diff to validate deployments and capture evidence.

Can I capture ARIA tree snapshots and compare diffs during automated browser testing?▼

Yes, you can snapshot ARIA trees during automated browser testing to validate accessibility and generate exportable refs. The engine also supports before/after diffing and annotated screenshots to verify UI changes and detect regressions.

Does this headless browser tool log console and network traffic for bug reproduction?▼

The headless browser tool logs both console and network traffic during automated QA sessions. This built-in logging captures errors and requests, making it effective for bug reproduction, feature verification, and diagnosing issues across web apps.

What is the best way to run regression testing in CI using a headless browser?▼

Run regression testing in CI by wiring a persistent Playwright-based headless browser to execute scripted actions. It repeats tests across deployments, captures annotated screenshots, and compares diffs to catch UI regressions automatically.

Can I test forms, uploads, and responsive layouts with Playwright automation?▼

Yes, you can test forms, uploads, and responsive layouts with Playwright automation. The engine supports fill actions for inputs, handles file uploads, and validates responsive designs by navigating and inspecting pages across different viewport configurations.

Are there limitations when using a headless browser for accessibility validation?▼

Accessibility validation relies on snapshotting ARIA trees rather than full visual rendering. While effective for structure checks and exportable refs, it may not capture visual-only layout issues that require a headed browser or manual review.