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 SDK confusion
Routing Table
| If the user wants to... | Route to | |---|---| | Choose the right Zoom surface for a new project | [plan-zoom-product](../plan-zoom-product/SKILL.md) | | Set up OAuth, tokens, scopes, or app credentials | [setup-zoom-oauth](../setup-zoom-oauth/SKILL.md) | | Embed or customize a Zoom meeting flow | [build-zoom-meeting-app](../build-zoom-meeting-app/SKILL.md) | | Build a bot, recorder, or real-time meeting processor | [build-zoom-bot](../build-zoom-bot/SKILL.md) | | Debug a broken integration | [debug-zoom](../debug-zoom/SKILL.md) |
Supporting Zoom References
Use these only after selecting the workflow:
- [general](../general/SKILL.md)
- [rest-api](../rest-api/SKILL.md)
- [meeting-sdk](../meeting-sdk/SKILL.md)
- [video-sdk](../video-sdk/SKILL.md)
- [webhooks](../webhooks/SKILL.md)
- [websockets](../websockets/SKILL.md)
- [oauth](../oauth/SKILL.md)
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.