Domain

/brave

Use as fallback browser automation when Claude-in-Chrome MCP is unavailable. Covers browser control, navigation, screenshots, clicking, typing. NOT for: headless testing (use Playwright). Claude Code users should prefer MCP first.

$ golems-cli skills install brave
Experimental
92% best pass rate
13 assertions
3 evals
4 workflows

Updated 2 weeks ago

Browser automation via brave-manager CLI. Claude Code should prefer Claude-in-Chrome MCP - use brave-manager as fallback.

Prerequisites Check

1. Check brave-manager installed:

which brave-manager || echo "Not installed"

2. Launch Brave with debug port enabled:

# Close Brave completely first, then:
open -a 'Brave Browser' --args --remote-debugging-port=9222

If Brave is already running without the debug flag, quit it completely and relaunch.

3. Verify connection:

brave-manager tabs

If not installed or connection issues: See workflows/debugging.md


Quick Actions

What you want to doWorkflow
Navigate, switch tabs, page historyworkflows/navigation.md
Get element IDs, take screenshots, see errorsworkflows/inspection.md
Click, type, scroll, drag elementsworkflows/interaction.md
Run JS eval, verify state, debugworkflows/debugging.md

Core Concept: ID-Based Interaction

Always inspect first! Before clicking or typing:

brave-manager inspect

This:

  1. Numbers all interactive elements on the page
  2. Draws red labels for visual reference
  3. Returns the ID mapping for use with click/type/hover

Workflows

/brave:inspection/brave:navigation/brave:interaction/brave:debugging