Agent skill · product strategy · anthropics
choose-zoom-approach
Choose the right Zoom architecture for a use case. Use when deciding between REST API, Webhooks, WebSockets, Meeting SDK, Video SDK, Zoom Apps SDK, Zoom MCP, Phone, Contact Center, or a hybrid approach.
Why this skill is useful
Provides a structured decision framework for selecting the appropriate Zoom integration method based on specific use cases, which the AI wouldn't reliably generate on its own.
What it needs
About 1k tokens when loaded. Last updated 2026-08-07. 23,345 stars on the source repository.
What this skill does
Choose Zoom Approach Pick the smallest correct Zoom surface for the job, then layer in only the supporting pieces that are actually required. Decision Framework Problem Type Primary Zoom Surface --- --- Deterministic backend automation, account management, reporting, scheduled jobs rest-api Event delivery to your backend webhooks or websockets Embed Zoom meetings into your app meeting-sdk Build a fully custom video experience video-sdk Build inside the Zoom client zoom-apps-sdk AI-agent tool workflows over Zoom data zoom-mcp Real-time media extraction or meeting bots rtms plus meeting-sdk when needed Phone workflows phone Contact Center or Virtual Agent flows contact-center or virtual-agent Guardrails Do not recommend Video SDK when the user actually needs Zoom meeting semantics. Do not recommend Meeting SDK when the user needs a fully custom session product. Do not replace deterministic backend automation with MCP-only guidance. Prefer hybrid rest-api + zoom-mcp when the user needs both stable system actions and AI-driven discovery. What To Produce One recommended path Minimum supporting components Hard constraints and tradeoffs Immediate next implementation step
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills anthropics/choose-zoom-approach