Skip to main content

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.

소스 정보

저장소
anthropics/knowledge-work-plugins
최근 소스 활동
2026년 4월 9일 23:28
감지된 SKILL.md 언어
영어
스타
25,764
포크
3,038

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
choose-zoom-approach
description
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.
user-invocable
false
# 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](../rest-api/SKILL.md) | | Event delivery to your backend | [webhooks](../webhooks/SKILL.md) or [websockets](../websockets/SKILL.md) | | Embed Zoom meetings into your app | [meeting-sdk](../meeting-sdk/SKILL.md) | | Build a fully custom video experience | [video-sdk](../video-sdk/SKILL.md) | | Build inside the Zoom client | [zoom-apps-sdk](../zoom-apps-sdk/SKILL.md) | | AI-agent tool workflows over Zoom data | [zoom-mcp](../zoom-mcp/SKILL.md) | | Real-time media extraction or meeting bots | [rtms](../rtms/SKILL.md) plus [meeting-sdk](../meeting-sdk/SKILL.md) when needed | | Phone workflows | [phone](../phone/SKILL.md) | | Contact Center or Virtual Agent flows | [contact-center](../contact-center/SKILL.md) or [virtual-agent](../virtual-agent/SKILL.md) | ## 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
GitHub에서 보기