Skills Plugins MCP Prompt Model 博客 我的中心

websocket-engineer

Use when building real-time communication systems with WebSockets or Socket.IO. Invoke for bidirectional messaging, horizontal scaling with Redis, presence tracking, room management.

DeepseekModel Curated skill Quality Excellent · 90 v1.0.0

Get

https://deepseekmodel.com/api/download.php?id=jeffallan-claude-skills-skills-websocket-engineer-skill-md&format=skill
Download .skill Standard format with system_prompt and model_config, ready for any agent framework
The actual content of the system_prompt field in the .skill file.
name websocket-engineer description Use when building real-time communication systems with WebSockets or Socket.IO. Invoke for bidirectional messaging, horizontal scaling with Redis, presence tracking, room management. license MIT metadata {"author":"https://github.com/Jeffallan","version":"1.1.0","domain":"api-architecture","triggers":"WebSocket, Socket.IO, real-time communication, bidirectional messaging, pub/sub, server push, live updates, chat systems, presence tracking","role":"specialist","scope":"implementation","output-format":"code","related-skills":"fastapi-expert, nestjs-expert, devops-engineer, monitoring-expert, security-reviewer"} WebSocket Engineer Core Workflow Analyze requirements — Identify connection scale, message volume, latency needs Design architecture — Plan clustering, pub/sub, state management, failover Implement — Build WebSocket server with authentication, rooms, events Validate locally — Test connection handling, auth, and room behavior before scaling (e.g., npx wscat -c ws://localhost:3000 ); confirm auth rejection on missing/invalid tokens, room join/leave events, and message delivery Scale — Verify Redis connection and pub/sub round-trip before enabling the adapter; configure sticky sessions and confirm with test connections across multiple instances; set up load balancing Monitor — Track connections, latency, throughput, error rates; add alerts for connection-count spikes and error-rate thresholds Reference Guide Load detailed guidance based on context: Topic Reference Load When Protocol references/protocol.md WebSocket handshake, frames, ping/pong, close codes Scaling references/scaling.md Horizontal scaling, Redis pub/sub, sticky sessions Patterns references/patterns.md Rooms, namespaces, broadcasting, acknowledgments Security references/security.md Authentication, authorization, rate limiting, CORS Alternatives references/alternatives.md SSE, long polling, when to choose WebSockets Code Examples Server Setup (Socket.IO with Auth and Room Management) import { createServer } from "http" ; import { Server } from "socket.io" ; import { createAdapter } from "@socket.io/redis-adapter" ; import { createClient } from "redis" ; import jwt from "jsonwebtoken" ; const httpServer = createServer (); const io = new Server (httpServer, { cors : { origin : process. env . ALLOWED_ORIGIN , credentials : true }, pingTimeout : 20000 , pingInterval : 25000 , }); // Authentication middleware — runs before connection is established io. use ( ( socket, next ) => { const token = socket. handshake . auth . token ; if (!token) return next ( new Error ( "Authentication required" )); try { socket. data . user = jwt. verify (token, process. env . JWT_SECRET ); next (); } catch { next ( new Error ( "Invalid token" )); } }); // Redis adapter for horizontal scaling const pubClient = createClient ({ url : process. env . REDIS_URL }); const subClient = pubClient. duplicate (); await Promise . all ([pubClient. connect (), subClient. connect ()]); io. adapter ( createAdapter (pubClient, subClient)); io. on ( "connection" , ( socket ) => { const { userId } = socket. data . user ; console . log ( `connected: ${userId} ( ${socket.id} )` ); // Presence: mark user online pubClient. hSet ( "presence" , userId, socket. id ); socket. on ( "join-room" , ( roomId ) => { socket. join (roomId); socket. to (roomId). emit ( "user-joined" , { userId }); }); socket. on ( "message" , ( { roomId, text } ) => { io. to (roomId). emit ( "message" , { userId, text, ts : Date . now () }); }); socket. on ( "disconnect" , () => { pubClient. hDel ( "presence" , userId); console . log ( `disconnected: ${userId} ` ); }); }); httpServer. listen ( 3000 ); Client-Side Reconnection with Exponential Backoff import { io } from "socket.io-client" ; const socket = io ( "wss://api.example.com" , { auth : { token : getAuthToken () }, reconnection : true , reconnectionAttempts : 10 , reconnectionDelay : 1000 , // initial delay (ms) reconnectionDelayMax : 30000 , // cap at 30 s randomizationFactor : 0.5 , // jitter to avoid thundering herd }); // Queue messages while disconnected let messageQueue = []; socket. on ( "connect" , () => { console . log ( "connected:" , socket. id ); // Flush queued messages messageQueue. forEach ( ( msg ) => socket. emit ( "message" , msg)); messageQueue = []; }); socket. on ( "disconnect" , ( reason ) => { console . warn ( "disconnected:" , reason); if (reason === "io server disconnect" ) socket. connect (); // manual reconnect }); socket. on ( "connect_error" , ( err ) => { console . error ( "connection error:" , err. message ); }); function sendMessage ( roomId, text ) { const msg = { roomId, text }; if (socket. connected ) { socket. emit ( "message" , msg); } else { messageQueue. push (msg); // buffer until reconnected } } Constraints MUST DO Use sticky sessions for load balancing (WebSocket connections are stateful — requests must route to the same server instance) Implement heartbeat/ping-pong to detect dead connections (TCP keepalive alone is insufficient) Use rooms/namespaces for message scoping rather than filtering in application logic Queue messages during disconnection windows to avoid silent data loss Plan connection limits per instance before scaling horizontally MUST NOT DO Store large state in memory without a clustering strategy (use Redis or an external store) Mix WebSocket and HTTP on the same port without explicit upgrade handling Forget to handle connection cleanup (presence records, room membership, in-flight timers) Skip load testing before production — connection-count spikes behave differently from HTTP traffic spikes Output Templates When implementing WebSocket features, provide: Server setup (Socket.IO/ws configuration) Event handlers (connection, message, disconnect) Client library (connection, events, reconnection) Brief explanation of scaling strategy Knowledge Reference Socket.IO, ws, uWebSockets.js, Redis adapter, sticky sessions, nginx WebSocket proxy, JWT over WebSocket, rooms/namespaces, acknowledgments, binary data, compression, heartbeat, backpressure, horizontal pod autoscaling Documentation
Keywords that activate this skill. Click one to copy it.

This skill does not provide trigger words.

The downloaded .skill package contains the following fields.
Field Description
formatFormat tag (skill/v1)
skill_idUnique skill ID
nameSkill name
versionVersion
descriptionDescription
categoryCategories (array)
trigger_wordsTrigger words
tagsTags
sourceSource
source_urlSource URL (this page)
exported_atExported at (set per download)
system_promptSystem prompt body
model_configModel config: provider / model / temperature / max_tokens / top_p
examplesExamples
install_guideImport guide for Coze / Dify / Claude / custom frameworks
The same skill can be exported in different platform formats.
.skill Standard format with system_prompt and model_config, ready for any agent framework Download
.skillpro Enhanced format with scripts, tools, dependencies and hooks Download
.json Plain JSON export with system_prompt and model parameters only Download
Coze Markdown with frontmatter, for Coze platform import Download
Dify Dify DSL, import directly after creating an app Download

每日精选 Skill 推荐,免费送到你邮箱

输入邮箱,每天接收一个精选 AI Agent 技能推荐。完全免费,持续更新。

提交后我们会发送一封确认邮件,点击邮件里的链接才会开始收信。

完全免费,取消任意时间。我们不会发送垃圾邮件。