Agent skill
claude-bowser
Observable 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.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/claude-bowser
SKILL.md
Claude Bowser
Purpose
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.
Pre-flight Check
Before doing anything, verify Chrome MCP tools are available. Look for tools matching mcp__claude_in_chrome__*.
- If available: proceed with the workflow.
- If NOT available: stop and reply to the user: "Chrome tools are not available. Please restart Claude Code with the
--chromeflag:claude --chrome"
Workflow
- Resize the browser window to 1440x900
- Execute the user's request using Chrome MCP tools (navigate, click, screenshot, etc.)
- Report results back to the user
Limitations
- No parallel instances. All Chrome MCP connections share a single Chrome extension controller. Only one bowser task at a time.
- Observable only. This uses your real Chrome — there is no headless mode.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?