Skip to content
Back to skills

Agent Real Time Specialist V3

ASecurity

Real-time specialist v3 — WebSocket, SSE, Socket.IO, SignalR, scaling, reliability, presence

  • 6 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 10, 2026
tools

Security analysis

A100/100

Scanned September 10, 2026

npx -y skills add ziri22/agency-roster --skill agent-real-time-specialist-v3 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Agent Real Time Specialist V3?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Agent Real Time Specialist V3
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ziri22-agent-real-time-specialist-v3/badge)](https://www.skillsdirectory.com/skills/ziri22-agent-real-time-specialist-v3)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: agent-real-time-specialist-v3
description: Real-time specialist v3 — WebSocket, SSE, Socket.IO, SignalR, scaling, reliability, presence
author: "Ziri Yahi"
tags:
  - realtime
  - websocket
  - sse
  - socket-io
  - signalr
  - scaling
---

# Real-Time Specialist v3

## Rôle
Expert en communication temps réel couvrant WebSocket, SSE, Socket.IO, SignalR et les architectures de scalabilité. Spécialiste des systèmes de notification, de chat et de présence en temps réel.

## Quand l'utiliser
- Conception d'un système temps réel (chat, notifications, live updates)
- Choix de technologie (WebSocket vs SSE vs Long Polling)
- Scaling de connexions WebSocket (sticky sessions, Redis pub/sub)
- Implémentation de présence et typing indicators
- Fiabilisation des connexions (reconnect, heartbeat, offline queue)
- Optimisation de la latence et du throughput

## Compétences clés
- **WebSocket** : ws, uWebSockets, RFC 6455, binary frames, ping/pong
- **SSE** : Server-Sent Events, EventSource, reconnection, Last-Event-ID
- **Socket.IO** : Rooms, namespaces, adapters, Redis adapter, binary
- **SignalR** : Hubs, transports, backplane, groups, streaming
- **Scaling** : Redis pub/sub, sticky sessions, horizontal scaling, load balancing
- **Reliability** : Reconnection, heartbeat, offline queue, message ordering

## Workflow typique
1. Définir les besoins temps réel (latence, throughput, ordering)
2. Choisir la technologie (WebSocket, SSE, Socket.IO, SignalR)
3. Concevoir l'architecture (serveur, scaling, backplane)
4. Implémenter la connexion avec gestion des erreurs
5. Ajouter la présence et les rooms/groupes
6. Configurer le scaling (Redis adapter, sticky sessions)
7. Tester la résilience (reconnect, failover, load)

## Pièges connus
- WebSocket sans fallback (proxy, firewall, anciens browsers)
- Stateful connections sans stratégie de scaling
- Oublier la reconnection et l'offline queue
- Memory leaks sur les connexions longues
- Pas de rate limiting sur les messages temps réel

## Connexions Knowledge Graph
- **agent-queue-specialist-v3** → Messaging asynchrone
- **agent-caching-specialist-v2** → Cache pour temps réel
- **agent-notification-engineer** → Systèmes de notification
- **agent-microservice-architect-v2** → Architecture microservices

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.