chrome-devtools

Automate browser inspection, interaction, and performance testing via Puppeteer CLI scripts.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/LuizEduPP/skills --skill chrome-devtools-luizedupp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chrome-devtools
Source: https://github.com/LuizEduPP/skills/tree/main/chrome-devtools
Command: npx skills add https://github.com/LuizEduPP/skills --skill chrome-devtools-luizedupp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires puppeteer, debug, yargs, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill eliminates the friction of manually driving Chrome DevTools for browser automation, debugging, and performance analysis so you can script every interaction reproducibly.

Core Features & Use Cases

  • Command-driven CLI scripts: navigate, click, fill, evaluate, snapshot, console, network, screenshot, and performance tools emit structured JSON for easy parsing and chaining.
  • Robust automation patterns: built-in helpers enforce working directory checks, selector validation, persistent browsers, automatic compression, and guided recovery steps for resilient workflows.
  • Use Case: Capture a page screenshot, stream network logs, and measure Core Web Vitals before reporting regressions by running screenshot, network, and performance scripts in sequence.

Quick Start

Tell chrome-devtools to capture a screenshot of https://example.com and save it under docs/screenshots for rapid analysis.

Frequently Asked Questions about chrome-devtools

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

FAQPage Schema
How do I automate Chrome DevTools tasks like screenshots and network tracing with Puppeteer?

Automate Chrome DevTools tasks using deterministic Puppeteer CLI scripts that handle navigation, screenshots, and network tracing. Scripts emit structured JSON outputs, replacing manual browser debugging with reproducible workflows for QA and engineering teams.

Can I measure Core Web Vitals and monitor console logs during browser automation?

Yes, you can measure Core Web Vitals and monitor console logs during browser automation. Built-in performance and console scripts capture runtime metrics and page messages, emitting structured JSON to report regressions and analyze page behavior.

What do I need to run Puppeteer scripts for web scraping and browser automation?

You need Node 18+ and platform-specific Chrome dependencies to run Puppeteer scripts for web scraping and automation. Optionally, install ImageMagick to auto-compress large screenshots captured during navigation and form automation workflows.

What is the best way to script deterministic browser interactions for QA testing?

The best way to script deterministic browser interactions for QA testing is using robust automation patterns with built-in helpers. These enforce selector validation, persistent browsers, and guided recovery steps to ensure resilient workflows across modern web applications.

Why does my Puppeteer screenshot script enforce a strict scripts directory execution?

Puppeteer screenshot scripts enforce a strict scripts directory execution to ensure deterministic and reproducible browser automation workflows. Working directory checks maintain consistent outputs and guided recovery steps for complex debugging sessions.