chrome-devtools
by podcasting101
Web & Frontend DevelopmentBrief
Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation.
Description
What This Skill Does
Controls Chrome via the Chrome DevTools Protocol through an MCP server. Supports navigating pages, interacting with DOM elements, running JavaScript, capturing screenshots, and analyzing network requests. The browser starts automatically and maintains a persistent profile across tool calls.
Gives agents direct access to a live browser without requiring a separate Playwright or Selenium setup.
When to Use It
- Debug a broken form that fails silently in production
- Scrape data from a JavaScript-rendered page
- Trace slow network requests to find a bottleneck
- Automate a multi-step login flow for testing
- Inspect DOM structure to fix a layout regression
Example Workflow
User asks: Why is the checkout button not responding on my e-commerce page?
- 1
Call navigate_page to open the checkout page
- 2
Call wait_for to confirm the page is fully loaded
- 3
Call take_snapshot to map the page structure and locate the button uid
- 4
Call evaluate_script to check for JavaScript errors or missing event listeners on the button
- 5
Report the console errors and handler state back to the user
Identifies that a missing script dependency is preventing the click handler from attaching
Requirements
- Google Chrome browser installed
Installation
clawhub install podcasting101/chrome-devtoolsRun the CLI command, or paste the prompt into Claude Code, Cursor, Codex or whichever coding agent you use.