chrome-devtools-cli-usage

Automate Chrome browser tasks using Chrome DevTools CLI commands.

1|Updated Nov 2, 2025
One-click install
npx skills add https://github.com/pleaseai/chrome-devtools-cli --skill chrome-devtools-cli-usage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chrome-devtools-cli-usage
Source: https://github.com/pleaseai/chrome-devtools-cli/tree/main/skills/chrome-devtools-cli-usage
Command: npx skills add https://github.com/pleaseai/chrome-devtools-cli --skill chrome-devtools-cli-usage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive usage guide for the Chrome DevTools CLI, helping developers automate browser tasks, debug efficiently, and analyze performance with a CLI-driven workflow.

Core Features & Use Cases

  • Usage Guidance: Step-by-step instructions for launching, navigating, capturing screenshots, and analyzing performance with the Chrome DevTools CLI.
  • Workflow Examples: Ready-to-run examples for navigation, debugging, network monitoring, and device emulation to speed up automation tasks.
  • Use Case: A developer can quickly script end-to-end browser tests in CI, generate performance reports, and monitor network activity with TOON-friendly outputs.

Quick Start

Install the CLI using Homebrew, npm/Bun, or direct binaries, then begin with common commands such as nav new-page, debug screenshot, perf analyze, and network start-monitoring to automate repetitive browser tasks.

Frequently Asked Questions about chrome-devtools-cli-usage

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

FAQPage Schema
How do I automate Chrome browser tasks from the command line?

Chrome DevTools CLI enables command-line automation of browser tasks including navigation, screenshot capture, performance analysis, and network monitoring. Install via Homebrew, npm, or Bun, then use commands like `nav new-page`, `debug screenshot`, and `perf analyze` to script repetitive browser workflows in CI/CD pipelines and local development.

Can I use Chrome DevTools CLI for end-to-end browser testing in CI pipelines?

Yes. Chrome DevTools CLI supports headless, isolated, and containerized deployments ideal for CI/CD environments. Script navigation, device emulation, performance tracing, and network inspection to generate automated test results and performance reports without manual browser interaction.

What debugging and performance analysis features does Chrome DevTools CLI provide?

Chrome DevTools CLI offers performance tracing, network monitoring, device emulation, and debugging capabilities with JSON and TOON-friendly output formats. Analyze page load metrics, inspect network activity, and emulate devices directly from the command line to identify bottlenecks and issues.

How do I capture screenshots and monitor network activity with Chrome DevTools CLI?

Use `debug screenshot` to capture page states and `network start-monitoring` to inspect HTTP requests and responses. Both commands support headless execution and structured output formats, enabling programmatic integration with automation scripts and reporting tools.

Does Chrome DevTools CLI work with Puppeteer for browser automation?

Chrome DevTools CLI is a standalone CLI tool for browser automation and debugging. While both automate Chrome tasks, Chrome DevTools CLI provides a command-driven interface for performance analysis, network inspection, and device emulation without requiring Node.js API dependencies.

What environments does Chrome DevTools CLI support?

Chrome DevTools CLI runs in local development, test environments, and containerized deployments. It supports headless, isolated, proxy, and secure configurations, making it suitable for local scripting, CI/CD pipelines, and Docker-based automation workflows.