ck:chrome-devtools

Name: ck:chrome-devtools
Availability: InStock
Author: mafvietnam

Automate browser workflows with Puppeteer and CDP using persistent sessions.

Updated Mar 30, 2026

Search Tags:#automation #qa #cdp #puppeteer #browser #session-persistence

Ready to run

npx skills add https://github.com/mafvietnam/mafapp --skill ck-chrome-devtools-mafvietnam

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Automates browser automation workflows using Puppeteer and Chrome DevTools Protocol with persistent sessions to streamline repetitive testing, data collection, and QA tasks.

Core Features & Use Cases

Browser automation through a suite of CLI scripts (navigate, click, fill, screenshot, network, performance)
Session persistence across runs via WebSocket endpoint files and saved auth/storage state
Flexible interaction using ARIA snapshots and selector utilities to stabilize automation across dynamic pages
Real-world use: test login flows, collect performance metrics, and capture reproducible browser sessions

Quick Start

Launch Chrome with remote debugging and run a sample workflow to navigate to a URL.

Frequently Asked Questions about ck:chrome-devtools

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

FAQPage Schema

How do I persist browser sessions across multiple Puppeteer automation runs?▼

You persist browser sessions by utilizing WebSocket endpoint files and saved authentication or storage state, enabling reproducible automation pipelines across multiple runs without repeated logins.

What is the best way to automate QA testing with Chrome DevTools Protocol and Puppeteer?▼

Automating QA testing with Puppeteer and CDP is best achieved through CLI scripts for navigation and clicking, stabilized by ARIA snapshots and selector utilities for dynamic page interactions.

Can I capture network and performance metrics using Puppeteer browser automation?▼

Yes, you can capture network and performance metrics during browser automation by executing the dedicated CLI scripts provided, collecting real-world performance data for QA tasks.

Does this Puppeteer automation skill require a specific browser setup to maintain sessions?▼

Yes, maintaining persistent sessions requires launching Chrome with remote debugging enabled, establishing the WebSocket endpoint connection needed for Puppeteer to save and reuse session state.

How do I stabilize browser automation scripts on dynamic web pages?▼

You stabilize browser automation scripts on dynamic pages by using ARIA snapshots and selector utilities, ensuring reliable interactions when page elements shift dynamically during navigation.