build-zoom-meeting-app
$
npx mdskill add openai/plugins/build-zoom-meeting-appBuilds embedded Zoom meeting experiences with proper SDK and API integration
- Solves the problem of embedding Zoom meetings into applications
- Uses Meeting SDK, REST API, Webhooks, RTMS, and Video SDK
- Routes to the correct SDK based on meeting or custom video requirements
- Delivers a structured workflow for meeting creation and join flows
SKILL.md
.github/skills/build-zoom-meeting-appView on GitHub ↗
--- name: build-zoom-meeting-app description: Use when embedding meetings. --- # /build-zoom-meeting-app Use this skill for embedded meeting experiences and meeting lifecycle implementation. ## Covers - Meeting SDK selection and platform routing - Join/auth implementation planning - Meeting creation plus join flow design - Web vs native platform considerations - Meeting SDK vs Video SDK boundary decisions ## Workflow 1. Confirm whether the user wants a Zoom meeting or a custom video session. 2. Route to Meeting SDK if the user needs actual Zoom meetings. 3. Pull in the relevant platform references. 4. Add REST API only for meeting creation, resource management, or reporting. 5. Add webhooks or RTMS only when the use case explicitly needs them. ## Primary References - [meeting-sdk](../meeting-sdk/SKILL.md) - [rest-api](../rest-api/SKILL.md) - [webhooks](../webhooks/SKILL.md) - [rtms](../rtms/SKILL.md) - [video-sdk](../video-sdk/SKILL.md) ## Common Mistakes - Using Video SDK for normal Zoom meeting embeds - Mixing resource-management APIs into the core join flow without reason - Skipping platform-specific SDK constraints until too late
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|