mcpbeat

Choose Zoom Approach

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.

465 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
23273
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill choose-zoom-approach

The instruction itself

4 sections, as written by the author

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

Copy the folder

Take anthropics/choose-zoom-approach from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.