browse

Name: browse
Availability: InStock
Author: Ingo

Run persistent headless Chromium browser tests with screenshots and DOM assertions.

Updated Aug 27, 2026

Search Tags:#automation #testing #debugging #screenshots #qa #playwright #browser

Ready to run

npx skills add https://github.com/ingoatl/propertycentral --skill browse-ingoatl

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a fast, persistent headless browser environment for automated QA testing and site dogfooding, enabling deterministic tests, evidence capture, and CI-friendly verification across deployments.

Core Features & Use Cases

Persistent headless Chromium with reusable state across tests (cookies, cookies, and sessions) for reliable QA runs.
Interact with pages, verify states, diff results, take annotated screenshots, and test forms and uploads.
Use cases include verifying new deployments, dogfooding user flows, and documenting bugs with visual evidence.

Quick Start

Launch a quick QA test by running a script that navigates to a page, interacts with elements, and captures a screenshot for evidence.

Frequently Asked Questions about browse

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I run automated QA testing in a CI pipeline without manual browser setup?▼

Automated QA testing in CI pipelines requires a fast headless browser with deterministic command latency and telemetry-friendly logging to enable repeatable deployment verification without manual setup.

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

Yes, persistent headless Chromium allows reusable state across tests, maintaining cookies and sessions for reliable QA runs and feature validation across different testing environments.

How do I capture screenshots as visual evidence for bug reproduction?▼

Screenshot capture for bug reproduction involves navigating to a URL, interacting with DOM elements, and taking annotated screenshots to document visual evidence of site states.

Does this headless browser support DOM state assertions and element interaction for feature validation?▼

Yes, headless browser environments support URL navigation, element interaction, DOM state assertions, and optional dialog and JavaScript handling for comprehensive feature validation and dogfooding.

What's the best way to verify new deployments using a headless browser?▼

Deployment verification is best achieved by running a ready-to-run preamble script in a fast headless browser to navigate pages, verify states, and diff results across environments.

Are there limitations when using headless browsers for automated testing and dogfooding?▼

Headless browser testing limitations involve ensuring deterministic command latency and handling optional JavaScript dialogs, requiring telemetry-friendly logging to maintain reliable test execution across CI pipelines.