Build Zoom Meeting App
Plan and implement embedded Zoom meetings (Meeting SDK joins, web/mobile embeds, and meeting lifecycle) without picking Video SDK by mistake.
Overview
build-zoom-meeting-app is an agent skill for the Build phase that plans and implements embedded Zoom meetings via Meeting SDK, join/auth, and lifecycle flows while separating Meeting SDK from Video SDK.
Install
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill build-zoom-meeting-appWhat is this skill?
- 5-step workflow: confirm meeting vs custom video, route to Meeting SDK, pull platform refs, add REST only when needed, w
- Meeting SDK vs Video SDK boundary decisions for normal Zoom meeting embeds
- Join/auth implementation planning plus meeting creation and join flow design
- Web vs native platform considerations with links to meeting-sdk, rest-api, webhooks, rtms, and video-sdk references
- Common-mistakes guardrails against mixing resource APIs into core join flows
- 5-step workflow from meeting confirmation through optional webhooks/RTMS
- 5 primary reference skills: meeting-sdk, rest-api, webhooks, rtms, video-sdk
Adoption & trust: 835 installs on skills.sh; 19.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need users to join real Zoom meetings inside your app but you are unsure which Zoom SDK to use, which APIs belong in the join path, and how web vs native constraints affect the design.
Who is it for?
Solo builders shipping a SaaS or mobile app that must embed standard Zoom meetings rather than a fully custom video stack.
Skip if: Teams building a custom real-time media product with no Zoom meeting host/join semantics (Video SDK territory) or integrations that only need unrelated Zoom admin APIs with no embed.
When should I use this skill?
Implementing Meeting SDK joins, web or mobile meeting embeds, meeting lifecycle flows, or deciding between Meeting SDK and Video SDK.
What do I get? / Deliverables
You get a routed integration plan—Meeting SDK for real meetings, REST only where needed, optional webhooks/RTMS—with platform-specific references so implementation can start without rework.
- SDK and API routing decision (Meeting SDK vs Video SDK)
- Join/auth and meeting creation flow design aligned to platform constraints
Recommended Skills
Journey fit
Zoom SDK routing, join/auth, and meeting-creation flows are integration work that happens while building the product. The skill explicitly covers Meeting SDK selection, REST for meeting creation, and optional webhooks/RTMS—classic third-party integration scaffolding.
How it compares
Use for Meeting SDK meeting embeds and lifecycle planning—not as a substitute for ad-hoc API doc browsing when you already know you need Video SDK-only custom sessions.
Common Questions / FAQ
Who is build-zoom-meeting-app for?
Indie and solo developers implementing Zoom meeting embeds on web or mobile who need clear SDK boundaries and a minimal REST/webhook surface.
When should I use build-zoom-meeting-app?
During Build integrations when you are implementing Meeting SDK joins, designing create-then-join flows, or deciding Meeting SDK vs Video SDK before coding the meeting UX.
Is build-zoom-meeting-app safe to install?
Review the Security Audits panel on this Prism page and inspect the skill package in your repo before granting network or secret access to Zoom credentials.
SKILL.md
READMESKILL.md - Build Zoom Meeting App
# /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