Stats
Actions
Tags
From bowser-qa
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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/bowser-qa:claude-bowserThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
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.
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.
Before doing anything, verify Chrome MCP tools are available. Look for tools matching mcp__claude_in_chrome__*.
--chrome flag: claude --chrome"npx claudepluginhub eduardoarantes/claude-code-plugin-marketplace --plugin bowser-qaControls Chrome via DevTools Protocol for navigating, clicking, typing, multi-tab management, and content extraction with auto-screenshots.
Automates Chrome browser using 70 tabz MCP tools for screenshots, form filling, network debugging, responsive design testing, performance profiling, DOM inspection, and TTS notifications.
Provides browser-level verification using Claude-in-Chrome (primary) or chrome-devtools-mcp (fallback). Includes provider detection, dev server detection, and graceful degradation.