build-zoom-bot
$
npx mdskill add openai/plugins/build-zoom-botBuild bots that join meetings, process media, and react to live session data
- Solve automation needs for meeting participation and real-time data handling
- Uses Meeting SDK, RTMS, REST API, Webhooks, and Scribe for implementation
- Routes tasks based on bot role: join, observe, transcribe, summarize, or act
- Delivers structured results via backend orchestration and event flow design
SKILL.md
.github/skills/build-zoom-botView on GitHub ↗
--- name: build-zoom-bot description: Use when building bots. --- # /build-zoom-bot Use this skill for automation that joins meetings, captures media, or reacts to live session data. ## Covers - Bot architecture - Meeting join strategy - Real-time media and transcript handling - Backend orchestration - Storage, post-processing, and event flow design ## Workflow 1. Clarify whether the bot needs to join, observe, transcribe, summarize, or act. 2. Route to Meeting SDK and RTMS as the core implementation path. 3. Add REST API for meeting/resource management and Webhooks for asynchronous events when needed. 4. Call out environment and lifecycle constraints early. ## Primary References - [meeting-sdk](../meeting-sdk/SKILL.md) - [rtms](../rtms/SKILL.md) - [scribe](../scribe/SKILL.md) - [rest-api](../rest-api/SKILL.md) - [webhooks](../webhooks/SKILL.md) ## Common Mistakes - Treating batch transcription and live media as the same workflow - Designing the bot before defining join authority and auth model - Forgetting post-meeting storage and retry behavior
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|