browser-mate
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.
What this skill does
# 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
```bash
# 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:
```bash
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:
```json
{ "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`.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.