chrome-devtools

Automate browser interactions and debugging with persistent Puppeteer CLI sessions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Automating browser interactions across sites is error-prone and time-consuming; this Skill provides a self-contained, persistent Puppeteer‑based toolkit to drive tests, captures, and analysis without reinitializing the browser for every task.

Core Features & Use Cases

  • Persistent session automation: navigate, click, fill, screenshot, and log network/console data across multiple scripts.
  • ARIA accessibility snapshots and performance analysis: generate YAML/JSON snapshots, collect metrics, and debug with console output.
  • Use Case: QA automation and accessibility testing across dashboards, forms, and data-intensive pages, with reusable scripts and centralized context.

Quick Start

Install dependencies and run a sample script to verify the environment.

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 testing with Puppeteer across multiple pages?

Automating browser testing with Puppeteer is handled through persistent session scripts that navigate, click, fill, and capture screenshots across multiple pages. This Skill provides a self-contained toolkit to drive tests and captures without reinitializing the browser for every task.

How do I capture ARIA accessibility snapshots during browser automation?

Capturing ARIA accessibility snapshots during browser automation is achieved by running the Skill's Puppeteer CLI scripts. These scripts generate YAML or JSON snapshots of the page state, enabling accessibility testing and debugging for data-intensive pages and dashboards.

What is the best way to collect network and console logs for performance analysis?

Collecting network and console logs for performance analysis is done using the Skill's Puppeteer-based automation scripts. The toolkit logs network and console data during persistent browsing sessions and outputs the collected metrics in a structured JSON format for debugging.

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

Yes, you need Node.js 18 or higher to run these Puppeteer automation scripts. The Skill requires this environment along with dependencies like Puppeteer and Sharp to load operational context and execute browser automation, debugging, and performance analysis tasks.

Can I use this Puppeteer toolkit for QA automation on data-intensive dashboards?

Yes, you can use this Puppeteer toolkit for QA automation on data-intensive dashboards. The Skill is specifically designed for QA automation and accessibility testing across dashboards and forms, providing reusable scripts and centralized context for persistent session workflows.

Why does browser automation fail when reinitializing sessions for every task?

Browser automation fails or becomes error-prone when reinitializing sessions for every task due to lost state and increased overhead. This Skill solves the problem by providing a persistent Puppeteer-based toolkit that maintains session state across multiple scripts for continuous testing.