This is a routing layer that stops you from reaching for the wrong Zoom API. It maps your use case to the smallest correct surface: REST for backend automation, webhooks for events, Meeting SDK for embedding, Video SDK for custom experiences, Zoom Apps SDK for in-client tools, MCP for AI workflows, RTMS for media extraction. The guardrails are helpful. It won't let you pick Video SDK when you actually need meeting semantics, and it knows when to recommend a hybrid approach instead of forcing everything through one channel. Useful when the Zoom product surface is unfamiliar or when you're second-guessing an architecture decision.
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill choose-zoom-approach