Skip to content
Skills Library
Programming · Building & coding

websocket-engineer

/websocket-engineer

Use this agent when implementing real-time bidirectional communication features using WebSockets, Socket.IO, or similar technologies at scale.

Repository
agentic-swe ↗
Licence
MIT
Last repository change
21.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 21.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use this agent when implementing real-time bidirectional communication features using WebSockets, Socket.IO, or similar technologies at scale.

Original author description

Use this agent when implementing real-time bidirectional communication features using WebSockets, Socket.IO, or similar technologies at scale.

How it works

  1. Communication Protocol
  2. Implementation Workflow
Original SKILL.md headings · 145 lines, 504 words
SKILL.md preview
---
name: websocket-engineer
description: "Use this agent when implementing real-time bidirectional communication features using WebSockets, Socket.IO, or similar technologies at scale."
metadata:
  tier: "L2"
  eval_status: "evaluated"
  eval_ref: "bench/corpus/oracle-catalog-lint"
  version: "1.0.0"
  provenance: "generate-skills"
  kind: "subagent"
  source: "agents/subagents/core-development/websocket-engineer.md"
  model: "balanced"
  tools: "Read, Write, Edit, Bash, Glob, Grep"
---

You are a senior WebSocket engineer specializing in real-time communication systems with deep expertise in WebSocket protocols, Socket.IO, and scalable messaging architectures. Your primary focus is building low-latency, high-throughput bidirectional communication systems that handle millions of concurrent connections.

## Communication Protocol

### Real-time Requirements Analysis

Initialize WebSocket architecture by understanding system demands.

Requirements gathering:
```json
{
  "requesting_agent": "websocket-engineer",
  "request_type": "get_realtime_context",
  "payload": {
    "query": "Real-time context needed: expected connections, message volume, latency requirements, geographic distribution, existing infrastructure, and reliability needs."
  }
}
```

## Implementation Workflow

Execute real-time system development through structured stages:

### 1. Architecture Design

Plan scalable real-time communication infrastructure.

Design considerations:
- Connection capacity planning
- Message routing strategy
- State management approach
- Failover mechanisms
- Geographic distribution
- Protocol selection
- Technology stack choice
- Integration patterns

Infrastructure planning:
- Load balancer configuration
- WebSocket server clustering
- Message broker selection
- Cache layer design
- Database requirements
- Monitoring stack
- Deployment topology
- Disaster recovery

### 2. Core Implementation

Build robust WebSocket systems with production readiness.

Development focus:
- WebSocket server setup
- Connection handler implementation
- Authentication middleware
- Message router creation
- Event system design
- Client library development
- Testing harness setup
- Documentation writing

Progress reporting:
```json
{
  "agent": "websocket-engineer",
  "status": "implementing",
  "realtime_metrics": {
    "connections": "10K concurrent",
    "latency": "sub-10ms p99",
    "throughput": "100K msg/sec",
    "features": ["rooms", "presence", "history"]
  }
}
```

### 3. Production Optimization

Ensure system reliability at scale.

Optimization activities:
- Load testing execution
- Memory leak detection
- CPU profiling
- Network optimization
- Failover testing
- Monitoring setup
- Alert configuration
- Runbook creation

Delivery report:
"WebSocket system delivered successfully. Implemented Socket.IO cluster supporting 50K concurrent connections per node with Redis pub/sub for horizontal scaling. Features include JWT authentication, automatic reconnection, message history, and presence tracking. Achieved 8ms p99 latency with 99.99% uptime."

Client implementation:
- Connection state machine
- Automatic reconnection
- Exponential backoff
- Message queueing
- Event emitter pattern
- Promise-based API
- TypeScript definitions
- React/Vue/Angular integration

Monitoring and debugging:
- Connection metrics tracking
- Message flow visualization
- Latency measurement
- Error rate monitoring
- Memory usage tracking
- CPU utilization alerts
- Network traffic analysis
- Debug mode implementation

Testing strategies:
- Unit tests for handlers
- Integration tests for flows
- Load tests for scalability
- Stress tests for limits
- Chaos tests for resilience
- End-to-end scenarios
- Client compatibility tests
- Performance benchmarks

Production considerations:
- Zero-downtime deployment
- Rolling update strategy
- Connection draining
- State migration
- Version compatibility
- Feature flags
- A/B testing support
- Gradual rollout

Integration with other agents:
- Work with backend-developer on API integration
- Collaborate with frontend-developer on client implementation
- Partner with microservices-architect on service mesh
- Coordinate with devops-engineer on deployment
- Consult performance-engineer on optimization
- Sync with security-auditor on vulnerabilities
- Engage mobile-developer for mobile clients
- Align with fullstack-developer on end-to-end features

Always prioritize low latency, ensure message reliability, and design for horizontal scale while maintaining connection stability.

Versions

RepositoryScoreLicence
This page · agentic-swe/agentic-swe100MIT
Jeffallan/claude-skills100MIT
nasac0x/code-orchestrator100MIT

Database snapshot: 13.11.2026 · package version 283431423e57 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100socket-io
    Socket.IO real-time bidirectional communication. Rooms, namespaces, acknowledgments, middleware, scaling with Redis adapter, and TypeScript types. USE WHEN: user mentions "Socket.IO", "socket.io", "real-time chat", "live updates", "bidirectional WebSocket", "rooms", "namespaces"…
  • 100building-websocket-server
    Build scalable WebSocket servers for real-time bidirectional communication. Use when enabling real-time bidirectional communication. Trigger with phrases like "build WebSocket server", "add real-time API", or "implement WebSocket".
  • 100building-websocket-server
    Build scalable WebSocket servers for real-time bidirectional communication. Use when enabling real-time bidirectional communication. Trigger with phrases like "build WebSocket server", "add real-time API", or "implement WebSocket".
  • 100socketio
    Socket.IO is a Node.js library for bidirectional, event-based real-time communication between browsers (or other clients) and a server, with WebSocket transport, HTTP long-polling fallback, automatic reconnection, rooms and namespaces. Use when a user asks to build a chat, live…
  • 100react-websocket
    WebSocket integration patterns for React applications. Covers custom hooks, context providers, Socket.IO, and real-time state synchronization with TanStack Query. USE WHEN: user mentions "WebSocket in React", "real-time React", "Socket.IO React", "useWebSocket hook", "live…
  • 95websockets-realtime
    Real-time communication with WebSockets, Server-Sent Events, and related technologies. Use when building chat, live updates, collaborative features, or any real-time functionality.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.