browse

Run automated headless browser tests on user-provided URLs with screenshots and diffs.

8|2|Updated Mar 24, 2026

Search Tags:#browser automation #ui interaction #responsive testing #qa testing #headless chromium #screenshot evidence #web diff

Ready to run

npx skills add https://github.com/MFS-code/gstack --skill browse-mfs-code

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of slow, unreliable manual QA by letting you quickly load a URL, interact with the UI, and capture evidence to confirm what changed.

Core Features & Use Cases

Fast automated browsing for QA: navigate to any URL, interact with page elements, and assert element state.
Evidence-grade outputs: take screenshots and annotated screenshots, plus unified diffs before/after actions.
Robust interaction for real sites: handle dialogs, file uploads, responsive layout checks, and stateful sessions across calls.

Quick Start

Tell your AI agent: “Use /browse to open https://example.com, submit a login form using the provided fields, and take an annotated screenshot plus a diff showing what changed.”

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 testing for UI interaction and navigation?▼

Automated headless browser testing validates web application behavior by running navigation, interaction, and state assertions on arbitrary user-provided URLs. It handles dialogs, file uploads, and responsive layout checks while preserving sessions across calls.

How do I take annotated screenshots for bug report evidence?▼

Capture evidence-grade screenshots and unified diffs before and after UI actions to document web application behavior. This Skill produces annotated visual proof of state changes directly from headless browser sessions for bug reports.

Can I verify deployment changes using web diff screenshots?▼

Web diff screenshots confirm what changed after a release by loading arbitrary URLs, performing UI interactions, and generating unified diffs. This Skill validates deployment behavior by capturing visual evidence of state changes.

Does headless chromium support stateful sessions for responsive testing?▼

Headless Chromium supports stateful responsive testing by preserving browser state across calls to check layouts, handle dialogs, and manage file uploads. This Skill maintains session continuity for multi-step QA workflows.

What is the best way to handle dialogs and file uploads in automated QA testing?▼

Automated QA testing handles dialogs and file uploads through robust interaction capabilities designed for real sites. This Skill manages these complex interactions statefully while capturing screenshots and diffs as evidence.

Why does browser automation fail to preserve state across multiple calls?▼

Browser automation fails to preserve state without retry-aware error handling and session continuity. This Skill applies deterministic command execution and preserves browser state across calls to maintain reliable stateful testing.