websocket-monitor

Monitor WebSocket activity on Chromium pages via CDP instrumentation.

1|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/anouar1991/binaryPetsClaude --skill websocket-monitor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: websocket-monitor
Source: https://github.com/anouar1991/binaryPetsClaude/tree/main/plugins/playwright-toolkit/skills/websocket-monitor
Command: npx skills add https://github.com/anouar1991/binaryPetsClaude --skill websocket-monitor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Instrument pages to observe and diagnose WebSocket activity by leveraging Chrome DevTools Protocol events, providing visibility into connection lifecycles, message payloads, and protocol usage (Socket.IO/engine.io).

Core Features & Use Cases

  • Instrument WebSocket events via CDP to capture connections, frames, timing, and byte counts with live dashboards.
  • Patch the WebSocket constructor to detect higher-level protocols and report Socket.IO and engine.io usage for debugging and optimization.
  • Collect and analyze metrics such as latency, message size, direction, and history to troubleshoot reconnections and throughput in web apps.

Quick Start

Install CDP WebSocket listeners, patch protocol detection, navigate to your target page, and harvest the captured data for analysis.

Frequently Asked Questions about websocket-monitor

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

FAQPage Schema
How do I monitor WebSocket connections and messages using Chrome DevTools Protocol?

Monitor WebSocket activity by installing CDP-powered event listeners on Chromium-based pages to capture connection lifecycles, message payloads, frame timing, and byte counts for real-time inspection.

Can I detect Socket.IO and engine.io usage when debugging a web app?

Detect Socket.IO and engine.io protocol usage by patching the WebSocket constructor, which identifies and reports higher-level protocol activity to help debug real-time web applications.

What metrics can I collect for troubleshooting WebSocket latency and reconnections?

Collect WebSocket metrics such as latency, message size, direction, timing data, and history to troubleshoot reconnections and analyze throughput issues in web applications.

Does this WebSocket inspection approach work with Playwright?

Yes, this WebSocket inspection works with Playwright by leveraging CDP-powered instrumentation on Chromium-based pages to observe connection lifecycles and message frames.

What is the best way to analyze WebSocket message frequency and payloads in production?

Analyze message frequency and payloads by instrumenting WebSocket events via CDP, capturing frames and byte counts with live dashboards to diagnose real-time app behavior in production environments.

When do I need to patch the WebSocket constructor for protocol detection?

Patch the WebSocket constructor when you need to detect higher-level protocols like Socket.IO or engine.io, reporting protocol identity for debugging and optimization across test and production pages.