browse

Name: browse
Availability: InStock
Author: lemig

Drive a local headless Chromium browser for QA testing and screenshot capture.

Updated May 14, 2026

Search Tags:#automation #screenshots #qa #browser #headless

Ready to run

npx skills add https://github.com/lemig/transcriptor --skill browse-lemig

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a fast, local headless browser for QA testing to verify features, regression fixes, and bug reproduction without relying on cloud services.

Core Features & Use Cases

Navigate to arbitrary URLs, interact with elements, and verify page state.
Capture annotated screenshots and diffs to aid bug reports and feature verification.
Validate responsive layouts and interact with forms, dialogs, and uploads across scenarios.

Quick Start

Launch the browser, navigate to a URL, perform interactions, and capture annotated screenshots to verify behavior.

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 locally without cloud services?▼

You can automate headless browser QA testing locally by driving a fast Chromium-based environment to verify features, reproduce bugs, and run regression checks without relying on cloud services.

Can I capture annotated screenshots during automated browser regression checks?▼

Yes, you can capture annotated screenshots and diffs during automated browser regression checks to aid bug reports and verify feature behavior across arbitrary URLs.

What interactions are supported for headless browser feature verification?▼

Headless browser feature verification supports interacting with elements, validating page state, handling form submissions, dialogs, and uploads across various scenarios.

Do I need a local Chromium-based environment to validate responsive layouts?▼

Yes, you need a local Chromium-based environment to validate responsive layouts, interact with elements, and verify page state without depending on external cloud services.

Why use a local headless browser instead of cloud services for bug reproduction?▼

Using a local headless browser for bug reproduction provides fast navigation, interaction, and screenshot capture without the latency, cost, or external dependencies associated with cloud services.