Browser Mate Skill for Claude

Use when automating a real, logged-in Chrome WITHOUT disturbing the user's open tabs — e.g. authenticated sessions like ChatGPT, LinkedIn, or any site needing a persistent login. Launches or reuses a dedicated debug Chrome instance per named profile that coexists with the user's main browser; it never quits or kills any browser (unlike real-browser, which closes Chrome Beta's tabs). Trigger on "automate this site without closing my tabs", "use my logged-in session", "open ChatGPT/LinkedIn in automation", or when a browser task must preserve the user's existing windows. macOS, requires the agent-browser CLI.

4k tokens

context cost

the whole folder, loaded on every use

files

ships runnable scripts

copies elsewhere

how many repositories repackaged it

337

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/glebis/claude-skills --skill browser-mate

What comes with it

12 005 bytes besides the instruction

assets/profiles.example.json

references/agent-browser.md

scripts/browser.py

The instruction itself

6 sections, as written by the author

browser-mate

Non-destructive Chrome automation. The problem it solves: to attach a CDP/agent-browser

session, Chrome must run with --remote-debugging-port. The real-browser skill achieves

this by quitting Chrome Beta first, destroying the user's open tabs. browser-mate

instead runs a dedicated debug Chrome instance (its own --user-data-dir + port) that

coexists with the user's main browser — Chrome permits concurrent instances when the

data dirs differ, so no quit is needed.

The one invariant (never violate)

Never quit, pkill, or osascript quit any browser. The skill only ever launches a

new dedicated instance or reuses an existing one. The single stop path sends SIGTERM only

to a process matched by BOTH our dedicated user_data_dir AND our debug port — never the

user's browser.

Usage

# Ensure a profile's debug Chrome is up (launch or reuse); prints the PORT on stdout
PORT=$(python3 scripts/browser.py chatgpt)

# Then drive it with agent-browser (always pass --cdp $PORT). See references/agent-browser.md
SID=$(LC_ALL=C tr -dc 'a-z0-9' < /dev/urandom | head -c 6)
agent-browser --cdp $PORT --session $SID open "https://chatgpt.com/"
agent-browser --cdp $PORT --session $SID snapshot -i

Other subcommands:

python3 scripts/browser.py list              # configured profiles
python3 scripts/browser.py status [profile]  # up/down
python3 scripts/browser.py stop chatgpt      # SIGTERM OUR instance only (graceful)

For the full agent-browser command set (click, fill, upload, screenshot, reliability,

upgrade gotchas), read references/agent-browser.md.

Profiles

Config: ~/.config/browser-mate/profiles.json (auto-created from assets/profiles.example.json

on first run). Each profile:

{ "default": "automation",
  "profiles": {
    "automation": { "binary": "<chrome binary>", "user_data_dir": "~/.browser-mate/automation", "port": 9222 },
    "chatgpt":     { "binary": "<chrome binary>", "user_data_dir": "~/.browser-mate/chatgpt", "port": 9223, "default_url": "https://chatgpt.com/" }
  } }

Each profile keeps its own login state — log in once per profile, it persists.
Add a profile by editing the JSON: pick a unique port and a dedicated user_data_dir

(the launcher validates uniqueness and refuses dirs that point at the user's real Chrome

profile).

Authentication

Cannot enter passwords (and must not). For a first-time login, launch the profile, then ask

the user to log in manually in that window once; the session persists in the profile's

user_data_dir for all future runs.

Safety & limits

Loopback only. The debug port binds to 127.0.0.1 (Chrome default). CDP has no auth

— anyone local can drive it. Use on trusted machines; never pass --remote-debugging-address.

Dedicated data dir. A profile's user_data_dir must never be the user's real Chrome

profile (~/Library/Application Support/Google/Chrome*) — the launcher refuses these.

Locked dir. If a profile's dir is already open in a non-debug Chrome window, the

launcher fails loudly rather than killing it.

Replaces real-browser's launch step; interaction still uses agent-browser.

Other skills for the same job

different authors, same section of the catalogue

Autonomous Agent Patterns

by ComeOnOliver

×1

Design patterns for building autonomous coding agents. Covers tool integration, permission systems, browser automation, and human-in-the-loop workflows. Use when building AI agents, designing tool APIs, implementing permission systems, or creating autonomous coding assistants.

Use when the user says "use the DevTools skill" or when they need help debugging a web app with Chrome DevTools MCP (UI bugs, incorrect behavior, console errors, network/API failures, or performance/lag), especially if the user seems inexperienced and needs guided, step-by-step diagnosis.

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

Use this when working on the VS Code integrated browser ("browserView") to understand its architecture and mental model. Covers the embedded Chromium browser, its editor tab, navigation, overlay/layout, sessions, and agent browser tools under `src/vs/platform/browserView` and `src/vs/workbench/contrib/browserView`.

3k tokens

Cua Driver

by ThinkInAIXYZ

Drive a native macOS app via the cua-driver MCP server or CLI — snapshot its AX tree, click/type/scroll by element_index, verify via re-snapshot. Use when the user asks you to operate, drive, automate, or perform a GUI task in a real macOS application on the host (e.g. "open a file in TextEdit", "navigate to /Applications in Finder", "click the Save button in Numbers").

EAS service (paid). Run and control a user's app on a remote iOS/Android simulator hosted on EAS cloud. Read before running any `eas simulator:*` commands - it has the current syntax for this experimental API. Use whenever the user needs a simulator they can't run locally - 'run my app on a cloud simulator', 'use eas simulator to run/install/screenshot my app', 'I'm on Linux/Cursor and need an iOS device', 'no sim on this box / headless CI', 'let an agent click through my app and screenshot it', 'test my dev build on a remote sim with live reload', 'stream a sim to my browser' - even when they don't say 'EAS Simulator' or 'cloud'. On a host WITHOUT a local simulator (Linux, CI, cloud sandbox) it's the default; on macOS, do NOT auto-trigger for a plain 'run on the simulator' - use it only for a cloud/remote/shareable sim, an iOS version they lack, or an agent-driven session. NOT for local sims (expo run:ios, Xcode, Android Studio), EAS Build/Update, web preview, or physical devices.

12k tokens

Scrapling Skill

by daymade

Install, troubleshoot, and use Scrapling CLI to extract HTML, Markdown, or text from webpages. Use this skill whenever the user mentions Scrapling, `uv tool install scrapling`, `scrapling extract`, WeChat/mp.weixin articles, browser-backed page fetching, or needs help deciding between static and dynamic extraction.

4k tokens scripts

Goose Graphics

by gooseworks-ai

Portable visual skill pack for the Agent Skills ecosystem (Claude Code, Claude Desktop, Claude Cowork, Claude Design, Goose, Cursor, Codex). Discovers community-published styles + formats via the gooseworks CLI, runs an extract-style workflow on reference images, and exports rendered PNGs via Playwright.

23k tokens scripts

How to use it

Copy the folder

Take glebis/browser-mate from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.