Reference skill for Zoom Meeting SDK. Use after routing to a meeting-embed workflow when implementing real Zoom meeting joins, platform-specific SDK behavior, auth and join flows, waiting room issues, or meeting bot patterns.
This is a large reference skill for the Zoom Meeting SDK, covering how to embed the full Zoom meeting experience into web, mobile, desktop, and headless bot environments. It solves the problem of navigating platform-specific SDK behavior — auth and join flows, signature generation, waiting-room issues, and meeting bot patterns — by consolidating cross-platform guidance and routing the user to the correct implementation path for their target.
The skill spans many platforms (Web, Android, iOS, macOS, Electron, Linux, Windows, Unreal, React Native) with per-platform concepts, architecture notes, lifecycle workflows, join/start examples, environment-variable references, versioning/compatibility notes, and troubleshooting runbooks. It documents key correctness details such as the difference between the CDN `ZoomMtg` Client View (callback API) and the npm `ZoomMtgEmbedded` Component View (promise API), and it strongly emphasizes secure architecture: SDK signatures must be generated server-side and the SDK Secret must never be exposed in client code. It includes a server-side JWT signing example and hard routing guardrails distinguishing the Meeting SDK join path from REST `join_url` links.
It targets developers integrating Zoom meetings into their own applications across any supported platform, as well as those building meeting bots. The guidance is documentation and pattern reference rather than executable tooling, and its security posture is defensive — it repeatedly instructs keeping secrets server-side and using short-lived tokens.
Web, Android, iOS, macOS, Electron, Linux, Windows, Unreal, and React Native, each with its own concepts, examples, references, and troubleshooting docs.
A Zoom app with Meeting SDK credentials — an SDK Key and Secret from the Zoom Marketplace — plus a platform-specific development environment.
The skill is explicit that signatures must be generated server-side and the SDK Secret must never be exposed in client code; it provides a Node.js server-side JWT signing example and recommends short-lived, rotated tokens.
CDN provides the `ZoomMtg` global (Client View, full-page, callback-style API); npm provides `ZoomMtgEmbedded` (Component View, embeddable, promise-style API). They are different APIs.
Only switch to a REST `join_url` link flow if the user explicitly wants meeting resource management or browser join links; the Meeting SDK join path requires an SDK signature and SDK join call.
Quick Setup:
.claude/skills/Repository
anthropics/knowledge-work-plugins