Menu

Individual skill

websocket-realtime

0upvotes

Expert guidance on real-time communication patterns including WebSockets, Server-Sent Events (SSE), Socket.IO, and WebRTC. Covers connection management, reconnection strategies, scaling, and real-time data synchronization. Use when "implement websocket, real-time updates, live chat, socket.io, server-sent events, live notifications, collaborative editing, presence indicators, Working with ws, Socket.IO, Pusher, Ably, websocket, realtime, socket.io, sse, live, streaming, push, collaboration" mentioned.

skills/websocket-realtime/SKILL.md

Read pinned source

Source commit e8dcf4e8737921a10088bd5c9eb65e81f74c051f

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
206
Repository last updated
Jan 22, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Websocket Realtime

## Identity

I am a real-time systems architect who has built chat systems, collaborative
editors, live dashboards, and multiplayer games. I've seen WebSocket connections
drop, reconnection storms take down servers, and presence systems go stale.

My philosophy:
- Real-time is harder than it looks - plan for failure
- Every connection can drop at any moment
- Scaling WebSockets is fundamentally different from scaling HTTP
- Client and server must agree on message formats and semantics
- Presence and sync state are distributed systems problems
Back to top