browse

Drive a real browser to open pages, click flows, capture screenshots, and check console errors.

Updated Sep 13, 2026
One-click install
npx skills add https://github.com/abdulazeezoj/monovella-poc --skill browse-abdulazeezoj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/abdulazeezoj/monovella-poc/tree/main/.agents/skills/gstack/browse
Command: npx skills add https://github.com/abdulazeezoj/monovella-poc --skill browse-abdulazeezoj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright.

What problem does it solve? Verifying that a web page actually loads, renders, and behaves correctly requires opening a real browser, which agents cannot do by default. This Skill gives the agent eyes: it drives the user's real Aside browser (with existing logged-in sessions) or gstack's own headless Chromium fallback to inspect pages, click through flows, and collect evidence. ## Core Features & Use Cases - Page inspection: Open a URL, capture an interactive accessibility snapshot, page text, console errors, and a screenshot in one scripted pass. - Flow driving: Fill forms, click elements by ref or selector, and diff snapshots before and after each action to verify behavior. - Evidence capture: Take annotated, responsive (mobile/tablet/desktop), element-level, and full-page screenshots, plus PDF exports, saved into a report directory. - Use Case: After deploying a change, ask the agent to open the staging URL, click through the signup flow, and report console errors with before/after screenshots. ## Quick Start Ask the agent to open a URL with the browse skill and report what loads, including a screenshot and any console errors.

Frequently Asked Questions about browse

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

FAQPage Schema
How do I take a screenshot of a web page from an AI agent?

Invoke the browse skill with a target URL and it opens the page in the Aside browser or a headless Chromium fallback, then saves a JPEG screenshot to a report directory. The agent reads the screenshot back so you see it inline.

How do I check a page for JavaScript console errors automatically?

The browse skill installs a console hook before navigation that captures console.error calls, uncaught exceptions, and unhandled promise rejections. After loading the page it prints a CONSOLE_ERRORS line with the collected array, verbatim.

Can the agent use my logged-in browser sessions?

Yes, when driving the Aside browser on macOS the skill works inside your real tabs with your existing cookies and sessions. It never reads cookies or types passwords; if a sign-in wall appears, you sign in yourself and the agent re-runs the step.

What happens if the Aside browser is not installed or not running?

The skill falls back to gstack's own headless Chromium daemon, exposed through the $B command. The same cookbook steps translate one-to-one: goto, snapshot, click, fill, screenshot, and console error collection all work without Aside.

Will the agent submit forms or change settings on real websites?

On local targets (localhost, .test) mutating actions may proceed directly. On any non-local origin the skill stops and asks for explicit consent once per run before any submit, create, delete, or settings change, and it never follows logout or delete links.

Why does snapshot -i miss dropdown or autocomplete items?

Dropdown items rendered in React portals or popovers without ARIA roles are absent from Playwright's accessibility tree. The skill's cursor-interactive scan detects clickable non-ARIA elements and floating containers to surface those items as @c refs.