setup-zoom-websockets
$
npx mdskill add openai/plugins/setup-zoom-websocketsSets up Zoom WebSockets for persistent event streaming
- Solves the need for real-time event handling with Zoom's WebSockets
- Uses Zoom's WebSockets API and event subscription model
- Evaluates connection requirements and event stream configuration
- Delivers normalized event data and connection observability
SKILL.md
.github/skills/setup-zoom-websocketsView on GitHub ↗
--- name: setup-zoom-websockets description: Use when building Zoom WebSockets. --- # Setup Zoom WebSockets Use this skill when the integration needs persistent Zoom event delivery instead of HTTP webhook callbacks. If normal webhook retries and delivery are enough, prefer `setup-zoom-webhooks`. ## Workflow 1. Confirm WebSockets are justified by latency, firewall, connection model, or deployment constraints. 2. Configure the app and event subscriptions for the required event stream. 3. Implement connection setup, authentication, heartbeat, reconnect, backoff, and shutdown handling. 4. Normalize events into the same internal contract used by webhook handlers when both are supported. 5. Add observability for connection state, reconnect count, event lag, and dropped messages. 6. Debug by isolating token/auth problems, app subscription settings, network proxies, TLS interception, and reconnect loops. ## References - Full preserved guide: [references/full-guide.md](references/full-guide.md) - Connection: [references/connection.md](references/connection.md) - Events: [references/events.md](references/events.md) - Common issues: [troubleshooting/common-issues.md](troubleshooting/common-issues.md)
More from openai/plugins
- accessibility-and-inclusive-visualizationMake data visualizations accessible and inclusive. Use when the user needs chart or diagram accessibility guidance, text alternatives for complex visuals, color and contrast review, keyboard support, reduced-motion behavior for animation or parallax, or an accessibility QA workflow for exported figures, UML-like diagrams, and dashboards.
- agent-browserBrowser automation CLI for AI agents. Use when the user needs to interact with websites, verify dev server output, test web apps, navigate pages, fill forms, click buttons, take screenshots, extract data, or automate any browser task. Also triggers when a dev server starts so you can verify it visually.
- agent-browser-verifyAutomated browser verification for dev servers. Triggers when a dev server starts to run a visual gut-check with agent-browser — verifies the page loads, checks for console errors, validates key UI elements, and reports pass/fail before continuing.
- agents-sdkBuild AI agents on Cloudflare Workers using the Agents SDK. Load when creating stateful agents, durable workflows, real-time WebSocket apps, scheduled tasks, MCP servers, or chat applications. Covers Agent class, state management, callable RPC, Workflows integration, and React hooks. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
- ai-elementsAI Elements component library guidance — pre-built React components for AI interfaces built on shadcn/ui. Use when building chat UIs, message displays, tool call rendering, streaming responses, reasoning panels, or any AI-native interface with the AI SDK.
- ai-gatewayVercel AI Gateway expert guidance. Use when configuring model routing, provider failover, cost tracking, or managing multiple AI providers through a unified API.
- ai-generation-persistenceAI generation persistence patterns — unique IDs, addressable URLs, database storage, and cost tracking for every LLM generation
- ai-sdkVercel AI SDK expert guidance. Use when building AI-powered features — chat interfaces, text generation, structured output, tool calling, agents, MCP integration, streaming, embeddings, reranking, image generation, or working with any LLM provider.
- aiq-deploy|
- aiq-research|