skills.rest
yolopunk
yolopunkCOMMUNITY
Explore all skills by this author →
GitHub

browse

Operate a persistent headless Chromium browser to automate QA testing.

Updated Apr 6, 2025
Search Tags:#automation#testing#qa#playwright#browser#headless#browse
One-click install
npx skills add https://github.com/yolopunk/jedi --skill browse-yolopunk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/yolopunk/jedi/tree/main/.claude/skills/gstack/browse
Command: npx skills add https://github.com/yolopunk/jedi --skill browse-yolopunk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Jedi Browse provides a persistent headless Chromium browser that automates QA testing, enabling you to verify site behavior, reproduce user flows, and capture evidence without manual setup.

Core Features & Use Cases

  • Persistent headless browser lifecycle with deterministic startup and session preservation.
  • Navigate, interact with elements, capture annotated screenshots, and perform diffing between page states.
  • Use cases include automated UI testing, regression checks, knowledge-dogfooding, and rapid evidence collection for bugs.

Quick Start

Launch the skill and navigate to a URL to begin automated QA testing in a headless browser.

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 launching a persistent headless Chromium browser to navigate pages, interact with UI elements, and collect logs. Playwright-powered execution drives the browser lifecycle while preserving sessions across interactions.

Can I take annotated screenshots during automated UI testing?▼

Yes, you can capture annotated screenshots during automated UI testing to verify site behavior and collect bug evidence. The browser navigates to target URLs and captures page states, enabling visual diffing between before and after states.

Does this testing tool support persistent browser sessions?▼

Yes, it supports persistent browser sessions with deterministic startup. Session preservation allows you to reproduce user flows across multiple interactions without losing state, making it ideal for regression checks and complex automated UI testing.

How do I interact with UI elements in a headless Chromium environment?▼

Interact with UI elements using safe URL validation and ref-based element targeting. The local command server processes your interaction requests, allowing Playwright-powered execution to click, type, and navigate within the headless browser.

What is the best way to collect evidence for bug reproduction?▼

Collect bug reproduction evidence by executing user flows in the headless browser and capturing annotated screenshots. The tool gathers page logs and performs diffing between page states to provide rapid visual proof of site behavior anomalies.

Do I need Playwright installed to run headless browser automation?▼

Playwright is required as the underlying engine for headless browser execution. The skill fulfills this runtime requirement internally, providing a local command server that manages the Chromium lifecycle and processes automation commands.

Related Skills

Explore More Software Engineering Skills→
archibatearchibate
6

agent-browser

Automate Chromium browser interactions via CDP with CLI commands.

Community
Advanced
yolopunkyolopunk

qa-only

Automate browser-based QA testing and generate structured reports with evidence.

Community
Advanced
thangvawnthangvawn

e2e-testing

Create and manage Playwright end-to-end tests with Page Object Model.

Community
Advanced
appautomatonappautomaton
18

playwright-cli

Automate complex web interactions and stateful sessions via a Playwright-backed shell interface.

Official
Advanced