chrome-devtools-deep

Access advanced Chrome DevTools Protocol features via Playwright's newCDPSession method.

Updated May 28, 2026
One-click install
npx skills add https://github.com/syntropic137/harness-app-template --skill chrome-devtools-deep
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chrome-devtools-deep
Source: https://github.com/syntropic137/harness-app-template/tree/main/.claude/skills/chrome-devtools-deep
Command: npx skills add https://github.com/syntropic137/harness-app-template --skill chrome-devtools-deep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Playwright's high-level API does not expose advanced Chrome DevTools Protocol features like performance tracing, heap snapshots, source-mapped stack traces, and deep network response inspection, leaving developers without a straightforward way to access these critical debugging capabilities within their existing Playwright workflows.

Core Features & Use Cases

  • Native CDP Access via Playwright: Use Playwright's built-in newCDPSession method to send Chrome DevTools Protocol commands directly, avoiding the overhead and fragility of external raw websocket tools like websocat.
  • Advanced Diagnostic Recipes: Pre-built code snippets for common high-value tasks including performance trace capture, source-mapped exception logging, network response body filtering, and heap snapshot generation for memory leak diagnosis.
  • Real-World Use Case: When debugging an intermittent performance regression in a single-page application, use this skill to capture a full Chrome trace of a critical user flow to identify rendering bottlenecks that standard Playwright metrics cannot surface.

Quick Start

Use the chrome-devtools-deep skill to capture a performance trace of a user checkout flow on your test e-commerce page to identify rendering bottlenecks.

Frequently Asked Questions about chrome-devtools-deep

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

FAQPage Schema
How do I capture a performance trace in Playwright to find rendering bottlenecks?

Diagnose memory leaks in Playwright by using the native newCDPSession method to send Chrome DevTools Protocol commands for heap snapshot generation. This skill provides pre-built recipes to capture heap snapshots for memory leak diagnosis within test environments.

Can I use Chrome DevTools Protocol features not exposed by Playwright's high-level API?

Yes, you can access advanced Chrome DevTools Protocol features not exposed by Playwright's high-level API by using the built-in newCDPSession method. This allows direct CDP interaction for performance profiling and deep network response inspection.

What is the best way to get source-mapped stack traces in Playwright tests?

The best way to get source-mapped stack traces in Playwright is by using this skill's pre-built diagnostic recipes to interact with CDP directly. It enables source-mapped exception logging without relying on external raw websocket tools.

Do I need external websocket tools like websocat for deep network debugging in Playwright?

No, you do not need external raw websocket tools like websocat for deep network debugging. This skill enables direct CDP access through Playwright's native newCDPSession method for network response body filtering and inspection.

How does CDP access work within existing Playwright workflows?

CDP access works within existing Playwright workflows by leveraging the native newCDPSession method to send Chrome DevTools Protocol commands directly. This integrates advanced diagnostic capabilities like performance profiling into your test environments.