start

Name: start
Availability: InStock
Author: Zoom

Route user requests to the correct Zoom integration skill based on the job-to-be-done.

7|2|Updated Apr 2, 2026

Search Tags:#workflow #integration #routing #oauth #decision #mcp #zoom

Ready to run

npx skills add https://github.com/zoom/zoom-plugin --skill start-zoom

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: start
Source: https://github.com/zoom/zoom-plugin/tree/main/skills/start
Command: npx skills add https://github.com/zoom/zoom-plugin --skill start-zoom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Start skill reduces cognitive load by routing user requests to the correct Zoom integration skill based on the job to be done, rather than product name, enabling faster, more accurate project planning.

Core Features & Use Cases

Routing to the appropriate sub-skill (for example, setup-zoom-oauth, build-zoom-meeting-app, or debug-zoom) based on the user's goal.
Pulls in product-specific Zoom references only after the route is resolved to avoid information overload.
Prevents common early mistakes such as confusion between Meeting SDK vs Video SDK and REST API vs MCP when choosing the workflow.

Quick Start

Tell your goal and it will route you to the correct Zoom implementation skill.

Frequently Asked Questions about start

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I choose the right Zoom integration for my workflow?▼

To choose the right Zoom integration, clarify your job-to-be-done first. Routing based on your specific goal—rather than product name—prevents common setup mistakes and directs you to the correct implementation skill efficiently.

What is the difference between Zoom Meeting SDK and Video SDK for app development?▼

The difference between Zoom Meeting SDK and Video SDK is a common early mistake when choosing a workflow. Clarifying your development goal first ensures you route to the correct SDK and avoid architectural confusion during setup.

How do I set up Zoom OAuth for my integration?▼

To set up Zoom OAuth, you route to the setup-zoom-oauth sub-skill after defining your integration goal. This ensures you pull in the correct authentication references only when the workflow is resolved, avoiding information overload.

When should I use Zoom REST API vs MCP for routing requests?▼

Deciding between Zoom REST API vs MCP depends on your specific job-to-be-done. Routing logic clarifies your workflow goal first to prevent this common early mistake, ensuring you select the appropriate architecture before implementation.

Can I debug my Zoom integration workflow without knowing the exact product?▼

Yes, you can debug your Zoom integration by stating your general goal. The routing skill directs you to the debug-zoom sub-skill based on the job-to-be-done, pulling product-specific references only after the correct route is resolved.

What is the best way to plan a Zoom meeting app architecture?▼

The best way to plan a Zoom meeting app architecture is to define your job-to-be-done clearly. Routing to the build-zoom-meeting-app sub-skill happens only after goal clarification, preventing early setup mistakes and ensuring efficient workflow selection.