AutoGineer
Generated banner for Choose Zoom Approach
Generated logo for Choose Zoom Approach

Choose Zoom Approach

AnthropicOfficialCreated by ZoomDistributed by Anthropic

  • Skill
  • Guidelines
  • Automation and integrations
  • MIT
  • No issues found
Download ZIP

From the author

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.
— the description by Zoom

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a structured decision framework to help developers select the most efficient Zoom surface for their specific use case. By mapping problem types to the correct Zoom SDKs, APIs, or event-driven services, it ensures that integrations remain lightweight and maintainable. It emphasizes choosing the smallest correct surface area and layering only necessary components, while providing guardrails to prevent common architectural missteps.

What it does

  • Maps common development problem types to specific Zoom surfaces.
  • Distinguishes between Meeting SDK and Video SDK use cases.
  • Provides guidance on event-driven architectures using webhooks or WebSockets.
  • Suggests hybrid approaches for combining system actions with AI-driven discovery.
  • Defines clear guardrails to avoid over-engineering or incorrect tool selection.
  • Outlines the necessary components and next steps for implementation.

When to use it

  • When starting a new integration project with the Zoom platform.
  • When evaluating whether to use the Meeting SDK versus the Video SDK.
  • When determining if a requirement is best served by REST APIs or real-time event streams.
  • When planning to integrate AI-agent workflows with Zoom data.
  • When needing to decide between embedded client apps or backend automation.

Advantages

  • Prevents architectural bloat by recommending the smallest viable surface.
  • Reduces development time by clarifying the correct tool for specific requirements.
  • Provides clear separation between backend automation and frontend user experiences.
  • Ensures alignment with Zoom's intended use cases for each SDK and API.

Usage examples

“I need to build a custom video experience that does not look like a standard Zoom meeting. Which tool should I use?”
The skill recommends the Video SDK, noting that it is designed for fully custom video experiences, unlike the Meeting SDK which provides standard Zoom meeting semantics.
“We need to automate account reporting and trigger backend actions based on meeting events. What is the best approach?”
The skill suggests a combination of the REST API for deterministic account management and reporting, paired with webhooks or WebSockets for real-time event delivery.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/anthropics/choose-zoom-approach/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip choose-zoom-approach.zip -d .agents/skills

Documentation by Zoom

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

Files

ATTRIBUTION.md

Attribution

This folder is an unmodified copy of the Agent Skill "choose-zoom-approach", distributed by AutoGineer (https://autogineer.com/agent-skills).

The skill's own files are unmodified copies. AutoGineer is not affiliated with or endorsed by the author or the publisher.

Files added by AutoGineer

  • ATTRIBUTION.md: this file, written by AutoGineer

  • LICENSE: copied from partner-built/zoom-plugin/LICENSE

Requirements and compatibility

Written for: Claude Code, Claude apps

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Claude Code frontmatter

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Zoom
Publisher
Anthropic (Official)
Distributed by
Anthropic
Source
anthropics/knowledge-work-plugins · partner-built/zoom-plugin/skills/choose-zoom-approach · commit e050c2e
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from partner-built/zoom-plugin/LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Zoom or Anthropic.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download choose-zoom-approach.zip