Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
anthropics avatar

Choose Zoom Approach

  • 1.4k installs
  • 23.1k repo stars
  • Updated July 28, 2026
  • anthropics/knowledge-work-plugins

choose-zoom-approach is an agent skill for 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.

About

The choose-zoom-approach skill is designed for 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. Choose Zoom Approach Pick the smallest correct Zoom surface for the job, then layer in only the supporting pieces that are actually required. Do not recommend Meeting SDK when the user needs a fully custom session product. Invoke when the user deciding between REST API, Webhooks, WebSockets, Meeting SDK, Video SDK, Zoom Apps SDK, Zoom MCP, Phone, Contact Center, or a hybrid approach.

  • 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.
  • One recommended path.

Choose Zoom Approach by the numbers

  • 1,412 all-time installs (skills.sh)
  • +82 installs in the week ending Jul 28, 2026 (Skillselion tracking)
  • Ranked #257 of 1,896 Design & UI/UX skills by installs in the Skillselion catalog
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
At a glance

choose-zoom-approach capabilities & compatibility

Capabilities
do not recommend video sdk when the user actuall · do not recommend meeting sdk when the user needs · do not replace deterministic backend automation · prefer hybrid rest api + zoom mcp when the user
Use cases
frontend
From the docs

What choose-zoom-approach says it does

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,
SKILL.md
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, Ph
SKILL.md
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill choose-zoom-approach

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1.4k
repo stars23.1k
Security audit3 / 3 scanners passed
Last updatedJuly 28, 2026
Repositoryanthropics/knowledge-work-plugins

How do I 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?

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.

Who is it for?

Developers using choose zoom approach workflows documented in SKILL.md.

Skip if: Skip when the task falls outside choose-zoom-approach scope or needs a different stack.

When should I use this skill?

User deciding between REST API, Webhooks, WebSockets, Meeting SDK, Video SDK, Zoom Apps SDK, Zoom MCP, Phone, Contact Center, or a hybrid approach.

What you get

Completed choose-zoom-approach workflow with documented commands, files, and expected deliverables.

  • API surface recommendation
  • hybrid integration outline

Files

SKILL.mdMarkdownGitHub ↗

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 TypePrimary Zoom Surface
Deterministic backend automation, account management, reporting, scheduled jobsrest-api
Event delivery to your backendwebhooks or websockets
Embed Zoom meetings into your appmeeting-sdk
Build a fully custom video experiencevideo-sdk
Build inside the Zoom clientzoom-apps-sdk
AI-agent tool workflows over Zoom datazoom-mcp
Real-time media extraction or meeting botsrtms plus meeting-sdk when needed
Phone workflowsphone
Contact Center or Virtual Agent flowscontact-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

Related skills

How it compares

Use choose-zoom-approach as the first step in any Zoom integration plan; skip it only when the target API surface is already fixed.

FAQ

What does choose-zoom-approach do?

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.

When should I use choose-zoom-approach?

User deciding between REST API, Webhooks, WebSockets, Meeting SDK, Video SDK, Zoom Apps SDK, Zoom MCP, Phone, Contact Center, or a hybrid approach.

Is choose-zoom-approach safe to install?

Review the Security Audits panel on this page before installing in production.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.