Dev Browser

Browser automation with persistent named pages via the dev-browser CLI. Use when users ask to navigate websites, fill forms, take screenshots, extract web data, test web apps, log into sites, or automate browser workflows. Trigger phrases include "go to [url]", "click on", "fill out the form", "take a screenshot", "scrape", "automate", "test the website", "log into", "open the browser", or any browser interaction request.

6,740 stars 443 forksTesting & QA Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add SawyerHood/dev-browser

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add SawyerHood/dev-browser --skill dev-browser
Manual install
git clone --depth 1 https://github.com/SawyerHood/dev-browser.git /tmp/dev-browser
mkdir -p ~/.claude/skills
cp -r /tmp/dev-browser/skills/dev-browser ~/.claude/skills/dev-browser

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# dev-browser

CLI for controlling a real Chrome with short Puppeteer scripts. One warm daemon; named pages persist between runs.

```bash
npm install -g dev-browser   # bun add -g dev-browser works too; the first run downloads the binary if the install script was blocked
dev-browser install          # only if the first run says "No Chrome found"
```

Run `dev-browser --help` (full guide; `dev-browser help <topic>` for one section) before non-trivial work. Quick start:

```bash
dev-browser <<'EOF'
const page = await browser.getPage("main");        // named page persists across runs
await page.goto("https://example.com");            // default waitUntil: domcontentloaded
await page.snapshot({ interactive: true })         // ARIA tree with refs; last expression is printed
EOF
dev-browser -e 'const p = await browser.getPage("main"); await p.click("ref/e6"); await p.waitForLoad(); p.url()'
```

Gotchas: end lines with semicolons (a line starting with `(` continues the previous one); return an object as
`({ a, b })`; `page.click` never waits (use `waitForSelector` first); page names are per browser (`--headless` and
headed are separate Chromes and profiles); refs reset on navigation — re-snapshot; file paths resolve against your cwd
(uploadFile, screenshot/pdf `path`); do not run parallel dev-browser calls against the same named page.
Read the full skill on GitHub

Details

Skill name
dev-browser
Path
skills/dev-browser/SKILL.md
License
MIT
Repo updated
3 November 2026
Copies
Found in 2 GitHub repos

FAQ

What does the Dev Browser skill do?

Browser automation with persistent named pages via the dev-browser CLI. Use when users ask to navigate websites, fill forms, take screenshots, extract web data, test web apps, log into sites, or automate browser workflows. Trigger phrases include "go to [url]", "click on", "fill out the form", "take a screenshot", "scrape", "automate", "test the website", "log into", "open the browser", or any browser interaction request.

How do I install the Dev Browser skill?

Claude Code plugin: /plugin marketplace add SawyerHood/dev-browser. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Dev Browser popular?

It lives in SawyerHood/dev-browser, which has 6,740 GitHub stars and 443 forks, and is included in 2 curated skill lists.

Related skills

Pua

20k

tanweai/pua

Use for PUA/try-harder productivity coaching when the user expresses frustration, repeated failure, quality complaint, passive behavior, says retry/change approach/don't give up, asks for evidence/completion check/test before done, or wants Ding-style workplace reminders. Triggers include: try harder, stop giving up, figure it out, again??, why still failing, change approach, no evidence, run tests, done without proof, 换个方法, 再试试, 别摆烂, 别偷懒, 为什么还不行, 又错了, 证据呢, 没跑测试别说完成, 验收, 闭环, 自嗨, 置身钉外, 无招, 老板体感. Do not use for calm first-attempt requests.

Testing & QAIn 1 list1.2k

Typescript Testing

31k

ComposioHQ/composio

Select and run TypeScript SDK verification for packages, examples, type checks, linting, builds, Vitest suites, Effect v4 CLI tests, and runtime E2E tests. Use when adding tests, diagnosing TypeScript CI, choosing a focused test command, validating TypeScript package changes, or writing/porting CLI tests against effect@^4.1.0 and @effect/vitest. Do not use for Python-only checks.

Testing & QAIn 1 list5k

Good Skill Complex

18k

larksuite/cli

A very complex description that spans multiple lines and contains weird chars: !@#$%^&*()

Testing & QA1.4k

Python Testing

31k

ComposioHQ/composio

Select and run Python SDK verification with nox, Makefile targets, Ruff, mypy, pytest markers, sanity tests, type inference checks, and build checks. Use when adding Python tests, diagnosing Python CI, or validating Python SDK/provider changes. Do not use for TypeScript-only checks.

Testing & QAIn 1 list5k

Break

12k

jakubkrehel/skills

Renders a component you choose under every scenario that can reach it on a temporary page and stress tests it.

Testing & QA483

CLI E2E

31k

ComposioHQ/composio

Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.

Testing & QAIn 1 list5k

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.