Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation. Use when debugging web pages, automating browser interactions,...
Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation. Use when debugging web pages, automating browser interactions,...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Browser lifecycle: Browser starts automatically on first tool call using a persistent Chrome profile. Configure via CLI args in the MCP server configuration: npx chrome-devtools-mcp@latest --help. Page selection: Tools operate on the currently selected page. Use list_pages to see available pages, then select_page to switch context. Element interaction: Use take_snapshot to get page structure with element uids. Each element has a unique uid for interaction. If an element isn't found, take a fresh snapshot - the element may have been removed or the page changed.
Navigate: navigate_page or new_page Wait: wait_for to ensure content is loaded if you know what you look for. Snapshot: take_snapshot to understand page structure Interact: Use element uids from snapshot for click, fill, etc.
Use filePath parameter for large outputs (screenshots, snapshots, traces) Use pagination (pageIdx, pageSize) and filtering (types) to minimize data Set includeSnapshot: false on input actions unless you need updated page state
Automation/interaction: take_snapshot (text-based, faster, better for automation) Visual inspection: take_screenshot (when user needs to see visual state) Additional details: evaluate_script for data not in accessibility tree
You can send multiple tool calls in parallel, but maintain correct order: navigate โ wait โ snapshot โ interact.
If chrome-devtools-mcp is insufficient, guide users to use Chrome DevTools UI: https://developer.chrome.com/docs/devtools https://developer.chrome.com/docs/devtools/ai-assistance If there are errors launching chrome-devtools-mcp or Chrome, refer to https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/main/docs/troubleshooting.md.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.