dev-browser

Automate browser interactions via CLI-driven sandboxed JavaScript scripts.

Updated Jun 1, 2026

Search Tags:#automation #screenshots #cli #playwright #web-testing #browser

Ready to run

npx skills add https://github.com/zuzu59/z-skills --skill dev-browser-zuzu59

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dev-browser
Source: https://github.com/zuzu59/z-skills/tree/main/skills/dev-browser
Command: npx skills add https://github.com/zuzu59/z-skills --skill dev-browser-zuzu59

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Browser automation that controls browsers through sandboxed JavaScript scripts via CLI. Scripts run in a QuickJS WASM sandbox instead of Node.js, and do not use require, fetch, fs, or process.

Core Features & Use Cases

Persistent named pages across script runs via browser.getPage()
CLI-driven control of browsers with a sandboxed runtime
Connect to running Chrome/Chromium or Helium CDP endpoints for automation workflows

Quick Start

Install dev-browser globally and run a simple script to automate a browser session.

Frequently Asked Questions about dev-browser

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

FAQPage Schema

How do I automate browser tasks with persistent page states across sessions?▼

Browser automation with persistent named pages allows scripts to maintain state across runs via browser.getPage(). This CLI-driven approach connects to running Chrome or Helium CDP endpoints to manage and reuse specific pages.

Can I use Node.js modules like fs or fetch in a sandboxed browser automation script?▼

No, sandboxed browser automation scripts run in a QuickJS WASM sandbox instead of Node.js. This runtime restricts access to require, fetch, fs, or process, ensuring secure execution of web testing and navigation tasks.

How do I take screenshots and fill forms via CLI-driven browser automation?▼

You can fill forms and take screenshots by running a simple script through a globally installed CLI. The script drives browser interactions, automating web behavior testing and capturing page states during the session.

Does this browser automation tool support connecting to running Chrome or Chromium instances?▼

Yes, the browser automation CLI supports connecting to running Chrome, Chromium, or Helium CDP endpoints. This allows you to attach scripts to active browser sessions for seamless automation workflows.

What is a QuickJS WASM sandbox and why use it for web testing automation?▼

A QuickJS WASM sandbox is an isolated JavaScript runtime used for web testing automation instead of Node.js. It executes browser control scripts securely by blocking direct file system and process access, preventing unsafe operations.

Are there limitations when running browser automation scripts in a WASM sandbox?▼

Yes, the primary limitation is the lack of Node.js APIs. Scripts running in the QuickJS WASM sandbox cannot use require, fetch, fs, or process, meaning you must rely solely on the provided browser automation CLI commands.