choose-zoom-approach
anthropics/knowledge-work-plugins
Choose the right Zoom architecture for your use case: REST API, Webhooks, WebSockets, Meeting SDK, Video SDK, Zoom Apps SDK, MCP, Phone, or Contact Center.
What is choose-zoom-approach?
A decision framework for selecting the optimal Zoom integration surface based on your problem type. Use this when architecting Zoom integrations to avoid over-engineering and pick the smallest correct surface plus only necessary supporting pieces.
- Maps problem types to primary Zoom surfaces (REST API, Webhooks, WebSockets, Meeting SDK, Video SDK, Zoom Apps SDK, MCP, Phone, Contact Center)
- Identifies minimum supporting components required for each approach
- Enforces guardrails against common architectural mistakes (e.g., Video SDK when meeting semantics are needed)
- Recommends hybrid approaches when both stable system actions and AI-driven discovery are required
- Provides hard constraints and tradeoffs for each path
How to install choose-zoom-approach
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill choose-zoom-approachHow to use choose-zoom-approach
- 1.Identify your primary problem type (backend automation, event delivery, embedded meetings, custom video, etc.)
- 2.Locate that problem in the decision framework table to find the recommended primary Zoom surface
- 3.Review the guardrails to confirm your choice avoids common mistakes
- 4.Identify any minimum supporting components needed alongside the primary surface
- 5.Proceed to the recommended skill (e.g., rest-api, meeting-sdk, zoom-mcp) for implementation details
Use cases
- Deciding between REST API vs. Webhooks for event-driven backend automation
- Choosing between Meeting SDK and Video SDK when embedding Zoom into your application
- Selecting Zoom Apps SDK for building tools that run inside the Zoom client
- Architecting real-time media extraction or meeting bot workflows with RTMS
- Planning Contact Center or Virtual Agent integrations for customer service workflows
- Backend engineers architecting Zoom integrations
- Product managers evaluating Zoom integration approaches
- Developers building embedded Zoom experiences
- AI/agent developers working with Zoom data workflows
- Contact center and virtual agent platform builders
choose-zoom-approach FAQ
Use REST API for deterministic backend automation, account management, reporting, and scheduled jobs. Use Webhooks or WebSockets when you need event delivery to your backend in response to Zoom activities.
Meeting SDK embeds Zoom meetings into your app with Zoom meeting semantics and features. Video SDK builds a fully custom video experience from scratch without Zoom meeting semantics.
Use Zoom MCP for AI-agent tool workflows over Zoom data, especially when you need both stable system actions and AI-driven discovery. Often combined with REST API in a hybrid approach.
Start with the minimal Zoom surface that solves your problem, then add supporting components only if actually required. This avoids over-engineering and reduces complexity.
Yes, use RTMS plus Meeting SDK when needed for real-time media extraction or meeting bots that require access to meeting audio/video streams.
Full instructions (SKILL.md)
Source of truth, from anthropics/knowledge-work-plugins.
name: choose-zoom-approach description: 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. user-invocable: false
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-mcpwhen 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
Related skills
More from anthropics/knowledge-work-plugins and the wider catalog.
close-management
Manage month-end close with task sequencing, dependencies, and status tracking.
close-month
Close the books, reconcile against payment processors, forecast cash flow, and distribute the close packet—all in one chain.
code-review
Review code changes for security, performance, and correctness issues before merging.
comp-analysis
Benchmark compensation, analyze pay bands, and model equity grants for hiring and retention.
competitive-brief
Research competitors and identify positioning gaps, messaging opportunities, and market threats.
competitive-intelligence
Analyze competitive wins, losses, and battlecards to win more deals against named competitors.