home / skills / oimiragieo / agent-studio / chrome-browser
This skill unifies Chrome DevTools MCP and Claude-in-Chrome to automate testing, debugging, and authenticated demos across public and gated sites.
npx playbooks add skill oimiragieo/agent-studio --skill chrome-browserReview the files below or copy the command above to add this skill to your agents.
---
name: chrome-browser
description: Browser automation with two integrations - Chrome DevTools MCP (always available, performance tracing) and Claude-in-Chrome extension (authenticated sessions, GIF recording). Use DevTools for testing/debugging, Claude-in-Chrome for authenticated workflows.
version: 2.0.0
model: sonnet
invoked_by: both
user_invocable: true
tools:
# Chrome DevTools MCP (always available)
- mcp__chrome-devtools__click
- mcp__chrome-devtools__fill
- mcp__chrome-devtools__fill_form
- mcp__chrome-devtools__navigate_page
- mcp__chrome-devtools__new_page
- mcp__chrome-devtools__list_pages
- mcp__chrome-devtools__select_page
- mcp__chrome-devtools__close_page
- mcp__chrome-devtools__take_screenshot
- mcp__chrome-devtools__take_snapshot
- mcp__chrome-devtools__hover
- mcp__chrome-devtools__drag
- mcp__chrome-devtools__press_key
- mcp__chrome-devtools__evaluate_script
- mcp__chrome-devtools__handle_dialog
- mcp__chrome-devtools__resize_page
- mcp__chrome-devtools__emulate
- mcp__chrome-devtools__upload_file
- mcp__chrome-devtools__wait_for
- mcp__chrome-devtools__list_console_messages
- mcp__chrome-devtools__get_console_message
- mcp__chrome-devtools__list_network_requests
- mcp__chrome-devtools__get_network_request
- mcp__chrome-devtools__performance_start_trace
- mcp__chrome-devtools__performance_stop_trace
- mcp__chrome-devtools__performance_analyze_insight
# Claude-in-Chrome (requires --chrome flag)
- mcp__claude-in-chrome__computer
- mcp__claude-in-chrome__navigate
- mcp__claude-in-chrome__read_page
- mcp__claude-in-chrome__find
- mcp__claude-in-chrome__form_input
- mcp__claude-in-chrome__fill_form
- mcp__claude-in-chrome__javascript_tool
- mcp__claude-in-chrome__take_screenshot
- mcp__claude-in-chrome__gif_creator
- mcp__claude-in-chrome__tabs_context_mcp
- mcp__claude-in-chrome__tabs_create_mcp
- mcp__claude-in-chrome__read_console_messages
- mcp__claude-in-chrome__read_network_requests
- mcp__claude-in-chrome__upload_image
- mcp__claude-in-chrome__get_page_text
- mcp__claude-in-chrome__resize_window
- mcp__claude-in-chrome__shortcuts_list
- mcp__claude-in-chrome__shortcuts_execute
- mcp__claude-in-chrome__update_plan
best_practices:
- Use Chrome DevTools MCP for testing and debugging (always available)
- Use Claude-in-Chrome for authenticated workflows (Google Docs, Gmail)
- Filter console output with patterns to avoid verbosity
- Dismiss modal dialogs manually if they appear
error_handling: graceful
streaming: supported
---
# Chrome Browser Automation
<identity>
Chrome Browser Skill - Unified browser automation using TWO integrations: Chrome DevTools MCP (always available, performance tracing, network inspection) and Claude-in-Chrome extension (authenticated sessions, GIF recording).
</identity>
## Two Integrations - When to Use Each
| Feature | Chrome DevTools MCP | Claude-in-Chrome |
| ------------------------ | ------------------------------- | ------------------------------ |
| **Status** | ✅ Always available | ⚠️ Requires `--chrome` flag |
| **Activation** | Automatic (built-in) | `claude --chrome` + extension |
| **Auth sessions** | ❌ Fresh browser | ✅ Uses your logins |
| **Performance tracing** | ✅ Full Core Web Vitals | ❌ Not available |
| **Network inspection** | ✅ Detailed with body access | ✅ Basic |
| **Device emulation** | ✅ Mobile, geolocation, CPU | ❌ Limited |
| **GIF recording** | ❌ No | ✅ Yes |
| **Page text extraction** | Via snapshot | ✅ Dedicated tool |
| **Best for** | Testing, debugging, performance | Authenticated workflows, demos |
### Decision Guide
```
Need to test/debug a public site? → Chrome DevTools MCP
Need performance analysis? → Chrome DevTools MCP
Need to access authenticated apps? → Claude-in-Chrome (--chrome)
Need to record a demo GIF? → Claude-in-Chrome (--chrome)
Need to interact with Google Docs? → Claude-in-Chrome (--chrome)
Need device/network emulation? → Chrome DevTools MCP
```
<capabilities>
**Chrome DevTools MCP:**
- Page navigation and tab management
- Element interaction (click, fill, hover, drag)
- JavaScript execution in page context
- Console message monitoring
- Network request inspection with body access
- Performance tracing with Core Web Vitals
- Device emulation (mobile, geolocation, CPU throttling)
- Screenshot capture
- Dialog handling (alert, confirm, prompt)
**Claude-in-Chrome:**
- Authenticated web app interaction (Google Docs, Gmail, Notion)
- Session recording as GIF
- Natural language element finding
- Form automation with your saved data
- Page text extraction
- Shortcut/workflow execution
</capabilities>
<instructions>
<execution_process>
## Chrome DevTools MCP (Always Available)
No setup required - these tools work immediately.
### Step 1: List and Select Pages
```javascript
// List all open pages
mcp__chrome - devtools__list_pages();
// Select a page to work with
mcp__chrome - devtools__select_page({ pageId: 1 });
// Create a new page
mcp__chrome - devtools__new_page({ url: 'https://example.com' });
```
### Step 2: Navigate and Interact
```javascript
// Navigate to URL
mcp__chrome - devtools__navigate_page({ url: 'https://example.com' });
// Take accessibility snapshot (get element UIDs)
mcp__chrome - devtools__take_snapshot();
// Click element by UID from snapshot
mcp__chrome - devtools__click({ uid: 'ref_123' });
// Fill form field
mcp__chrome - devtools__fill({ uid: 'ref_456', value: '[email protected]' });
// Fill entire form
mcp__chrome -
devtools__fill_form({
elements: [
{ uid: 'ref_456', value: '[email protected]' },
{ uid: 'ref_789', value: 'password123' },
],
});
```
### Step 3: Debug and Inspect
```javascript
// Read console messages
mcp__chrome - devtools__list_console_messages({ types: ['error', 'warn'] });
// Get specific console message details
mcp__chrome - devtools__get_console_message({ msgid: 1 });
// List network requests
mcp__chrome - devtools__list_network_requests({ resourceTypes: ['xhr', 'fetch'] });
// Get request/response details
mcp__chrome - devtools__get_network_request({ reqid: 1 });
// Execute JavaScript
mcp__chrome -
devtools__evaluate_script({
function: '() => document.title',
});
```
### Step 4: Performance Analysis
```javascript
// Start performance trace (with page reload)
mcp__chrome - devtools__performance_start_trace({ reload: true, autoStop: true });
// Or manual stop
mcp__chrome - devtools__performance_start_trace({ reload: true, autoStop: false });
// ... interact with page ...
mcp__chrome - devtools__performance_stop_trace();
// Analyze specific insight
mcp__chrome -
devtools__performance_analyze_insight({
insightSetId: 'navigation-1',
insightName: 'LCPBreakdown',
});
```
### Step 5: Device Emulation
```javascript
// Emulate mobile device
mcp__chrome -
devtools__emulate({
viewport: {
width: 375,
height: 667,
deviceScaleFactor: 2,
isMobile: true,
hasTouch: true,
},
userAgent: 'Mozilla/5.0 (iPhone; CPU iPhone OS 16_0 like Mac OS X)...',
});
// Emulate slow network
mcp__chrome - devtools__emulate({ networkConditions: 'Slow 3G' });
// Emulate geolocation
mcp__chrome -
devtools__emulate({
geolocation: { latitude: 37.7749, longitude: -122.4194 },
});
```
---
## Claude-in-Chrome (Requires Setup)
### Prerequisites
1. **Install Claude-in-Chrome extension** (v1.0.36+) from Chrome Web Store
2. **Start Claude with flag**: `claude --chrome`
3. **Chrome must be visible** (no headless mode)
4. **Paid Claude plan** required (Pro, Team, or Enterprise)
### Step 1: Get Tab Context
```javascript
// ALWAYS call first to get available tabs
mcp__claude-in-chrome__tabs_context_mcp({ createIfEmpty: true })
// Create a new tab for this conversation
mcp__claude-in-chrome__tabs_create_mcp()
```
### Step 2: Navigate and Read
```javascript
// Navigate to URL
mcp__claude-in-chrome__navigate({ url: "https://docs.google.com", tabId: 123 })
// Read page structure (accessibility tree)
mcp__claude-in-chrome__read_page({ tabId: 123 })
// Find elements by natural language
mcp__claude-in-chrome__find({ query: "login button", tabId: 123 })
// Extract page text
mcp__claude-in-chrome__get_page_text({ tabId: 123 })
```
### Step 3: Interact
```javascript
// Click, type, screenshot via computer tool
mcp__claude-in-chrome__computer({
action: "left_click",
coordinate: [100, 200],
tabId: 123
})
mcp__claude-in-chrome__computer({
action: "type",
text: "Hello world",
tabId: 123
})
mcp__claude-in-chrome__computer({
action: "screenshot",
tabId: 123
})
// Fill form by element reference
mcp__claude-in-chrome__form_input({
ref: "ref_1",
value: "[email protected]",
tabId: 123
})
```
### Step 4: Record GIF Demo
```javascript
// Start recording
mcp__claude-in-chrome__gif_creator({ action: "start_recording", tabId: 123 })
// Take screenshot to capture initial state
mcp__claude-in-chrome__computer({ action: "screenshot", tabId: 123 })
// ... perform actions ...
// Take final screenshot
mcp__claude-in-chrome__computer({ action: "screenshot", tabId: 123 })
// Stop and export
mcp__claude-in-chrome__gif_creator({ action: "stop_recording", tabId: 123 })
mcp__claude-in-chrome__gif_creator({
action: "export",
download: true,
filename: "demo.gif",
tabId: 123
})
```
</execution_process>
<best_practices>
### Chrome DevTools MCP
1. **Always take snapshot first** to get element UIDs before clicking/filling
2. **Use includeSnapshot: true** on actions to get updated state
3. **Filter network requests** by resourceTypes to avoid noise
4. **Save traces to file** with filePath parameter for later analysis
### Claude-in-Chrome
1. **Call tabs_context_mcp first** to get valid tab IDs
2. **Create new tabs** rather than reusing existing ones
3. **Use read_page before find** to understand page structure
4. **Filter console with patterns** to avoid verbosity
5. **Dismiss modal dialogs manually** - they block all events
### General
1. **Prefer Chrome DevTools MCP** for public sites (always available)
2. **Use Claude-in-Chrome** only when authentication is required
3. **Don't trigger alert/confirm/prompt** - they block browser events
</best_practices>
</instructions>
<examples>
<usage_example>
**Test Login Flow (Chrome DevTools MCP)**:
```javascript
// Create page and navigate
mcp__chrome - devtools__new_page({ url: 'https://example.com/login' });
// Take snapshot to get element UIDs
mcp__chrome - devtools__take_snapshot();
// Fill login form
mcp__chrome -
devtools__fill_form({
elements: [
{ uid: 'email_field', value: '[email protected]' },
{ uid: 'password_field', value: 'testpass123' },
],
});
// Click submit
mcp__chrome - devtools__click({ uid: 'submit_button' });
// Check for errors
mcp__chrome - devtools__list_console_messages({ types: ['error'] });
```
</usage_example>
<usage_example>
**Performance Audit (Chrome DevTools MCP)**:
```javascript
// Navigate to page
mcp__chrome - devtools__navigate_page({ url: 'https://example.com' });
// Run performance trace with reload
mcp__chrome -
devtools__performance_start_trace({
reload: true,
autoStop: true,
filePath: 'trace.json.gz',
});
// Analyze LCP breakdown
mcp__chrome -
devtools__performance_analyze_insight({
insightSetId: 'navigation-1',
insightName: 'LCPBreakdown',
});
```
</usage_example>
<usage_example>
**Google Docs Editing (Claude-in-Chrome)**:
```javascript
// Get tab context
mcp__claude-in-chrome__tabs_context_mcp({ createIfEmpty: true })
// Navigate to Google Docs (uses your login)
mcp__claude-in-chrome__navigate({
url: "https://docs.google.com/document/d/YOUR_DOC_ID",
tabId: 123
})
// Read page to find elements
mcp__claude-in-chrome__read_page({ tabId: 123 })
// Click in document and type
mcp__claude-in-chrome__computer({
action: "left_click",
ref: "document_body",
tabId: 123
})
mcp__claude-in-chrome__computer({
action: "type",
text: "Meeting notes for today...",
tabId: 123
})
```
</usage_example>
<usage_example>
**Record Demo GIF (Claude-in-Chrome)**:
```javascript
// Start recording
mcp__claude-in-chrome__gif_creator({ action: "start_recording", tabId: 123 })
// Initial screenshot
mcp__claude-in-chrome__computer({ action: "screenshot", tabId: 123 })
// Navigate
mcp__claude-in-chrome__navigate({ url: "https://example.com/product", tabId: 123 })
mcp__claude-in-chrome__computer({ action: "screenshot", tabId: 123 })
// Click add to cart
mcp__claude-in-chrome__computer({ action: "left_click", ref: "add_to_cart", tabId: 123 })
mcp__claude-in-chrome__computer({ action: "screenshot", tabId: 123 })
// Stop and export
mcp__claude-in-chrome__gif_creator({ action: "stop_recording", tabId: 123 })
mcp__claude-in-chrome__gif_creator({
action: "export",
download: true,
filename: "add-to-cart-flow.gif",
options: { showClickIndicators: true, showProgressBar: true },
tabId: 123
})
```
</usage_example>
</examples>
## Available Tools
### Chrome DevTools MCP (Always Available)
| Tool | Description |
| --------------------------------------------------- | -------------------------------- |
| `mcp__chrome-devtools__list_pages` | List all browser pages |
| `mcp__chrome-devtools__select_page` | Select page for operations |
| `mcp__chrome-devtools__new_page` | Create new page with URL |
| `mcp__chrome-devtools__close_page` | Close a page |
| `mcp__chrome-devtools__navigate_page` | Navigate, reload, back/forward |
| `mcp__chrome-devtools__take_snapshot` | Get accessibility tree with UIDs |
| `mcp__chrome-devtools__take_screenshot` | Capture page/element screenshot |
| `mcp__chrome-devtools__click` | Click element by UID |
| `mcp__chrome-devtools__fill` | Fill input/select by UID |
| `mcp__chrome-devtools__fill_form` | Fill multiple form elements |
| `mcp__chrome-devtools__hover` | Hover over element |
| `mcp__chrome-devtools__drag` | Drag element to another |
| `mcp__chrome-devtools__press_key` | Press key or combination |
| `mcp__chrome-devtools__evaluate_script` | Execute JavaScript |
| `mcp__chrome-devtools__handle_dialog` | Accept/dismiss dialogs |
| `mcp__chrome-devtools__upload_file` | Upload file via input |
| `mcp__chrome-devtools__wait_for` | Wait for text to appear |
| `mcp__chrome-devtools__resize_page` | Resize browser window |
| `mcp__chrome-devtools__emulate` | Device/network/geo emulation |
| `mcp__chrome-devtools__list_console_messages` | List console output |
| `mcp__chrome-devtools__get_console_message` | Get message details |
| `mcp__chrome-devtools__list_network_requests` | List network requests |
| `mcp__chrome-devtools__get_network_request` | Get request/response details |
| `mcp__chrome-devtools__performance_start_trace` | Start performance recording |
| `mcp__chrome-devtools__performance_stop_trace` | Stop performance recording |
| `mcp__chrome-devtools__performance_analyze_insight` | Analyze performance insight |
### Claude-in-Chrome (Requires `--chrome` flag)
| Tool | Description |
| ---------------------------------------------- | ------------------------------- |
| `mcp__claude-in-chrome__tabs_context_mcp` | Get tab context (call first!) |
| `mcp__claude-in-chrome__tabs_create_mcp` | Create new tab |
| `mcp__claude-in-chrome__navigate` | Navigate to URL |
| `mcp__claude-in-chrome__read_page` | Get accessibility tree |
| `mcp__claude-in-chrome__find` | Find elements by description |
| `mcp__claude-in-chrome__get_page_text` | Extract page text |
| `mcp__claude-in-chrome__computer` | Click, type, screenshot, scroll |
| `mcp__claude-in-chrome__form_input` | Fill form field |
| `mcp__claude-in-chrome__fill_form` | Fill multiple fields |
| `mcp__claude-in-chrome__javascript_tool` | Execute JavaScript |
| `mcp__claude-in-chrome__read_console_messages` | Read console logs |
| `mcp__claude-in-chrome__read_network_requests` | Read network requests |
| `mcp__claude-in-chrome__resize_window` | Resize browser window |
| `mcp__claude-in-chrome__upload_image` | Upload image to element |
| `mcp__claude-in-chrome__gif_creator` | Record/export GIF |
| `mcp__claude-in-chrome__shortcuts_list` | List available shortcuts |
| `mcp__claude-in-chrome__shortcuts_execute` | Execute shortcut |
| `mcp__claude-in-chrome__update_plan` | Present plan for approval |
## Agent Integration
This skill is automatically assigned to:
- **developer** - Testing, debugging, data extraction
- **qa** - Automated testing, form validation, user flow verification
- **security-architect** - Security testing, authentication flows
- **devops-troubleshooter** - Production debugging, monitoring
- **researcher** - Web scraping, data extraction
## Related Workflow
For guidance on using this skill effectively, see the corresponding workflow:
- **Workflow File**: `.claude/workflows/chrome-browser-skill-workflow.md`
- **When to Use**: When you need browser automation for testing, debugging, authenticated workflows, or demo recording
- **Integration Methods**:
- Slash command invocation (`/chrome-browser`)
- Agent skill assignment (via frontmatter)
- Direct script execution
**Two Integration Options:**
- **Chrome DevTools MCP** (always available) - For public site testing, performance analysis, debugging
- **Claude-in-Chrome** (requires `--chrome` flag) - For authenticated app workflows, GIF recording
The workflow provides examples for invocation methods, agent assignment, and memory integration patterns.
## Troubleshooting
### Claude-in-Chrome "Browser extension is not connected"
**Symptom**: When using `--chrome` flag, tools return "Browser extension is not connected" error despite extension being installed.
**Root Cause**: Claude.app (desktop) and Claude Code register **competing native messaging hosts**. When both are installed, the Chrome extension connects to whichever registered last, causing connection failures.
**Diagnosis**:
1. Check if both Claude.app and Claude Code are installed
2. On Windows: Check `%APPDATA%\Claude\ChromeNativeHost\com.anthropic.claude_browser_extension.json`
3. On macOS: Check `~/Library/Application Support/Claude/ChromeNativeHost/`
**Known Bug**: This is documented in GitHub issues:
- [#15336](https://github.com/anthropics/claude-code/issues/15336) - Windows Native Messaging Host not installing
- [#14894](https://github.com/anthropics/claude-code/issues/14894) - Reconnect extension fails on macOS
- [#20790](https://github.com/anthropics/claude-code/issues/20790) - Extension connects to Claude.app instead of Claude Code
**Workaround (macOS)**:
```bash
# Disable Claude.app's native host (keep file for restoration)
cd ~/Library/Application\ Support/Google/Chrome/NativeMessagingHosts/
mv com.anthropic.claude_browser_extension.json com.anthropic.claude_browser_extension.json.disabled
# Restart Chrome completely (quit and reopen)
# Then start Claude Code with --chrome flag
```
**Workaround (Windows)**: Not fully documented. Potential approach:
```powershell
# Rename the config to disable Claude.app's registration
cd $env:APPDATA\Claude\ChromeNativeHost
ren com.anthropic.claude_browser_extension.json com.anthropic.claude_browser_extension.json.disabled
# Restart Chrome and try again
```
**Alternative**: Use **Chrome DevTools MCP** instead - it works without the extension and provides similar functionality for most use cases.
### Modal Dialogs Blocking Events
**Symptom**: After triggering alert/confirm/prompt, all browser tools stop responding.
**Cause**: JavaScript modal dialogs block all browser events including extension communication.
**Fix**: User must manually dismiss the dialog in the browser. Avoid triggering dialogs in automation scripts.
## Memory Protocol (MANDATORY)
**Before starting:**
```bash
cat .claude/context/memory/learnings.md
```
**After completing:**
- New pattern -> `.claude/context/memory/learnings.md`
- Issue found -> `.claude/context/memory/issues.md`
- Decision made -> `.claude/context/memory/decisions.md`
> ASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.
This skill unifies Chrome browser automation through two integrations: Chrome DevTools MCP (always available) and Claude-in-Chrome (authenticated sessions and GIF recording). It provides a consistent API for navigation, element interaction, network inspection, performance tracing, device emulation, and authenticated workflows. Use DevTools MCP for debugging and performance analysis and Claude-in-Chrome when you need access to logged-in sessions or to record demos.
Chrome DevTools MCP connects to a local Chrome instance and exposes page snapshots, network details (including bodies), Core Web Vitals tracing, device emulation, and direct DOM interactions using element UIDs. Claude-in-Chrome runs as a browser extension with the Claude agent; it provides natural-language element finding, page text extraction, form automation using your saved credentials, and GIF recording of visible browser interactions. Choose the integration based on availability and whether authentication or recording is required.
Do I need any setup to use Chrome DevTools MCP?
No. DevTools MCP is always available and requires no extra flags or extensions.
When should I enable Claude-in-Chrome?
Enable Claude-in-Chrome when you need authenticated sessions, natural-language element finding, or GIF recording; it requires installing the extension and starting Claude with --chrome.