Skip to main content
skill CX Codex

browser-automation · civitai — Claude Code skill: what it does, how to install

browser-automation runs browser sessions behind an HTTP server, keeps auth profiles, and supports concurrent users. Useful for repeatable flows and multi-user checks.

Apache-2.0 ★ 7,327 updated 2026-10-25

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add civitai/civitai --skill browser-automation -a claude-code
Open on GitHub

What browser-automation does

This skill starts an HTTP service on localhost:9222. An agent can create or close browser sessions, inspect page state, capture screenshots, navigate to URLs, and run Playwright code. When several sessions are active, requests select one with session.

Reusable flows are stored as Playwright scripts in .browser/flows/*.js. Profiles keep authentication data under .browser/profiles/, while session screenshots go to .browser/sessions/{id}/screenshots/. The service also exposes endpoints for saving profiles, reviewing recorded chunks, and running stored flows.

It supports checks with profiles such as creator, member, moderator, and new-user, plus comparisons between a local HTML mockup and a live page. The HTTP endpoints are unavailable until server.mjs is running.

What it helps with

  • create browser sessions with separate user profiles
  • run Playwright actions against a page
  • reuse saved authentication between test runs
  • compare a local mockup with a live page
  • execute a stored flow from a chosen URL

Example prompts for the agent

  • Start server.mjs, create a member session, and inspect http://localhost:3000.
  • Create creator and viewer sessions, publish from the first one, then check the result in the second.
  • Save the current login as moderator and run a flow from .browser/flows/.

How to install browser-automation

1Skills CLI (Vercel)

npx skills add civitai/civitai --skill browser-automation -a claude-code

2Manually: put the files in place

~/.claude/skills/browser-automation/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/browser-automation/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about browser-automation

How do I install browser-automation in Claude Code?

Run npx skills add civitai/civitai --skill browser-automation -a claude-code, then open ~/.claude/skills/browser-automation/SKILL.md.

What does browser-automation do?

It exposes browser control through an HTTP server. The skill manages sessions, runs Playwright code, stores reusable flows and auth profiles, and returns page state or screenshots.

How does browser-automation handle multi-user testing?

Create separate sessions with different profiles and add ?session=name to requests. One session can act as creator while another checks the result as viewer.

Source text

SKILL.md · Apache-2.0
---
name: browser-automation
description: Browser automation via HTTP server. Supports multiple concurrent sessions for multi-user testing, saved flows, and profile-based auth persistence.
---

# Browser Automation Skill

Explore pages interactively, build reusable flows, and test multi-user scenarios.

## Quick Start

```bash
# Start server
node .claude/skills/browser-automation/server.mjs &

# Check available profiles
curl http://localhost:9222/profiles

# Create a session
curl -X POST http://localhost:9222/sessions \
  -d '{"name": "test", "url": "http://localhost:3000", "profile": "member"}'

# Inspect the page
curl http://localhost:9222/inspect

# Execute code
curl -X POST http://localhost:9222/chunk \
  -d '{"label": "Click button", "code": "await page.click(\"button.submit\");"}'

# Shutdown
curl -X POST http://localhost:9222/exit
```

## Endpoints

| Endpoint | Method | Description |
|----------|--------|-------------|
| `/profiles` | GET | List auth profiles with descriptions |
| `/sessions` | GET | List active sessions |
| `/sessions` | POST | Create session `{ name, url, profile?, headless? }` |
| `/sessions/:name` | DELETE | Close session |
| `/flows` | GET | List saved flows |
| `/flows/:name/run` | POST | Run flow `{ profile?, startUrl?, headless? }` |
| `/status` | GET | Session status |
| `/inspect` | GET | Page state + screenshot. Add `?fullPage=true` for full-page screenshot |
| `/chunk` | POST | Execute code `{ label, code }` |
| `/navigate` | POST | Navigate `{ url, fullPage? }`. Set `fullPage: true` for full-page screenshot |
| `/save-auth` | POST | Save auth `{ profile, description }` |
| `/review` | GET | Review recorded chunks |
| `/exit` | POST | Shutdown server |

Use `?session=name` when multiple sessions are active.

## Multi-User Testing

```bash
# Create two sessions with different profiles
curl -X POST http://localhost:9222/sessions \
  -d '{"name": "creator", "url": "http://localhost:3000", "profile": "creator"}'
curl -X POST http://localhost:9222/sessions \
  -d '{"name": "viewer", "url": "http://localhost:3000", "profile": "member"}'

# Creator does something
curl -X POST "http://localhost:9222/chunk?session=creator" \
  -d '{"label": "Publish", "code": "await page.click(\"button.publish\");"}'

# Viewer sees it
curl -X POST "http://localhost:9222/navigate?session=viewer" \
  -d '{"url": "http://localhost:3000/models"}'
```

## Profiles

```bash
# List profiles
curl http://localhost:9222/profiles

# Create new profile (description required)
curl -X POST http://localhost:9222/save-auth \
  -d '{"profile": "moderator", "description": "User with mod permissions"}'

# Refresh existing profile
curl -X POST http://localhost:9222/save-auth \
  -d '{"profile": "moderator"}'
```

| Profile | Description |
|---------|-------------|
| `moderator` | Mod permissions for content review |
| `creator` | Established user with published content |
| `member` | Standard logged-in user |
| `new-user` | Fresh account for onboarding flows |

## Flows

Saved flows are reusable Playwright scripts.

```bash
# List flows
curl http://localhost:9222/flows

# Run a flow
curl -X POST http://localhost:9222/flows/my-flow/run \
  -d '{"profile": "member"}'

# Run with custom start URL
curl -X POST http://localhost:9222/flows/my-flow/run \
  -d '{"profile": "member", "startUrl": "http://localhost:3000"}'
```

Flows are stored in `.browser/flows/*.js`.

## Playwright Code

Chunks execute with `page` available:

```javascript
await page.click('button.submit');
await page.fill('input[name="email"]', '[email protected]');
await page.waitForSelector('h1');
await page.goto('https://example.com');
const title = await page.textContent('h1');
```

## Mockup Comparison

Open local HTML mockups with `file://` URLs, then compare to live pages:

```bash
# 1. Open mockup and take full-page screenshot
curl -X POST http://localhost:9222/sessions \
  -d '{"name": "compare", "url": "file:///C:/path/to/mockup.html"}'
curl "http://localhost:9222/inspect?session=compare&fullPage=true"

# 2. Navigate to live page and screenshot
curl -X POST "http://localhost:9222/navigate?session=compare" \
  -d '{"url": "http://localhost:3000/page", "fullPage": true}'

# 3. Compare screenshots in session folder
```

## File Locations

- **Flows**: `.browser/flows/*.js`
- **Profile metadata**: `.browser/profiles/profiles.meta.json`
- **Auth state**: `.browser/profiles/*.json` (gitignored)
- **Screenshots**: `.browser/sessions/{id}/screenshots/`

© civitai · Apache-2.0 · civitai/civitai

Similar skills

All skills for Browser and scraping →

browser-automation by other authors comes first.

browser-automation sickn33 The browser-automation skill builds browser checks around observed UI state and explicit outcomes. Use it for UI workflows, timing failures, or authorised page-data collection. CX Codex +1 6,700installs browser-automation web-infra-dev browser-automation is a Claude Code and Codex skill that automates web interactions from screenshots via Midscene, without DOM selectors or accessibility tags. CX Codex +1 5,900installs browser-automation Alireza Rezvani browser-automation — a Claude Code skill that writes Playwright scripts for scraping, form filling, screenshots and saved sessions, plus the stealth settings that keep headless browsers from being blocked. CX Codex +1 636installs browser-automation borghei browser-automation is a Claude Code and Codex skill that scaffolds rate-limited Python requests scrapers and form scripts, then audits automation code for server overload and blocking risks. CX Codex +1 111installs browser-automation martinholovsky Directs agents to build browser automation with Playwright, CDP, and WebDriver using TDD and domain restrictions. CX Codex +1 235installs Browser Automation Claude Office Skills Browser Automation is a Claude Code skill that controls web pages through Puppeteer/Playwright. It covers scraping, browser-based tests, and repeatable web workflows. CX Codex +1 5,400installs browser-navigation Factory-AI browser-navigation automates browser tasks: page navigation, form filling, screenshots, data extraction, and session recording. CX Codex +1 120installs setup-browser-cookies garrytan setup-browser-cookies is a Claude Code skill that imports cookies from a local Chromium browser into a headless session. Runs when logging into test environments. CX Codex +1 379installs agent-browser-automation reason-machines The agent-browser-automation skill gives AI agents a headless browser through a Rust CLI and Chrome DevTools Protocol. Use it for pages, forms, snapshots, and screenshots. CX Codex +1 2,100installs sap-browser-automation secondsky The sap-browser-automation skill lets an agent inspect and operate authenticated SAP pages through a browser, Edge CDP, or Playwright. It covers SSO reuse, target checks, and screenshots. CX Codex +1 546installs browser brightdata This skill offloads local browser automation tasks to cloud infrastructure. It redirects traffic from drivers like Playwright, Puppeteer, or Selenium through a remote proxy server. CX Codex +1 183installs

From the same set11

The whole set →
quick-mockups quick-mockups generates 3 to 5 parallel UI mockups in HTML. Useful when you need to explore layouts, wireframes, and hierarchy variations before writing frontend code. CX Codex +1 1,700installs meilisearch-admin meilisearch-admin — a skill for monitoring Meilisearch: check indexes, tasks, server health, and search settings. Spot indexing errors and diagnose what's wrong with your search. CX Codex +1 132installs postgres-query postgres-query — a skill for Claude Code that executes PostgreSQL queries during debugging and performance analysis. It targets specific database environments with --prod or --dev flags under read-only mode. CX Codex +1 105installs agent-review Route code and prompts to external AI agents for review. Anthropic models use your local subscription via Claude Agent SDK; other models go through OpenRouter API. Useful for security audits, architecture validation, or a second opinion. CX Codex +1 3installs discord Posts messages, embeds, and announcements to Discord channels via REST API. Useful for team alerts and release notices during coding sessions. CX Codex +1 ★ 7,327repo stars clickhouse-query clickhouse-query runs ad-hoc ClickHouse queries from the chat: metrics, event data, execution plans. Read-only unless you say otherwise. CX Codex +1 ★ 7,327repo stars redis-inspect redis-inspect — a skill that reads keys, values and TTLs across two Redis instances, the main cache and the system cache. Handy when you need to see what the cache holds right now. CX Codex +1 ★ 7,327repo stars postgres-query postgres-query runs PostgreSQL queries, inspects index usage, and analyzes execution plans using read-only connections by default. CX Codex +1 ★ 7,327repo stars

Project sponsors

Companies that keep this analytics open