build-zoom-meeting-app — Codex skill: what it does, how to install
Guides the architecture for embedding Zoom meetings across web and native platforms. It picks the right SDK and maps out the join flow.
npx skills add openai/plugins --skill build-zoom-meeting-app -a codexWhat build-zoom-meeting-app does
This skill structures embedded video implementations. It first clarifies whether your application needs standard Zoom meetings or custom video sessions. For regular Zoom calls, it routes the implementation directly to the Meeting SDK and factors in platform differences between web and native targets.
Authentication and meeting lifecycles follow a strict boundary. The workflow reserves the REST API purely for room creation, reporting, and resource management. Webhooks or RTMS enter the setup only when real-time event tracking is essential.
A common mistake is picking Video SDK for normal Zoom meeting embeds. This skill prevents that mismatch and keeps the core join sequence free from unnecessary API calls.
What it helps with
- decide between Meeting SDK and Video SDK based on project needs
- design authentication and user join flows for Zoom meetings
- separate REST API management calls from real-time meeting joins
- plan webhook and RTMS integration for meeting events
Example prompts for the agent
- Help me design an embedded Zoom meeting experience using Meeting SDK
- What is the proper auth and join flow for a Zoom web app?
- Plan the meeting creation flow separating REST API calls from the join logic
How to install build-zoom-meeting-app
1Skills CLI (Vercel)
npx skills add openai/plugins --skill build-zoom-meeting-app -a codex2Manually: put the files in place
.agents/skills/build-zoom-meeting-app/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add openai/plugins --skill build-zoom-meeting-app -a claude-code2Manually: put the files in place
~/.claude/skills/build-zoom-meeting-app/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/build-zoom-meeting-app/
Manually: put the files in place
.cursor/skills/build-zoom-meeting-app/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install openai/plugins build-zoom-meeting-app2Manually: put the files in place
.github/skills/build-zoom-meeting-app/SKILL.mdPlatform CLI
gemini skills install https://github.com/openai/plugins --path plugins/zoom/skills/build-zoom-meeting-appManually: put the files in place
.devin/skills/build-zoom-meeting-app/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: Codex skills: how to install, where they live, how to call them
Questions about build-zoom-meeting-app
How to install build-zoom-meeting-app in Codex?
Run npx skills add openai/plugins --skill build-zoom-meeting-app -a codex or place the file at .agents/skills/build-zoom-meeting-app/SKILL.md.
What does the build-zoom-meeting-app skill do?
It guides the technical architecture for embedding Zoom meetings, helping you choose appropriate SDKs, design join lifecycles, and avoid architectural traps.
When does the skill use the REST API versus the Meeting SDK?
The Meeting SDK handles the live meeting interface and join process. The REST API is reserved strictly for creating meetings, handling resources, or pulling reports beforehand.
Source text
SKILL.md · MIT
--- 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
© Zoom · MIT · openai/plugins