How do I install the Webrtc Timing Test skill?

Run npx skillmds@latest add diegosouzapw/webrtc-timing-test in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Webrtc Timing Test safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Webrtc Timing Test?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Webrtc Timing Test free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Webrtc Timing Test?

diegosouzapw (@diegosouzapw) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Webrtc Timing Test by diegosouzapw — Agent Skill

Name: Webrtc Timing Test
Rating: 4.2 (5 reviews)
Author: diegosouzapw

Webrtc Timing Test

Measure WebRTC connection timing on Daily rooms. Use when testing Daily video call connection performance, measuring ICE negotiation time, benchmarking WebRTC setup latency, or when asked to test how long a Daily room takes to connect.

diegosouzapw Updated Sep 8, 2026 54 repo stars

File contents

WebRTC Connection Timing Test

Measure how long WebRTC connections take to establish on Daily video rooms.

Prerequisites

Chrome browser with Claude in Chrome extension
Chrome window size: 705 x 942 pixels

Procedure

Step 1: Set up browser window

Resize Chrome window to 705 x 942 pixels using mcp__claude-in-chrome__resize_window.

Step 2: Navigate to Daily room

Navigate to the Daily room URL (e.g., kwindla.daily.co/gradient-ascent). Wait for pre-join screen ("Get ready for your call") to load.

Step 3: Inject interceptor

Execute scripts/inject-interceptor.js using mcp__claude-in-chrome__javascript_tool. This must be done BEFORE clicking Join.

Step 4: Click Join

Execute scripts/click-join.js to click the Join button and record the exact time.

Step 5: Retrieve results

Wait ~5 seconds for connection, then execute scripts/retrieve-results.js to get timing data.

Key Metrics

Metric	Description
totalConnectionTime	Join click to `connectionState: connected` (user-perceived latency)
callSetupTime	Join click to RTCPeerConnection creation (Daily initialization)
pureWebRTCTime	RTCPeerConnection creation to connected (actual WebRTC negotiation)
iceConnectionTime	Join click to `iceConnectionState: connected`

Expected Results

Metric	Typical Time
callSetupTime	~350-500ms
pureWebRTCTime	~150-360ms
totalConnectionTime	~500-900ms

Notes

Daily creates 3 RTCPeerConnections (audio, video, data)
The interceptor must be installed BEFORE clicking Join
Network conditions affect ICE negotiation time
Daily's iframe may cause timing variability between runs

---name: webrtc-timing-testdescription: Measure WebRTC connection timing on Daily rooms. Use when testing Daily video call connection performance, measuring ICE negotiation time, benchmarking WebRTC setup latency, or when asked to test how long a Daily room takes to connect.---# WebRTC Connection Timing TestMeasure how long WebRTC connections take to establish on Daily video rooms.## Prerequisites- Chrome browser with Claude in Chrome extension- Chrome window size: **705 x 942** pixels## Procedure### Step 1: Set up browser windowResize Chrome window to 705 x 942 pixels using `mcp__claude-in-chrome__resize_window`.### Step 2: Navigate to Daily roomNavigate to the Daily room URL (e.g., `kwindla.daily.co/gradient-ascent`). Wait for pre-join screen ("Get ready for your call") to load.### Step 3: Inject interceptorExecute `scripts/inject-interceptor.js` using `mcp__claude-in-chrome__javascript_tool`. This must be done BEFORE clicking Join.### Step 4: Click JoinExecute `scripts/click-join.js` to click the Join button and record the exact time.### Step 5: Retrieve resultsWait ~5 seconds for connection, then execute `scripts/retrieve-results.js` to get timing data.## Key Metrics| Metric | Description ||--------|-------------|| **totalConnectionTime** | Join click to `connectionState: connected` (user-perceived latency) || **callSetupTime** | Join click to RTCPeerConnection creation (Daily initialization) || **pureWebRTCTime** | RTCPeerConnection creation to connected (actual WebRTC negotiation) || **iceConnectionTime** | Join click to `iceConnectionState: connected` |## Expected Results| Metric | Typical Time ||--------|--------------|| callSetupTime | ~350-500ms || pureWebRTCTime | ~150-360ms || totalConnectionTime | ~500-900ms |## Notes- Daily creates 3 RTCPeerConnections (audio, video, data)- The interceptor must be installed BEFORE clicking Join- Network conditions affect ICE negotiation time- Daily's iframe may cause timing variability between runs

Frequently asked questions