Agent skill · software engineering · samhvw8

chrome-devtools

Browser automation via Puppeteer CLI scripts (JSON output). Capabilities: screenshots, PDF generation, web scraping, form automation, network monitoring, performance profiling, JavaScript debugging, headless browsing. Actions: screenshot, scrape, automate, test, profile, monitor, debug browser. Keywords: Puppeteer, headless Chrome, screenshot, PDF, web scraping, form fill, click, navigate, network traffic, performance audit, Lighthouse, console logs, DOM manipulation, element selector, wait, scroll, automation script. Use when: taking screenshots, generating PDFs from web, scraping websites, automating form submissions, monitoring network requests, profiling page performance, debugging JavaScript, testing web UIs.

Why this skill is useful

Adds multiple executable Puppeteer scripts for browser automation that provide capabilities not available in standard libraries.

What it needs

Requires node installed locally. About 3k tokens when loaded. Last updated 2025-12-09. 10 stars on the source repository.

What this skill does

Chrome DevTools Agent Skill Browser automation via executable Puppeteer scripts. All scripts output JSON for easy parsing. Quick Start Installation Step 1: Install System Dependencies (Linux/WSL only) On Linux/WSL, Chrome requires system libraries. Install them first: Supports: Ubuntu, Debian, Fedora, RHEL, CentOS, Arch, Manjaro macOS/Windows: Skip this step (dependencies bundled with Chrome) Step 2: Install Node Dependencies Test Available Scripts All scripts are in .claude/skills/chrome-devtools/scripts/ Script Usage ./scripts/README.md Core Automation navigate.js - Navigate to URLs screenshot.js - Capture screenshots (full page or element) click.js - Click elements fill.js - Fill form fields evaluate.js - Execute JavaScript in page context Analysis & Monitoring snapshot.js - Extract interactive elements with metadata console.js - Monitor console messages/errors network.js - Track HTTP requests/responses performance.js - Measure Core Web Vitals + record traces Usage Patterns Single Command Important: Always save screenshots to ./docs/screenshots directory. Chain Commands (reuse browser) Parse JSON Output Common Workflows Web Scraping Performance Testing Form Automation Error Monitoring Script Options All scripts support: --headless false - Show browser window --close false - Keep browser open for chaining --timeout 30000 - Set timeout (milliseconds) --wait-until networkidle2 - Wait strategy See ./scripts/README.md for complete options. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills samhvw8/chrome-devtools

View the source on GitHub

Browse the @skills marketplace