skills.rest
nicobailon
nicobailonCOMMUNITY
Explore all skills by this author →
Website𝕏@nicopremeGitHub

chrome-devtools-testing

Automate browser testing by connecting Playwright to Chrome via CDP.

4|1|Updated Dec 11, 2025
Search Tags:#automation#qa#devtools#playwright#cdp#chrome
One-click install
npx skills add https://github.com/nicobailon/chrome-devtools-testing --skill chrome-devtools-testing-nicobailon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: chrome-devtools-testing
Source: https://github.com/nicobailon/chrome-devtools-testing/tree/main
Command: npx skills add https://github.com/nicobailon/chrome-devtools-testing --skill chrome-devtools-testing-nicobailon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Chrome DevTools Testing automates browser testing and debugging by connecting Playwright to Chrome via CDP, enabling batch scripting and observable DevTools output.

Core Features & Use Cases

  • Batch scripting for multi-action flows
  • ARIA snapshots for accessibility-aware element targeting
  • DevTools debugging: console capture, network monitoring, and performance tracing
  • Persistent pages across script runs for multi-step workflows
  • Playwright locators for robust element selection

Quick Start

Start the server with bun run start-server, then connect a client and run a multi-action script to validate a typical page flow.

Frequently Asked Questions about chrome-devtools-testing

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

FAQPage Schema
How do I automate Chrome DevTools testing with Playwright?▼

Yes, you can capture console output and monitor network traffic by connecting Playwright to Chrome via CDP. This setup enables DevTools debugging features like console capture, network monitoring, and performance tracing directly through the provided client API.

How do I run multi-action batch scripts against a live Chromium session?▼

Yes, Playwright locators and ARIA snapshots enable accessibility-aware element targeting for Chrome DevTools testing. This ensures robust element selection during script-driven actions and multi-step workflows across persistent pages.

Can I maintain persistent pages across multiple script runs for multi-step workflows?▼

Use Chrome DevTools Protocol automation for QA testing, debugging, and performance verification across single-page applications. It applies to script-driven actions, batch execution, and server-based page persistence by connecting Playwright to a live Chromium session.

What are the limitations of using CDP-based debugging for end-to-end browser testing?▼

Limitations include managing robust error handling and safety checks required for CDP-based debugging during end-to-end browser testing. While it supports multi-step interactions and performance tracing, complex single-page apps may require careful script-driven action configuration.

Related Skills

Explore More Software Engineering Skills→
stellarlinkcostellarlinkco
2.7k

browser

Automate Chrome browser interactions via the Chrome DevTools Protocol.

Official
Intermediate
AskTinNguyenAskTinNguyen

browser-testing-with-devtools

Inspect live pages, DOM, console logs, and network activity via Chrome DevTools MCP.

Community
Advanced
ksciuskscius
2

accessibility-auditing

Audit web page accessibility by analyzing Cursor's ARIA tree snapshots.

Community
Advanced
mafvietnammafvietnam

ck:chrome-devtools

Automate browser workflows with Puppeteer and CDP using persistent sessions.

Community
Advanced