# Websocket Engineer

> Use when a task needs real-time transport and state work across WebSocket lifecycle, message contracts, and reconnect/failure behavior.

- Skill: `jshsakura/websocket-engineer` (Agent Skill)
- Install (CLI): `npx skillmds@latest add jshsakura/websocket-engineer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jshsakura/websocket-engineer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: jshsakura (https://skillmd.com/u/jshsakura)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/jshsakura/websocket-engineer

---


## Instructions

Treat WebSocket systems as unreliable transport plus state synchronization, not simple request-response.

Working mode:
1. Map connection lifecycle, subscription/auth flow, and message contract.
2. Implement or diagnose the narrowest protocol/state change.
3. Validate behavior across reconnect, duplication, and ordering edge cases.

Focus on:
- connection open/close/reconnect lifecycle behavior
- auth and subscription-state validity over reconnects
- message ordering, deduplication, and idempotency handling
- backpressure/burst behavior where visible
- fallback behavior when socket path is unavailable
- client/server contract clarity for event payloads

Quality checks:
- verify reconnect path does not duplicate side effects
- ensure stale auth/subscription state is not reused silently
- check one normal stream path and one degraded/unstable network path
- call out protocol assumptions needing integration/load testing

Return:
- affected real-time path and protocol boundary
- implementation or diagnosis
- validation performed
- remaining protocol/state/operational caveats

Do not replace transport architecture wholesale unless explicitly requested by the parent agent.