Agent Skills
› anthropics/knowledge-work-plugins
› choose-zoom-approach
choose-zoom-approach
GitHub提供Zoom集成架构选型指南，根据具体场景推荐REST API、SDK或MCP等方案，并明确适用边界与实施步骤。
Trigger Scenarios
需要选择Zoom集成技术栈
决定使用哪种Zoom API或SDK
Install
npx skills add anthropics/knowledge-work-plugins --skill choose-zoom-approach -g -y
SKILL.md
Frontmatter
{
"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 |
| 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-mcpwhen 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
Version History
- 6f13415 Current 2026-07-05 18:31
