skills.rest
Kakarottoooo
KakarottooooCOMMUNITY
Explore all skills by this author →
GitHub

browse

Automate QA testing with a persistent headless browser using Playwright.

Updated Mar 17, 2026
Search Tags:#automation#qa#playwright#web-testing#screenshot#browser-testing
One-click install
npx skills add https://github.com/Kakarottoooo/onegent --skill browse-kakarottoooo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/Kakarottoooo/onegent/tree/main/.agents/skills/gstack/browse
Command: npx skills add https://github.com/Kakarottoooo/onegent --skill browse-kakarottoooo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bun, perl, and includes scripts (resource) components.

What problem does it solve?

The Skill provides a fast, persistent headless browser orchestration to automate QA tests, capture evidence, and validate user flows across deployments.

Core Features & Use Cases

  • Deterministic navigation and interaction across pages and forms
  • Diff-before/after and annotated screenshots for bug repros and visual regression testing
  • Responsive layout checks, dialogs, uploads, and multi-tab workflows
  • Use cases include regression testing, feature verification, and design validation across web apps

Quick Start

Open a URL with goto, capture an ARIA snapshot with snapshot, and optionally save annotated screenshots with -a to document UI state.

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 with a persistent headless browser to navigate pages, interact with elements, and verify UI state. This approach applies to regression testing, feature verification, and design validation across responsive layouts and dynamic content.

How do I capture screenshots for visual regression testing?▼

Capture screenshots for visual regression testing using the screenshot command with the -a flag to save annotated outputs. This documents UI state for bug repros and allows diffing before and after deployments.

Do I need Playwright installed to run web-testing automation?▼

Yes, you need Playwright installed as the browser engine to run web-testing automation. The Skill requires Playwright to execute commands like goto, click, type, wait, snapshot, and screenshot for deterministic navigation.

Can I handle multi-tab workflows and dialogs in browser automation?▼

Yes, you can handle multi-tab workflows and dialogs in browser automation through stateful tab management. The persistent headless browser supports robust error handling while interacting with forms, uploads, and dynamic content.

What's the best way to verify UI state across responsive layouts?▼

The best way to verify UI state across responsive layouts is using ARIA snapshots alongside annotated screenshots. This validates design changes and dynamic content while maintaining deterministic navigation across different deployment states.

Related Skills

Explore More Software Engineering Skills→
henkisdabrohenkisdabro
77

webapp-testing

Automate local web app testing with Playwright and headless Chromium.

Community
Intermediate
fray-cloudfray-cloud

browse

Drive a headless browser to automate QA tasks and capture annotated screenshots.

Community
Advanced
nateanatea

compatibility-testing

Automate cross-browser compatibility testing across devices using Playwright and BrowserStack.

Community
Advanced
BuilderIOBuilderIO
11

playwright-cli

Automate browser interactions and Playwright test workflows via command-driven tooling.

Official
Advanced