Agent skill · software engineering · bighardperson
clawbrowser
Use when the agent needs to drive a browser through the Microsoft Playwright CLI (`playwright-cli`) for navigation, form interactions, screenshots, recordings, data extraction, session management, or debugging without loading a full MCP browser. It trains the agent on the CLI commands, snapshots, and session/config habits that make Playwright CLI reliable for scripted browsing.
Why this skill is useful
Adds specific Playwright CLI commands and session management patterns that the AI wouldn't reliably generate on its own.
What it needs
Requires @playwright/cli installed locally. About 3k tokens when loaded. Last updated 2026-04-26. 34 stars on the source repository.
What this skill does
Clawbrowser – browser control via Playwright CLI Setup & orientation 1. Install the CLI and verify availability: The CLI is headless by default; add --headed to open or set browser.launchOptions.headless to false in playwright-cli.json when you need to see the UI. 2. The CLI reads playwright-cli.json by default or whatever file you pass with --config. Use the config to tune browser name, launch/context options, viewport, timeouts, output directories, and recording settings without changing every command. 3. Keep playwright-cli --help terminal-accessible; the script self-documents the latest commands and options so you can refresh your memory before trying a new action. Core interaction loop 1. Start with playwright-cli open <url> to load the page (add --session=name if you want isolation up front). 2. Run playwright-cli snapshot to generate element refs (e1, e2, …) before any interaction. Always re-snapshot after DOM changes or navigation to avoid stale refs. 3. Use refs for actions: click, dblclick, hover, drag, check, uncheck, select, fill, type, upload, eval Append [button], [value], or JS snippets as needed (e.g., playwright-cli click e4 right). 4. Capture output evidence with screenshot [ref], pdf, console [level], or network to prove the flow or inspect errors. 5. Example flow: Sessions & persistence Use --session=<name> to keep cookies, storage, and tabs isolated per workflow. Sessions behave like persistent profiles: they remember auth state, history, and tabs between commands. Export PLAYWRIGHTCLISESSION=mysession if you are running many commands in the same session — the CLI will default to that session without needing --session each time. Manage sessions explicitly: Use playwright-cli --isolated open ... for ephemeral contexts that do not persist to disk. Whenever you change browser settings for a session (launch args, headless toggle, browser selection), rerun playwright-cli config for that session and then session-restart to apply the new config. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills bighardperson/ClawBrowser