webrtc — Claude Code skill: what it does, how to install
WebRTC skill for P2P communication: video calls, screen sharing, data channels. Writes signaling logic, configures ICE/STUN/TURN, integrates SFU like LiveKit.
MIT 217 installs ★ 50 updated 2026-10-23
npx skills add claude-dev-suite/claude-dev-suite --skill webrtc -a claude-codeWhat webrtc does
The skill provides WebRTC templates and patterns: RTCPeerConnection with STUN and TURN servers, Socket.IO signaling, SDP and ICE candidate exchange. It creates data channels for text and binary data, sets up screen sharing via getDisplayMedia, and wires up SFU (LiveKit, mediasoup) for group calls.
In TypeScript it shows media stream handling, track replacement when switching between camera and screen, and subscription to remote tracks. Includes TURN fallback for NAT traversal and bandwidth adaptation for stable connections.
Without a TURN server, clients behind NAT won't connect. For group calls with more than three participants, P2P doesn't scale — the skill defaults to SFU from the first request. Handles camera access denial, monitors connectionstatechange to catch disconnections.
What it helps with
- set up peer-to-peer video call with SDP and ICE exchange
- add screen sharing with track switching
- create a data channel for text chat over WebRTC
- integrate LiveKit for a group call
- configure TURN for NAT traversal
Example prompts for the agent
- Build a P2P video call with Socket.IO signaling and Google STUN server
- Add a screen share button that switches the video track
- Create an ordered
chatdata channel and attach a message handler
How to install webrtc
1Skills CLI (Vercel)
npx skills add claude-dev-suite/claude-dev-suite --skill webrtc -a claude-code2Manually: put the files in place
~/.claude/skills/webrtc/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/webrtc/
1Skills CLI (Vercel)
npx skills add claude-dev-suite/claude-dev-suite --skill webrtc -a codex2Manually: put the files in place
.agents/skills/webrtc/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add claude-dev-suite/claude-dev-suite --skill webrtc -a cursor2Manually: put the files in place
.cursor/skills/webrtc/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install claude-dev-suite/claude-dev-suite skills/real-time/webrtc2Manually: put the files in place
.github/skills/webrtc/SKILL.md1Skills CLI (Vercel)
npx skills add claude-dev-suite/claude-dev-suite --skill webrtc -a gemini-cli2Platform CLI
gemini skills install https://github.com/claude-dev-suite/claude-dev-suite --path skills/real-time/webrtcManually: put the files in place
.devin/skills/webrtc/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add claude-dev-suite/claude-dev-suite --skill webrtc -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about webrtc
How to install webrtc in Claude Code?
Run npx skills add claude-dev-suite/claude-dev-suite --skill webrtc -a claude-code. The skill lands in ~/.claude/skills/webrtc/SKILL.md.
What does the webrtc skill do?
Writes WebRTC code: peer connection setup, signaling, data channels, screen sharing, and SFU integration. Shows ICE candidate and media stream handling.
Why do I need a TURN server in webrtc?
TURN relays connections through NAT when direct P2P fails. Without it, clients behind firewalls can't connect. The skill configures TURN in iceServers.
Source text
SKILL.md · MIT
---
name: webrtc
description: |
WebRTC peer-to-peer communication. Signaling, ICE/STUN/TURN, media streams,
data channels, screen sharing, and SFU integration (mediasoup, LiveKit).
USE WHEN: user mentions "WebRTC", "video call", "peer-to-peer", "P2P",
"screen sharing", "data channel", "STUN", "TURN", "mediasoup", "LiveKit"
DO NOT USE FOR: server-to-client streaming - use `sse`;
chat messaging - use `socket-io`
allowed-tools: Read, Grep, Glob, Write, Edit
---
# WebRTC
## Peer Connection Setup
```typescript
const config: RTCConfiguration = {
iceServers: [
{ urls: 'stun:stun.l.google.com:19302' },
{ urls: 'turn:turn.example.com', username: 'user', credential: 'pass' },
],
};
const pc = new RTCPeerConnection(config);
// Get local media
const stream = await navigator.mediaDevices.getUserMedia({ video: true, audio: true });
stream.getTracks().forEach((track) => pc.addTrack(track, stream));
// Display remote stream
pc.ontrack = (event) => {
remoteVideo.srcObject = event.streams[0];
};
// ICE candidates — send to remote peer via signaling
pc.onicecandidate = (event) => {
if (event.candidate) {
signalingChannel.send({ type: 'ice-candidate', candidate: event.candidate });
}
};
```
## Signaling (via Socket.IO)
```typescript
// Caller
const offer = await pc.createOffer();
await pc.setLocalDescription(offer);
socket.emit('signal', { type: 'offer', sdp: offer });
// Callee — on receiving offer
socket.on('signal', async (msg) => {
if (msg.type === 'offer') {
await pc.setRemoteDescription(msg.sdp);
const answer = await pc.createAnswer();
await pc.setLocalDescription(answer);
socket.emit('signal', { type: 'answer', sdp: answer });
} else if (msg.type === 'answer') {
await pc.setRemoteDescription(msg.sdp);
} else if (msg.type === 'ice-candidate') {
await pc.addIceCandidate(msg.candidate);
}
});
```
## Data Channels
```typescript
const dataChannel = pc.createDataChannel('chat', { ordered: true });
dataChannel.onopen = () => dataChannel.send('Hello!');
dataChannel.onmessage = (e) => console.log('Received:', e.data);
// Remote side
pc.ondatachannel = (event) => {
const channel = event.channel;
channel.onmessage = (e) => console.log('Received:', e.data);
};
```
## Screen Sharing
```typescript
const screenStream = await navigator.mediaDevices.getDisplayMedia({
video: { cursor: 'always' },
audio: true,
});
const videoTrack = screenStream.getVideoTracks()[0];
const sender = pc.getSenders().find((s) => s.track?.kind === 'video');
await sender?.replaceTrack(videoTrack);
videoTrack.onended = () => {
// User stopped sharing — switch back to camera
const cameraTrack = localStream.getVideoTracks()[0];
sender?.replaceTrack(cameraTrack);
};
```
## LiveKit (SFU — recommended for group calls)
```typescript
import { Room, RoomEvent } from 'livekit-client';
const room = new Room();
await room.connect(LIVEKIT_URL, accessToken);
await room.localParticipant.enableCameraAndMicrophone();
room.on(RoomEvent.TrackSubscribed, (track, publication, participant) => {
const element = track.attach();
document.getElementById('remote-videos')!.appendChild(element);
});
room.on(RoomEvent.ParticipantDisconnected, (participant) => {
console.log(`${participant.identity} left`);
});
```
## Anti-Patterns
| Anti-Pattern | Fix |
|--------------|-----|
| No TURN server | Always configure TURN for NAT traversal |
| P2P for group calls (>4 users) | Use SFU (LiveKit, mediasoup) |
| No error handling on getUserMedia | Handle NotAllowedError, NotFoundError |
| Signaling over unencrypted channel | Use WSS (WebSocket Secure) |
| No connection state monitoring | Listen to `connectionstatechange` event |
## Production Checklist
- [ ] TURN server deployed and configured
- [ ] SFU for group video (>3 participants)
- [ ] Fallback UI when media access denied
- [ ] Connection quality monitoring
- [ ] Bandwidth adaptation (simulcast)
- [ ] Recording capability if needed
© claude-dev-suite · MIT · claude-dev-suite/claude-dev-suite