zoom Start
Use this as the default entry skill for the plugin.
What This Skill Does
- Classifies the request by job-to-be-done, not by product name alone
- Routes into the right implementation skill
- Pulls in product-specific Zoom references only after the route is clear
- Prevents common early mistakes, especially Meeting SDK vs Video SDK and REST API vs MCP confusion
Routing Table
| If the user wants to... | Route to |
|---|---|
| Choose the right Zoom surface for a new project | plan-zoom-product |
| Create, select, or validate a Zoom Marketplace app or manifest | setup-zoom-marketplace-app |
| Set up OAuth, tokens, scopes, or app credentials | setup-zoom-oauth |
| Embed or customize a Zoom meeting flow | build-zoom-meeting-app |
| Build a bot, recorder, or real-time meeting processor | build-zoom-bot |
| Use Zoom-hosted MCP for AI workflows | setup-zoom-mcp |
| Debug a broken integration | debug-zoom |
Supporting Zoom References
Use these only after selecting the workflow:
- general
- rest-api
- meeting-sdk
- video-sdk
- webhooks
- websockets
- oauth
- Marketplace app management
- zoom-mcp
Operating Rules
- Prefer one clear recommendation over a product catalog dump.
- Ask a short clarifier only when the route is genuinely ambiguous.
- Keep the first response architectural and actionable, then go deep.
- Pull in deeper references only when they directly help the current decision or implementation.
- When a requested integration needs a Marketplace app created, updated, or validated, chain through setup-zoom-marketplace-app before OAuth or product implementation, then resume the originating workflow.