From tabz
Automates Chrome browser using 70 tabz MCP tools for screenshots, form filling, network debugging, responsive design testing, performance profiling, DOM inspection, and TTS notifications.
How this skill is triggered — by the user, by Claude, or both
Slash command
/tabz:browserThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Control Chrome via MCP tools for screenshots, interaction, debugging, and notifications.
Control Chrome via MCP tools for screenshots, interaction, debugging, and notifications.
Use mcp-cli to discover and call tools:
# Get tool schema (REQUIRED before calling)
mcp-cli info tabz/tabz_screenshot
# Call tool
mcp-cli call tabz/tabz_screenshot '{}'
# Get current tab info
mcp-cli call tabz/tabz_get_page_info '{}'
# Take screenshot
mcp-cli call tabz/tabz_screenshot '{}'
# Returns file path - use Read tool to view
# 1. Enable capture BEFORE triggering action
mcp-cli call tabz/tabz_enable_network_capture '{}'
# 2. Trigger the action on page
# 3. Get failed requests (status >= 400)
mcp-cli call tabz/tabz_get_network_requests '{"statusMin": 400}'
# 4. Check console for JS errors
mcp-cli call tabz/tabz_get_console_logs '{"level": "error"}'
# Emulate device
mcp-cli call tabz/tabz_emulate_device '{"device": "iPhone 14"}'
# Take screenshot
mcp-cli call tabz/tabz_screenshot '{}'
# Clear emulation
mcp-cli call tabz/tabz_emulate_clear '{}'
mcp-cli call tabz/tabz_fill '{"selector": "#email", "value": "[email protected]"}'
mcp-cli call tabz/tabz_click '{"selector": "button[type=submit]"}'
mcp-cli call tabz/tabz_speak '{"text": "Task complete"}'
mcp-cli call tabz/tabz_profile_performance '{}'
# Returns: DOM nodes, JS heap, event listeners, timing
mcp-cli call tabz/tabz_get_dom_tree '{"maxDepth": 3}'
| Category | Count | Key Tools |
|---|---|---|
| Screenshots | 2 | screenshot, screenshot_full |
| Interaction | 4 | click, fill, get_element |
| Network | 3 | enable_network_capture, get_network_requests |
| DOM/Debug | 4 | get_dom_tree, get_console_logs, profile_performance |
| Emulation | 6 | emulate_device, emulate_geolocation |
| Audio/TTS | 3 | speak, list_voices, play_audio |
| Tabs | 5 | list_tabs, open_url, switch_tab |
| Cookies | 5 | cookies_get, cookies_list |
mcp-cli info tabz/<tool> before callingtabId when possible - don't rely on "active" tab1762561083)tabz_screenshot cannot capture Chrome sidebarSee references/ for detailed workflows and full tool documentation:
screenshot-workflows.md - Viewport vs full page screenshotsnetwork-debugging.md - API request inspectionform-automation.md - Clicks, fills, selectorstts-notifications.md - Audio feedback patternscore-tools.md - Tabs, screenshots, clicks, fills, DOM inspectionwindows-groups.md - Windows, tab groups, multi-window workflowsnetwork-downloads.md - Network capture, downloads, file operationsbrowser-data.md - History, sessions, cookies, bookmarksprofiles-and-plugins.md - Terminal profiles, Claude Code plugin managementadvanced-tools.md - Emulation, performance profiling, notificationsnpx claudepluginhub ggprompts/tabzchrome --plugin tabzLaunches and configures Chrome DevTools MCP server for visual access to live browser, enabling screenshots, DOM snapshots, console debugging, network inspection, Core Web Vitals measurement, Lighthouse audits, and automation of interactions on Windows/Linux/WSL2.
Controls Chrome via DevTools Protocol for navigating, clicking, typing, multi-tab management, and content extraction with auto-screenshots.
Uses Chrome DevTools MCP for debugging, browser automation, performance analysis, and network inspection. Includes workflows for page interaction, extension testing, and efficient data retrieval.