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.

2,060
installs: 0 up / 0 down, score 0.00
votes: 31,299
repo stars
Updated: less than a month ago
In the catalog since: 1 Oct 2026
From: anthropics/knowledge-work-plugins

Get it through your agent npx skills add anthropics/knowledge-work-plugins@choose-zoom-approach

Skill instructions

Rendered from the published SKILL.md, 32 lines.

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

Get it through your agent

Call the Graph-of-Skills MCP server's retrieve_skill_bundle tool and it returns this skill's text inside your budget.

{
  "tool": "retrieve_skill_bundle",
  "arguments": {
    "query": "choose-zoom-approach"
  }
}

New to this? Set up Graph-of-Skills or get a free key. The text on this page comes from its authors: how skills are sourced and what we check. If none fits your task, your agent can write a skill for your own library. To keep a skill from your own library on a machine, see how to install one of your skills.

Share on X Share on LinkedIn Share on Bluesky Share on Hacker News

Share on Reddit

Source

Source repository anthropics/knowledge-work-plugins
Listing on skills.sh

From anthropics/knowledge-work-plugins via skills.sh

Related skills

plan-zoom-product
Choose the right Zoom building surface for a use case and explain the tradeoffs clearly. Use when deciding between REST API, Webhooks, WebSockets, Meeting SDK, Video SDK, Zoom Apps SDK, Phone, Contact Center, or MCP for a specific product idea or integration goal.
2,084 installs
build-zoom-rest-api-app
Reference skill for Zoom REST API. Use after choosing an API-based workflow when you need endpoint selection, resource-management patterns, OAuth requirements, rate-limit awareness, or API error debugging.
2,094 installs
api-integration-surface-strategy
Decide which integration surfaces a platform offers external developers and AI agents - REST, GraphQL, gRPC, SQL access, bulk data sharing, webhooks, SDKs, CLI, MCP, embedded components - and in what build order, sequenced by reversal cost and audience rather than novelty. Use whenever the user mentions which API to build first, adding a GraphQL or MCP layer, an integration-surface roadmap, API-first vs embedded-first, or a missing surface blocking deals - even if they never say "integration surface". Umbrella strategy only - once a surface is chosen, per-surface design belongs to siblings such as samber/developer-platform-skills@webhook-platform-design and samber/developer-platform-skills@sdk-portfolio-strategy.
7,419 installs
pick-ui-library
Pick the right library for a given frontend task from a curated, opinionated list — numbers, OTP inputs, charts, command menus, virtualization, drag and drop, toasts, state, styling, and more. Only runs when explicitly invoked; it does not trigger on its own.
181,098 installs
context7-mcp
This skill should be used when the user asks about libraries, frameworks, API references, or needs code examples. Activates for setup questions, code generation involving libraries, or mentions of specific frameworks like React, Vue, Next.js, Prisma, Supabase, etc.
6,127 installs

More from anthropics/knowledge-work-plugins

data-visualization
Create effective data visualizations with Python (matplotlib, seaborn, plotly). Use when building charts, choosing the right chart type for a dataset, creating publication-quality figures, or applying design principles like accessibility and color theory.
13,704 installs
documentation
Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing — API docs, architecture docs, or operational runbooks.
10,248 installs
code-review
Review code changes for security, performance, and correctness. Trigger with a PR URL or diff, "review this before I merge", "is this code safe?", or when checking a change for N+1 queries, injection risks, missing edge cases, or error handling gaps.
9,892 installs
build-dashboard
Build an interactive HTML dashboard with charts, filters, and tables. Use when creating an executive overview with KPI cards, turning query results into a shareable self-contained report, building a team monitoring snapshot, or needing multiple charts with filters in one browser-openable file.
9,096 installs
system-design
Design systems, services, and architectures. Trigger with "design a system for", "how should we architect", "system design for", "what's the right architecture for", or when the user needs help with API design, data modeling, or service boundaries.
7,469 installs

Content is provided as published by its creators; you are responsible for how you use it.

To request removal, use the contact form.