chrome-devtools

Automate browser tasks and data collection with Puppeteer CLI scripts.

2|Updated Jan 9, 2026

Search Tags:#authentication #puppeteer #web-scraping #browser-automation #session-persistence #cookie-management

Ready to run

npx skills add https://github.com/NammDev/Goads-Krea --skill chrome-devtools-nammdev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: chrome-devtools
Source: https://github.com/NammDev/Goads-Krea/tree/main/.claude/skills/chrome-devtools
Command: npx skills add https://github.com/NammDev/Goads-Krea --skill chrome-devtools-nammdev

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Automates browser tasks and data collection using Puppeteer CLI scripts with persistent sessions.

Core Features & Use Cases

Persistent browser sessions enable session reuse across script executions.
Screenshots, performance analysis, network monitoring, web scraping, form automation, and JavaScript debugging for end-to-end automation.
Use Case: QA automation and data extraction workflows across multiple sites with consistent context.

Quick Start

Navigate to a URL with navigate.js to verify a JSON output containing the final URL and page title.

Frequently Asked Questions about chrome-devtools

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

FAQPage Schema

How do I automate browser tasks with persistent sessions in Puppeteer?▼

Persistent browser sessions enable session reuse across Puppeteer CLI script executions, allowing you to automate browser tasks like data collection and form automation while maintaining consistent authentication context across multiple runs.

What can I do with Puppeteer CLI scripts for web scraping and network monitoring?▼

Puppeteer CLI scripts support web scraping, network monitoring, performance analysis, screenshots, form automation, and JavaScript debugging across project-scope or user-scope usage for end-to-end browser automation and data extraction workflows.

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

Yes, browser automation with Puppeteer requires Node.js and Puppeteer. Optional dependencies include sharp for image processing and yargs for command-line options, with scripts and references stored under .claude/skills/chrome-devtools.

How do I verify a Puppeteer navigation script is working correctly?▼

Navigate to a URL using navigate.js to verify browser automation output. The script returns a JSON output containing the final URL and page title, confirming successful navigation and session initialization for your Puppeteer automation workflow.

Can I reuse authentication cookies across multiple Puppeteer script executions?▼

Cookie management and session persistence enable you to reuse authentication context across multiple Puppeteer script executions. Persistent browser sessions maintain login state, allowing QA automation and data extraction workflows to run with consistent context across sites.

What's the best way to automate screenshots and performance analysis across multiple sites?▼

Puppeteer CLI scripts with persistent sessions provide the best way to automate screenshots and performance analysis across multiple sites. The sharp dependency handles image processing, while persistent sessions ensure consistent context for end-to-end QA automation workflows.