chrome-devtools-cli

Automate Chrome browser interactions and runtime debugging via a persistent daemon.

18|1|Updated Apr 8, 2026

Search Tags:#automation #performance #debugging #devtools #chrome #browser

Ready to run

npx skills add https://github.com/appautomaton/webmaton --skill chrome-devtools-cli-appautomaton

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: chrome-devtools-cli
Source: https://github.com/appautomaton/webmaton/tree/main/skills/chrome-devtools-cli
Command: npx skills add https://github.com/appautomaton/webmaton --skill chrome-devtools-cli-appautomaton

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires chrome-devtools-mcp, and includes references (resource) components.

What problem does it solve?

This skill solves the challenge of interacting with complex, JavaScript-heavy web applications that require human-like browser behavior, such as logging in, filling forms, or debugging runtime performance issues.

Core Features & Use Cases

Browser Automation: Perform clicks, typing, and navigation in a persistent Chrome environment.
Runtime Inspection: Evaluate JavaScript, monitor console logs, and inspect network traffic in real-time.
Performance & Quality: Run Lighthouse audits and capture performance traces to diagnose layout or speed issues.
Use Case: Use this to automate a multi-step login flow on a secure dashboard, then capture a performance trace to identify why the page load is slow.

Quick Start

Use the chrome-devtools-cli to navigate to a specific URL and take an accessibility snapshot to identify interactive elements.

Frequently Asked Questions about chrome-devtools-cli

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

FAQPage Schema

How do I automate Chrome browser interactions for complex JavaScript web applications?▼

Automate Chrome browser interactions by using a persistent background daemon to perform clicks, typing, and navigation. This approach handles human-like behavior for complex JavaScript web applications, enabling automated form submission and secure multi-step login flows.

Can I inspect network traffic and monitor console logs in real-time during web debugging?▼

Inspect network traffic and monitor console logs in real-time through runtime inspection. Evaluate JavaScript directly in the persistent Chrome environment to debug complex web applications and identify runtime performance issues during automated interactions.

How do I run Lighthouse audits and capture performance traces to diagnose slow page loads?▼

Run Lighthouse audits and capture performance traces to diagnose slow page loads by automating Chrome runtime inspection. This process evaluates page rendering speed and identifies layout or performance issues within the persistent browser environment.

Do I need chrome-devtools-mcp installed locally to interface with the browser via Unix sockets?▼

Yes, you need the chrome-devtools-mcp package installed locally to interface with the browser. It enables communication via Unix sockets or named pipes, which is required for the background daemon to automate Chrome interactions and debugging.

What's the best way to identify interactive elements on a web page for accessibility tree analysis?▼

Identify interactive elements by navigating to a specific URL and taking an accessibility snapshot. This accessibility tree analysis captures the page structure within the Chrome environment to detect available interactive elements for automation.

Why does browser automation require a persistent background daemon for runtime debugging?▼

Browser automation requires a persistent background daemon to maintain a continuous Chrome environment state. This persistent connection supports runtime debugging, allowing sequential actions like form submission followed immediately by network traffic inspection without losing context.