skills.rest
2300031147
2300031147COMMUNITY
Explore all skills by this author →
GitHub

browse

Drive a persistent headless browser to navigate URLs and verify page state.

Updated Apr 12, 2026
Search Tags:#automation#testing#screenshots#qa#diff#playwright#browser
One-click install
npx skills add https://github.com/2300031147/clawopencode --skill browse-2300031147
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/2300031147/clawopencode/tree/main/skills/browse
Command: npx skills add https://github.com/2300031147/clawopencode --skill browse-2300031147

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill provides a fast, headless browser engine to automate QA tasks, navigate to URLs, interact with elements, and capture evidence without manual steps.

Core Features & Use Cases

  • Persistent browser sessions for deterministic tests across steps.
  • Navigate, interact, and verify page state, diff before/after actions, and take annotated screenshots.
  • Validate responsive layouts, forms, uploads, and dialogs in real sites for bug hunting and regression testing.

Quick Start

Launch a test against a URL and capture results in seconds.

Frequently Asked Questions about browse

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

FAQPage Schema
How do I automate UI testing with a headless browser to capture screenshots?▼

You can automate UI testing by driving a persistent headless browser to navigate URLs, interact with elements, and capture annotated screenshots. This verifies page state and produces reliable evidence for regression checks.

Can I use Playwright for feature testing and form validation on real sites?▼

Yes, you can use Playwright for feature testing by validating responsive layouts, forms, and dialogs on real sites. The browser engine handles inputs and safety constraints to ensure deterministic behavior during validation.

What is the best way to collect visual diffs before and after browser actions?▼

The best way to collect visual diffs is to apply a headless browser engine to diff page state before and after actions. This automated QA process captures annotated evidence without requiring manual steps.

Does headless browser automation work for handling dialogs and file uploads?▼

Headless browser automation works for handling dialogs and validating file uploads. It drives a persistent browser session to interact with these elements and verify page state safely.

Why do I need persistent browser sessions for regression testing?▼

You need persistent browser sessions for regression testing to maintain deterministic test behavior across multiple steps. This ensures reliable results when navigating URLs and verifying page state sequentially.

Related Skills

Explore More Software Engineering Skills→
jonkikyjonkiky

browse

Automate QA testing with a persistent headless browser for web interactions.

Community
Advanced
steadyfallsteadyfall

browse

Navigate pages with a headless browser and capture annotated screenshots.

Community
Advanced
UnicornUnicorn

e2e-test-agent

Generate end-to-end test suites for web and full-stack applications.

Official
Advanced
chad3814chad3814

Backend API

Build Express API endpoints with typed validation and SSE progress streaming.

Community
Advanced