Knowledge-work-plugins 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.

install

source · Clone the upstream repo

git clone https://github.com/anthropics/knowledge-work-plugins

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/anthropics/knowledge-work-plugins "$T" && mkdir -p ~/.claude/skills && cp -r "$T/partner-built/zoom-plugin/skills/choose-zoom-approach" ~/.claude/skills/anthropics-knowledge-work-plugins-choose-zoom-approach && rm -rf "$T"

manifest: partner-built/zoom-plugin/skills/choose-zoom-approach/SKILL.md

source content

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