browse

Name: browse
Availability: InStock
Author: filipnyquist

Drive a headless browser to automate QA tasks on web apps.

Updated Mar 29, 2026

Search Tags:#automation #screenshots #qa #playwright #web-testing #browser #dogfooding

Ready to run

npx skills add https://github.com/filipnyquist/caidos --skill browse-filipnyquist

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/filipnyquist/caidos/tree/main/.claude/skills/gstack/browse
Command: npx skills add https://github.com/filipnyquist/caidos --skill browse-filipnyquist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The gstack browse skill provides a fast, automated way to test web features by driving a headless browser to navigate URLs, interact with elements, verify states, diff changes, and capture annotated screenshots for bug reports. It reduces manual QA overhead and enables consistent, repeatable tests in CI or local work.

Core Features & Use Cases

Navigate to pages, fill forms, click controls, and validate UI outcomes.
Diff screen states before and after actions and generate annotated evidence for bug reports.
Validate responsive layouts, handle dialogs, and test forms and file uploads across viewports for reliable dogfooding.

Quick Start

Open a URL and perform a simple interaction to verify the page behavior.

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 for web apps with a headless browser?▼

Automate web app QA testing by driving a headless browser to navigate pages, interact with elements, and validate outcomes. It captures annotated screenshots and state diffs to provide reproducible evidence for bug reports across CI or local environments.

Can I capture screenshots and diff page states for bug reproduction?▼

Yes, you can diff screen states before and after actions to generate annotated screenshots for bug reproduction. This provides deterministic, reproducible evidence of UI changes and layout failures during regression checks.

Does this web testing skill require Playwright with Bun to run?▼

Yes, this web testing skill requires a compatible runtime using Playwright with Bun. This setup enables fast, deterministic execution of browser automation commands for feature testing and regression checks in your local or CI environment.

What's the best way to validate responsive layouts and handle dialogs during regression checks?▼

The best way to validate responsive layouts and handle dialogs is by driving a headless browser across multiple viewports. This enables reliable dogfooding by testing forms, file uploads, and UI interactions deterministically.

How do I run feature testing and reproduce bugs in a CI environment?▼

Run feature testing and reproduce bugs in CI by executing deterministic browser actions via a robust command surface. The headless browser reports validation results and state diffs directly to the caller for consistent, repeatable regression checks.