chrome-devtools

Automate browser sessions and debugging with Chrome DevTools MCP integration.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/smorand/claude-config --skill chrome-devtools-smorand
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chrome-devtools
Source: https://github.com/smorand/claude-config/tree/main/skills/chrome-devtools
Command: npx skills add https://github.com/smorand/claude-config --skill chrome-devtools-smorand

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enables automated browser interactions, performance analysis, and debugging using Chrome DevTools MCP, enabling reliable automation and diagnostics.

Core Features & Use Cases

  • Browser automation: navigate pages, fill forms, handle dialogs
  • Performance analysis: record traces, CWV insights
  • Debugging: screenshots, network inspection, console monitoring
  • Network monitoring and multi-page management

Quick Start

Example: Open a page and capture a screenshot using the DevTools MCP server.

Frequently Asked Questions about chrome-devtools

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate browser interactions and debugging with Chrome DevTools?

Chrome DevTools automation enables you to programmatically navigate pages, fill forms, capture screenshots, and inspect network activity. Use the DevTools MCP integration to record performance traces, monitor console output, and handle dialogs across multi-page sessions with persistent data directories.

Can I use Chrome DevTools for performance testing and analysis?

Yes. Performance analysis through Chrome DevTools captures trace recordings, extracts Core Web Vitals insights, and profiles network behavior. This supports reliable diagnostics across browser automation workflows without manual intervention.

What's the best way to manage persistent browser state during automation?

Persistent data-dir management preserves browser state, cookies, and cache across automation sessions. Chrome DevTools MCP handles directory configuration, enabling reliable multi-page workflows and consistent debugging across repeated automation tasks.

How do I inspect network activity and debug console output during browser automation?

Network inspection and console monitoring through DevTools capture HTTP requests, responses, and real-time logs during automated sessions. This enables direct diagnostics without manual browser inspection.

Does Chrome DevTools automation work for web scraping scenarios?

Yes. Browser automation with element interaction, screenshot capture, and multi-page management supports web scraping workflows. Persistent data directories and DevTools integration enable reliable data extraction and validation across complex navigation paths.

What are the limitations when automating Chrome for debugging?

Chrome DevTools automation requires explicit data-dir configuration for state persistence; browser instances must remain active during trace recording and network analysis. Dialog handling and performance profiling are scoped to single Chrome sessions.