skills.rest
JovieInc
JovieIncOFFICIAL
Explore all skills by this author →
WebsiteGitHub

browse

Automate QA workflows with a persistent headless browser and annotated screenshots.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA teams and developers struggle with unstable or ad-hoc browser automation. This Skill provides a persistent headless browser that can be scripted to navigate, interact, verify page state, and collect evidence like annotated screenshots and diffs.

Core Features & Use Cases

  • Deterministic commands to navigate, interact with elements, and assert page state.
  • Diff before/after actions to track changes and reproduce bugs.
  • Annotated screenshots and responsive layout checks to facilitate bug reproduction and reporting.
  • Dialog handling, form testing, and state persistence across sessions for end-to-end QA.

Quick Start

Launch the gstack browse server and navigate to a URL to start QA testing.

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 to capture bug evidence?▼

Headless browser QA testing is automated by launching a persistent Playwright-backed browser to navigate URLs, interact with UI elements, verify page state, and capture annotated screenshots as bug report evidence.

What's the best way to compare UI diffs before and after actions in browser automation?▼

Comparing UI diffs in browser automation involves executing an action, capturing the resulting page state, and comparing it against the baseline to track changes and reproduce visual or functional bugs deterministically.

Does this browser automation Skill support dialog handling and state persistence for end-to-end QA?▼

Dialog handling and state persistence are supported, allowing the headless browser to manage popups, execute form testing, and maintain session state across multiple interactions for end-to-end QA workflows.

Do I need a Node environment to run Playwright headless browser automation?▼

A Node and Playwright environment is required to run this headless browser automation, providing the runtime needed to execute deterministic navigation, interaction, and page state verification commands.

Related Skills

Explore More Software Engineering Skills→
cshyangcshyang

trigger-config

Configure Trigger.dev projects with trigger.config.ts for build extensions.

Community
Advanced
olaafrossiolaafrossi
10

gstack

Automate QA browser sessions with a persistent headless browser.

Community
Advanced
MathiasPaulenkoMathiasPaulenko

jmeter-load-testing

Execute Apache JMeter load tests with JSR223 Groovy scripting.

Community
Advanced
npc-chrisnpc-chris
1

browse

Automate headless browser navigation, form interaction, and screenshot comparison for QA testing.

Community
Advanced