ck:chrome-devtools

Automates browser tasks via Puppeteer CLI scripts with persistent sessions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Browsers require repetitive tasks like taking screenshots, collecting performance data, monitoring network activity, scraping data, and debugging JS across sessions; manually repeating these steps is time consuming and error-prone.

Core Features & Use Cases

  • Persistent Puppeteer-based CLI automation: run scripts with session reuse for repeated tasks across pages.
  • Data collection and testing: capture screenshots, performance metrics, and network activity; scrape content reliably.
  • Form automation and debugging: automate form filling, evaluation, and quick JS troubleshooting in real browser contexts.

Quick Start

Install dependencies with npm and run the navigate script to start a session and verify the JSON output.

Frequently Asked Questions about ck:chrome-devtools

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

FAQPage Schema
Can I capture network activity and performance metrics during web scraping?

Yes, you can capture network activity and performance metrics during web scraping. The Skill automates Chrome to monitor network requests and collect performance data alongside content scraping, providing a comprehensive view of page behavior within a single session.

What's the best way to automate form filling and JavaScript debugging in a real browser?

The best way to automate form filling and JavaScript debugging is by controlling Chrome via Puppeteer CLI scripts. This approach executes form automation and JS troubleshooting directly in a real browser context, providing accurate evaluation and quick debugging results.

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

Yes, you need Node.js 18+ to run Puppeteer CLI scripts for browser automation. The environment requires Node.js, Puppeteer, and optional tooling like sharp and yargs to execute scripts and manage persistent session states effectively.

Does Puppeteer CLI support capturing screenshots across multiple pages and sessions?

Yes, Puppeteer CLI supports capturing screenshots across multiple pages and sessions. It automates Chrome to take screenshots reliably while storing session state for reuse, making repetitive screenshot tasks efficient and error-free.

Why use persistent sessions for browser automation instead of starting fresh each time?

Using persistent sessions for browser automation prevents time-consuming and error-prone manual repetitions. By storing and reusing session state, Puppeteer CLI scripts maintain context across pages, streamlining web scraping, testing, and debugging workflows.