dev-browser

Drive the user's real Chrome end-to-end — doctor, open, snapshot, fill forms, click, type, screenshot, evaluate, navigate, autofill from the local profile. Two paths under one skill — extension-relay CLI (default, no `--remote-debugging-port`, no WebDriver banner) and headless `dev-browser run --connect` (fallback for sandboxed scripting, file uploads, and dedicated-profile authenticated SPA work). Use when the user asks to fill out a form, click on a page, screenshot the current tab, log into a site, automate "this page" / "active tab", post under an authenticated identity, or run any Playwright-style script against signed-in Chrome.

browserchromeautomation house featured

install · efd09da

# CLI (primary)

$ autovault add jack-arturo/skillissue@efd09da503770bce1de134fc485f62e65f1d38c3:skills/dev-browser/SKILL.md --sync-profiles

# MCP tool call

add_skill({ source: "github", identifier: "jack-arturo/skillissue@efd09da503770bce1de134fc485f62e65f1d38c3:skills/dev-browser/SKILL.md" })

→ vault validates · signs · syncs agent skill dirs

source: jack-arturo/skillissue

Why it exists

Sandbox Chromium has no cookies. Real work needs the logged-in browser. This skill encodes Path A (extension relay) vs Path B (debug port) so agents stop asking which to use.

History

0.3.x

Chrome 136+ killed debug ports on the default profile; Path A became structural. Autonomy contract documents gotchas so future runs do not re-ask.

How Jack actually uses it

Default Path A. Reach for Path B only for multi-step scripts, file uploads, or dedicated profiles.

What it is not

Not a generic tutorial. It's the house runbook for this machine and these agents.

docs-screenshot-packager

Package

Version 0.3.2 · install pin efd09da · SSOT skills/dev-browser/ on GitHub · agents: claude-code, codex