| id | claude-browser |
| name | claude-browser |
| type | skill |
| version | 1.0.0 |
| created | 20/03/2026 |
| modified | 20/03/2026 |
| status | active |
| metadata | {"author":"NodeJS-Starter-V1","version":"1.0.0","locale":"en-AU"} |
| description | >- |
| context | fork |
Claude Browser — Chrome Extension Automation
Personal browser automation using Claude's Chrome extension MCP tools. Operates in the user's actual browser session with full access to logged-in state, cookies, and extensions.
When to Apply
Positive Triggers
- Personal browser automation (logged-in sessions)
- Form filling in authenticated web apps
- Reading content from pages requiring login
- Interactive demonstrations and walkthroughs
- GIF recording of browser workflows
- Tab management and multi-page navigation
Negative Triggers (Do NOT Apply)
- CI/CD pipeline testing (use
playwright-browser skill)
- Parallel test execution (Chrome extension is single-session)
- Headless browser operations
- Performance/load testing
Core Principles
- Single-session — one browser, one user, one context at a time
- User's actual browser — leverages existing login state and cookies
- Personal context — for tasks that require the user's authenticated session
- Always capture evidence — use
gif_creator or upload_image for visual records
- Tab-aware — always call
tabs_context_mcp at session start
Navigation + Reading
| Tool | Purpose |
|---|
navigate | Navigate to URL in current tab |
read_page | Read full page content (structured) |
get_page_text | Get plain text content |
find | Search for text/elements on page |
Interaction
| Tool | Purpose |
|---|
form_input | Fill form fields |
computer | Mouse/keyboard simulation |
javascript_tool | Execute JavaScript in page |
Tab Management