claude-bowser
installsforks
How to install claude-bowser?
disler/bowser/claude-bowser
$npx -y skills add disler/bowser --skill claude-bowserObservable browser automation using Chrome MCP tools. Use when you need to browse websites, take screenshots, interact with web pages, or perform browser tasks in your current Chrome. Keywords - browse, screenshot, browser, chrome, bowser, ui testing, observable.
SKILL.md
| 1 | # Claude Bowser |
| 2 | |
| 3 | ## Purpose |
| 4 | |
| 5 | Automate browsing using Chrome MCP tools (`mcp__claude_in_chrome__*`) available when Claude Code is started with `--chrome`. This uses your real Chrome browser — observable, with your existing profile, cookies, and extensions. |
| 6 | |
| 7 | ## Pre-flight Check |
| 8 | |
| 9 | **Before doing anything**, verify Chrome MCP tools are available. Look for tools matching `mcp__claude_in_chrome__*`. |
| 10 | |
| 11 | - If available: proceed with the workflow. |
| 12 | - If NOT available: stop and reply to the user: _"Chrome tools are not available. Please restart Claude Code with the `--chrome` flag: `claude --chrome`"_ |
| 13 | |
| 14 | ## Workflow |
| 15 | |
| 16 | 1. Resize the browser window to 1440x900 |
| 17 | 2. Execute the user's request using Chrome MCP tools (navigate, click, screenshot, etc.) |
| 18 | 3. Report results back to the user |
| 19 | |
| 20 | ## Limitations |
| 21 | |
| 22 | - **No parallel instances.** All Chrome MCP connections share a single Chrome extension controller. Only one bowser task at a time. |
| 23 | - **Observable only.** This uses your real Chrome — there is no headless mode. |
People who liked this also viewed
6 picksType
- tddSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- test-driven-developmentUse when implementing any feature or bugfix, before writing implementation codeSkillsJul 2026
- qaSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- verification-before-completionUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidenceSkillsJul 2026
- webapp-testingToolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser lSkillsJul 2026
- playwright-best-practicesUse when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling authentication or OAuth, teSkillsJul 2026
