Agent skill · software engineering · anthropics
setup-zoom-websockets
Reference skill for Zoom WebSockets. Use after routing to a low-latency event workflow when persistent connections, faster event delivery, or security constraints make WebSockets preferable to webhooks.
Why this skill is useful
Provides specific WebSocket connection patterns and Zoom API integration commands that the AI wouldn't reliably generate on its own.
What it needs
Requires axios, ws installed locally. Requires zoom account access. About 3k tokens when loaded. Last updated 2026-08-07. 23,345 stars on the source repository.
What this skill does
/setup-zoom-websockets Background reference for persistent Zoom event streams. Prefer workflow routing first, then use this file when WebSockets are plausibly better than webhooks. WebSockets vs Webhooks Aspect WebSockets Webhooks -------- ------------ ---------- Connection Persistent, bidirectional One-time HTTP POST Latency Lower (no HTTP overhead) Higher (new connection per event) Security Direct connection, no exposed endpoint Requires endpoint validation, IP whitelisting Model Pull (you connect to Zoom) Push (Zoom connects to you) State Stateful (maintains connection) Stateless (each event independent) Setup More complex (access token, connection) Simpler (just endpoint URL) Choose WebSockets when: Real-time, low-latency updates are critical Security is paramount (banking, healthcare, finance) You don't want to expose a public endpoint You need bidirectional communication Choose Webhooks when: Simpler setup is preferred Small number of event notifications Existing HTTP infrastructure Prerequisites Server-to-Server OAuth app in Zoom Marketplace Account ID, Client ID, and Client Secret WebSocket subscription with events enabled Need help with S2S OAuth? See the zoom-oauth skill for complete authentication flows. Start troubleshooting fast: Use the 5-Minute Runbook before deep debugging. Quick Start 1. Create Server-to-Server OAuth App 1. Go to Zoom Marketplace 2. Create a Server-to-Server OAuth app 3. Copy Account ID, Client ID, Client Secret 2. Enable WebSocket Subscription 1. In your app, go to Feature → Event Subscriptions 2. Add an Event Subscription 3. Select WebSockets as the method type 4. Select events to subscribe to (e.g., meeting.created, meeting.started) 5. Save - an endpoint URL will be generated 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills anthropics/websockets