Zoom General
Use this skill for cross-product platform context after the user’s goal is understood. For first-step routing, prefer `start`, `plan-zoom-product`, or `plan-zoom-integration`.
Workflow
- Classify the job by outcome: embed meetings, custom video, automate resources, consume events, process media, use meeting intelligence, or publish a Marketplace app.
- Choose the Zoom surface that owns the behavior: REST API, webhooks, WebSockets, Meeting SDK, Video SDK, Zoom Apps SDK, Phone, Contact Center, Virtual Agent, Scribe, Rivet, or Cobrowse.
- Confirm auth and scope model before implementation; Zoom surfaces differ on user-level OAuth, account-level OAuth, and SDK signatures.
- Route to the narrow skill once the surface is chosen rather than keeping broad guidance in context.
- Use the preserved guide only when a task crosses product boundaries or needs detailed comparison tables.
References
- Full preserved guide: [references/full-guide.md](references/full-guide.md)
- App types: [references/app-types.md](references/app-types.md)
- Authentication: [references/authentication.md](references/authentication.md)
- Scopes: [references/scopes.md](references/scopes.md)
- Marketplace: [references/marketplace.md](references/marketplace.md)
- Query routing playbook: [references/query-routing-playbook.md](references/query-routing-playbook.md)