browser-automation

Installation
SKILL.md

Browser automation

Self-Evolving Skill: This skill improves through use. If a step is wrong, Chrome or an MCP server changed behaviour, or a workaround was needed — fix this file (and scripts/chrome-profile.sh) immediately, don't defer. Only update for real, reproducible issues, and never add a real account, profile folder name or token.

Procedure here; the mechanics and measurements behind each rule are in references/doctrine.md. Scripts are in this plugin's scripts/; resolve the path with cc-plugin-root chrome-profiles (or use ~/.claude/plugins/marketplaces/cc-skills/plugins/chrome-profiles/scripts/).

CP="$(cc-plugin-root chrome-profiles)/scripts/chrome-profile.sh"

1. Pick the rung — start at the top

Rung Mechanism Use when
0. An API or OAuth token the site's API with a scoped, short-lived token from the vault/Keychain The site has an API for the job. No browser at all: the most reliable and the safest identity.
1. No browser, plain HTTP curl / httpx The page renders server-side.
2. A browser with its own profile the playwright-throwaway-headless MCP server or chromium.launch() (throwaway); a per-tool, sign-in-once profile on a debug port (chrome-debug-port-control.sh) You need JavaScript; and, if a login is needed, the tool signs in once in its own profile. The default for anything unattended.
3. Your real Chrome the servers below Supervised work that needs your own signed-in session, or a site that blocks automated browsers.
Installs
2
GitHub Stars
3
First Seen
Oct 22, 2026