gstack

Controls a persistent headless Chromium browser for QA testing, interaction, and screenshot capture.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/bobbo01/B2BPlatform --skill gstack-bobbo01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/bobbo01/B2BPlatform/tree/main/.agents/skills/gstack
Command: npx skills add https://github.com/bobbo01/B2BPlatform --skill gstack-bobbo01

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bun.

What problem does it solve? Manually verifying web pages, user flows, and deployments is slow and error-prone. This Skill gives an AI agent a persistent headless Chromium browser so it can navigate pages, click elements, fill forms, assert state, and capture annotated screenshots as bug evidence. ## Core Features & Use Cases - Interactive page control: Navigate URLs, snapshot accessibility trees with @e refs, click, fill, hover, upload files, and handle dialogs through a single CLI binary. - State verification and diffing: Assert element visibility, enabled/checked state, console errors, and network failures, and diff snapshots before and after actions to confirm changes. - Visual evidence capture: Take full-page, element, region, and responsive (mobile/tablet/desktop) screenshots, plus annotated screenshots labeling every interactive element. - Use Case: After deploying a new login flow, ask the agent to open the staging URL, fill credentials, submit the form, verify the dashboard appears, check the console for errors, and save an annotated screenshot as proof. ## Quick Start Ask the agent to open your site with gstack browse, walk through the login flow, and screenshot the result.

Frequently Asked Questions about gstack

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

FAQPage Schema
How do I test a login flow with a headless browser?

Navigate to the login page with goto, run snapshot -i to list interactive elements, fill the email and password fields by their @e refs, click submit, then use snapshot -D to diff the result and is visible to assert the dashboard appeared.

How do I test responsive layouts across mobile and desktop?

Run the responsive command with an output prefix to capture screenshots at 375x812, 768x1024, and 1280x720 in one step. For a specific device, set an exact size with viewport and then take a screenshot.

Can I test authenticated pages without logging in manually?

Yes. Use cookie-import-browser to import session cookies from an installed Chromium browser, optionally filtered by domain. After import, navigating to authenticated pages reuses the real login session.

How do I capture bug evidence with screenshots?

Use snapshot -a -o to produce an annotated screenshot with red overlay boxes and ref labels on every interactive element. Read the output PNG afterward so the image is visible in the conversation for the bug report.

Why do my element refs stop working after navigation?

Refs from snapshot are invalidated whenever the page navigates or reloads. Run snapshot again after any goto or reload to get fresh @e refs before clicking or filling elements.