skills.rest
agwacom
agwacomOFFICIAL
Explore all skills by this author →
GitHub

browse

Drive a headless browser to navigate URLs, interact with elements, and verify page state.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The browse Skill provides a fast, automated browser framework for QA testing and site dogfooding, reducing manual testing effort by driving a headless browser to navigate pages, interact with elements, and verify states. It also captures diffs and visual evidence to support bug reports.

Core Features & Use Cases

  • Headless browser automation for QA testing and dogfooding across URLs.
  • Interact with page elements, verify states, diff before/after actions, and capture annotated screenshots.
  • Supports responsive checks, form uploads, and dialog handling for robust UI validation.

Quick Start

Invoke /browse to start a headless QA session and begin testing a page.

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

Automate headless browser QA testing by driving Playwright to navigate URLs, interact with page elements, and verify page state across responsive layouts, forms, uploads, and dialogs.

Can I capture screenshots and diffs during automated browser testing?▼

Yes, automated browser testing captures annotated screenshots and diffs before and after actions to verify page states and provide visual evidence for bug reports.

Do I need Playwright to run headless browser automation for site dogfooding?▼

Yes, Playwright is required under the hood to drive the headless browser, navigate URLs, interact with elements, and execute deterministic tasks via scripts and assets.

What's the best way to reproduce bugs using a headless QA browser?▼

Reproduce bugs by driving a headless QA browser to navigate specific URLs, interact with elements, capture visual diffs, and verify page state to support bug reports.

Does headless browser automation support responsive checks and form uploads?▼

Yes, headless browser automation supports responsive checks, form uploads, and dialog handling to ensure robust UI validation across various page states and layouts.

Related Skills

Explore More Software Engineering Skills→
26mitch2626mitch26

setup-browser-cookies

Import cookies from a Chromium browser into Playwright headless sessions.

Community
Basic
shaythegay13shaythegay13

canary

Monitor live apps after deploy for console errors, performance regressions, and page failures.

Community
Advanced
neonwattyneonwatty
23

desktop-workflow-to-playwright

Converts desktop workflow markdown into Playwright test projects with authentication and CI configuration.

Community
Advanced
robertzengcnrobertzengcn

browse

Automate headless browser navigation, interaction, and visual verification with Playwright-based Chromium.

Community
Advanced