chrome-devtools

Automate browser tasks and UI testing via Puppeteer CLI scripts.

Updated Feb 8, 2026

Search Tags:#puppeteer #web-scraping #pdf-generation #browser-automation #headless-chrome #qa-debugging

Ready to run

npx skills add https://github.com/brixtonpham/claude-setup --skill chrome-devtools-brixtonpham

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: chrome-devtools
Source: https://github.com/brixtonpham/claude-setup/tree/main/hub/skills/chrome-devtools
Command: npx skills add https://github.com/brixtonpham/claude-setup --skill chrome-devtools-brixtonpham

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a ready-to-run set of Puppeteer CLI scripts that automate common browser tasks (screenshots, PDFs, scraping, form filling, and monitoring) to replace manual, repetitive steps.

Core Features & Use Cases

Screenshots & PDFs: Capture full-page screenshots and generate PDFs for documentation or QA.
Web Scraping & Form Automation: Extract data from pages and automate form submissions across websites.
Monitoring & Debugging: Collect network activity, console logs, and performance metrics to speed up debugging during development.

Quick Start

Run a quick test: take a full-page screenshot of https://example.com and save to /tmp/page.png using the chrome-devtools skill.

Frequently Asked Questions about chrome-devtools

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

FAQPage Schema

How do I automate full-page screenshots and PDF generation with Puppeteer?▼

Puppeteer automation drives headless Chrome to capture full-page screenshots and generate PDFs via CLI scripts. This skill provides ready-to-run scripts to replace manual browser steps for documentation or QA workflows.

Can I use Puppeteer CLI scripts for web scraping and form automation?▼

Yes, Puppeteer CLI scripts can extract data from pages and automate form submissions across websites. This skill targets repetitive data-gathering workflows by driving headless Chrome to interact with web elements programmatically.

Do I need Node.js 18+ to run Puppeteer browser automation scripts?▼

Yes, Node.js 18+ is required along with the puppeteer, debug, and yargs dependencies installed. The skill's scripts and references directories provide the automation logic and documentation needed to execute browser tasks.

How does headless Chrome collect network activity and console logs for QA debugging?▼

Headless Chrome automation collects network activity, console logs, and performance metrics during page interactions to speed up debugging. Puppeteer CLI scripts monitor these outputs to identify issues during development workflows.

What's the best way to automate repetitive browser testing tasks across web pages?▼

Automating repetitive browser testing tasks is best handled through Puppeteer CLI scripts that drive headless Chrome. This skill provides ready-to-run scripts for screenshots, form filling, and monitoring to replace manual QA steps.

Why does my Puppeteer script fail to capture network activity during monitoring?▼

Puppeteer network monitoring requires proper headless Chrome setup with Node.js 18+ and dependencies installed. The skill's scripts directory contains automation logic that correctly initializes network event listeners before page navigation begins.