start · anthropics, zoom-plugin — Claude Code skill for Zoom integration routing
This Claude Code skill picks a Zoom integration path and points to the implementation skill for the task. It starts from an app idea or a question about integrating Zoom.
MIT ★ 36,654 updated 2026-10-24
/plugin marketplace add anthropics/knowledge-work-plugins
/plugin install zoom-plugin@knowledge-work-pluginsWhat start does
The skill sorts a request by its goal, selects a suitable Zoom product, then routes to the relevant implementation skill. Product references are brought in after that choice.
Its routes cover OAuth, tokens and scopes, meeting flows, bots and real-time meeting processing, Zoom-hosted MCP, and integration debugging. It also guards against mixing up Meeting SDK and Video SDK or REST API and MCP. When the route is ambiguous, the skill asks a brief clarifying question.
What it helps with
- choose a Zoom product for a new integration
- find the skill for configuring OAuth and scopes
- decide which SDK fits a meeting or video feature
Example prompts for the agent
- Pick a Zoom integration path for this new app.
- Set up OAuth for my Zoom app and find the implementation skill.
- Help me choose between Meeting SDK, Video SDK, and MCP.
How to install start
1Plugin marketplace
/plugin marketplace add anthropics/knowledge-work-plugins/plugin install zoom-plugin@knowledge-work-pluginsThis installs the whole zoom-plugin plugin with all its skills
2Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill start -a claude-code3Manually: put the files in place
~/.claude/skills/start/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/start/
1Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill start -a codex2Manually: put the files in place
.agents/skills/start/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill start -a cursor2Manually: put the files in place
.cursor/skills/start/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install anthropics/knowledge-work-plugins partner-built/zoom-plugin/skills/start2Manually: put the files in place
.github/skills/start/SKILL.md1Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill start -a gemini-cli2Platform CLI
gemini skills install https://github.com/anthropics/knowledge-work-plugins --path partner-built/zoom-plugin/skills/startManually: put the files in place
.devin/skills/start/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about start
How do I install start in Claude Code?
Run these commands in order: /plugin marketplace add anthropics/knowledge-work-plugins, then /plugin install zoom-plugin@knowledge-work-plugins.
What does start do?
It identifies the right route for a Zoom task and sends the request to an implementation skill. Product references are loaded after the route is selected.
How does start help choose a Zoom integration?
It separates meeting and video SDK work, and distinguishes REST API use from MCP. If the request could fit more than one route, it asks a short clarifying question.
Source text
SKILL.md · MIT
--- name: start description: Start here for any Zoom integration or app idea. Use when you need to choose the right Zoom surface, shape the architecture, or route into the correct implementation skill without reading the whole Zoom doc set first. --- # 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](../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) | | Use Zoom-hosted MCP for AI workflows | [setup-zoom-mcp](../setup-zoom-mcp/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) - [zoom-mcp](../zoom-mcp/SKILL.md) ## Operating Rules 1. Prefer one clear recommendation over a product catalog dump. 2. Ask a short clarifier only when the route is genuinely ambiguous. 3. Keep the first response architectural and actionable, then go deep. 4. Pull in deeper references only when they directly help the current decision or implementation.
© Zoom · MIT · anthropics/knowledge-work-plugins
Similar skills
All skills for Agent setup: memory, context, orchestration →start by other authors comes first.