Websocket Engineer
v0.1.0Use when building real-time communication systems with WebSockets or Socket.IO. Invoke for bidirectional messaging, horizontal scaling with Redis, presence tracking, room management.
⭐ 2· 2k·16 current·16 all-time
byVeera@veeramanikandanr48
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (WebSocket / Socket.IO engineering, scaling, presence, rooms) matches the included SKILL.md and reference documents. All samples and recommendations are relevant to real-time systems and there are no unrelated requirements (no binaries, env vars, or external services declared).
Instruction Scope
SKILL.md and the reference files contain implementation guidance and code snippets only — connection handling, Redis adapters, JWT auth, rate limiting, etc. There are no instructions to read local system files, exfiltrate data, call unknown endpoints, or access credentials beyond illustrative use of environment variables in examples.
Install Mechanism
No install spec and no code files to execute — lowest-risk delivery model. The repository contains only documentation and example snippets; nothing will be downloaded or written by the skill itself.
Credentials
The skill declares no required environment variables or credentials. References include example usages of common env vars (e.g., JWT_SECRET, SERVER_ID) in code samples — appropriate and expected for runnable examples but not requested by the skill itself.
Persistence & Privilege
The skill does not request persistent presence (always:false). It is user-invocable and allows model invocation (platform default), which is expected. There is no install that alters agent/system configuration.
Assessment
This skill is documentation and code examples for building WebSocket systems — it does not install software or ask for secrets. Before using: (1) review and adapt the code snippets to your environment (they reference env vars like JWT_SECRET, Redis URLs, etc.) and never paste real secrets into prompts, (2) audit any snippet you copy into production (authentication, CORS, rate limits, TLS and cookie handling need real configuration), and (3) note the skill source is unknown and has no homepage — if you want stronger provenance, ask the publisher for identity or prefer a vetted source. If you plan to let an autonomous agent invoke this skill, ensure the agent's permissions and any code it generates are restricted (test in staging first).Like a lobster shell, security has layers — review code before you run it.
latestvk9753ttg31nx91g6s9113jhs1n809p16
License
MIT-0
Free to use, modify, and redistribute. No attribution required.