gateway-browser

Automate browser actions like navigate, click, type, and screenshot in verifiable steps.

12|3|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/baibairui/WoClaw --skill gateway-browser
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gateway-browser
Source: https://github.com/baibairui/WoClaw/tree/main/.codex-runtime/home/.agents/skills/gateway-browser
Command: npx skills add https://github.com/baibairui/WoClaw --skill gateway-browser

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automates browser-based tasks within a controlled Skill context, providing observable and reversible web interactions for AI-driven workflows.

Core Features & Use Cases

  • Bundled gateway-browser script executes browser actions (snapshot, navigate, click, type, screenshot) in small, verifiable steps with per-action state capture.
  • Collects evidence through screenshots, console traces, and structured reports to inform next steps and debugging.
  • Use Case: validate UI flows, gather live page state, and perform automated checks inside a long-running Agent workflow.

Quick Start

Invoke the gateway-browser.mjs script with a command such as navigate --url https://example.com to start browser actions.

Frequently Asked Questions about gateway-browser

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

FAQPage Schema
How do I automate browser actions and capture screenshots for AI workflows?

Automate browser actions and capture screenshots by invoking a bundled script that executes navigate, click, type, and snapshot commands in small, verifiable steps. It collects structured reports and screenshots to provide observable web interactions for AI-driven workflows.

What is the best way to validate UI flows and gather live page state automatically?

Validate UI flows and gather live page state by running automated browser actions within a controlled context. The script enforces stop conditions and collects evidence through screenshots and console traces, informing next steps and debugging inside a long-running Agent workflow.

How do I collect evidence like screenshots and console traces during web automation?

Collect evidence during web automation by executing iterative browser actions that capture screenshots, console traces, and structured reports. This per-action state capture mechanism ensures every interaction is verifiable and provides context for debugging automated checks.

Does browser automation work within a controlled Agent workflow without external dependencies?

Browser automation works within a controlled Agent workflow using a bundled script and environment variables for secure operation. It requires no external dependencies, relying entirely on internal components to enforce stop conditions and manage observable web interactions.

Why should I use reversible browser interactions for automated web checks?

Reversible browser interactions ensure that automated web checks remain observable and debuggable. By capturing per-action state and evidence like screenshots, you can trace iterative steps, validate UI flows accurately, and maintain control over long-running automation tasks.