browse

Name: browse
Availability: InStock
Author: apeejay-education

Operate a persistent headless Chromium browser for QA testing and site dogfooding.

1|Updated Mar 26, 2026

Search Tags:#automation #debugging #browse #visual-regression #headless-browser #qa-testing

Ready to run

npx skills add https://github.com/apeejay-education/cadencesprout --skill browse-apeejay-education

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/apeejay-education/cadencesprout/tree/main/.agents/skills/gstack-browse
Command: npx skills add https://github.com/apeejay-education/cadencesprout --skill browse-apeejay-education

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA teams and developers need a fast, repeatable way to test websites and web apps without manual browser interaction. This skill provides a persistent headless browser to navigate URLs, interact with elements, verify page state, diff changes, take annotated screenshots, test responsive layouts, and handle dialogs—so you can dogfood features and file bug reports quickly.

Core Features & Use Cases

Persistent headless Chromium with session state across calls.
Navigate to URLs, interact with elements, verify states, and run checks with commands like goto, click, fill, and is.
Diff and annotate screenshots to capture precise evidence and support bug reports.
Test responsive layouts and forms, including file uploads, across multiple viewports.
Record and manage browser state (cookies, tabs) across sessions for end-to-end testing.

Quick Start

Load a URL with goto, verify elements, and capture annotated screenshots using the available commands.

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 headless browser by navigating to URLs, interacting with elements using click and fill commands, and verifying page states to run repeatable user-flow smoke tests without manual browser interaction.

Can I persist session state like cookies across multiple headless browser test runs?▼

Yes, you can persist browser state including cookies and tabs across sessions. This persistent headless Chromium maintains session state across calls, enabling seamless end-to-end testing and state verification across multiple interactions.

What is the best way to capture visual evidence for bug reports during web testing?▼

The best way to capture bug report evidence is using screenshot diffing and annotation. You can take annotated screenshots to capture precise visual evidence and diff changes to highlight exact UI regressions across responsive layouts.

Does this headless browser tool support testing responsive layouts across multiple viewports?▼

Yes, it supports testing responsive layouts across multiple viewports. You can use the responsive command to verify forms, file uploads, and UI behavior across different screen sizes within your automated test suites.

How do I test user flows that trigger dialogs in a headless Chromium environment?▼

Test user flows with dialogs by leveraging built-in dialog handling within the persistent headless Chromium environment. This allows automated interactions like click and fill to proceed smoothly while managing unexpected browser dialog interruptions.

Do I need a browser runtime to use headless browser commands for deployment verification?▼

Yes, a browser runtime is required to execute headless browser commands. Once the runtime is available, you can run goto, click, fill, and screenshot commands for deployment verification and site dogfooding.