plan-zoom-product — Claude Code skill: pick the right Zoom API
This skill helps you pick the right Zoom building surface for your use case: REST API, Webhooks, Meeting SDK, Video SDK, or another option. It gives a recommendation with clear tradeoffs.
npx skills add anthropics/knowledge-work-plugins --skill plan-zoom-product -a claude-codeWhat plan-zoom-product does
When you're building with Zoom, you have many options: REST API for meeting management, Webhooks for event reactions, Meeting SDK for embedded video calls, Video SDK for custom video UIs, Zoom Apps SDK for in-client apps. The skill examines your goal, sorts it into a category (automation, embedded meetings, custom video, in-client behavior, or events) and recommends the primary surface plus the minimum supporting pieces.
It explains why other options are worse for your specific case and lays out a concrete next-step plan. Inside are links to related skills — like choose-zoom-approach for narrower questions or design-mcp-workflow if you need MCP integration.
What it helps with
- choose between REST API, Webhooks, and Zoom SDKs
- understand tradeoffs of different ways to embed video calls
- plan the architecture for a Zoom integration
- find the right tool to automate meeting creation
Example prompts for the agent
- I want users to conduct video meetings directly in my web app
- I need to automatically create Zoom meetings via API and send join links
- How do I embed custom video instead of the standard Zoom client
How to install plan-zoom-product
1Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill plan-zoom-product -a claude-code2Manually: put the files in place
~/.claude/skills/plan-zoom-product/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/plan-zoom-product/
1Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill plan-zoom-product -a codex2Manually: put the files in place
.agents/skills/plan-zoom-product/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill plan-zoom-product -a cursor2Manually: put the files in place
.cursor/skills/plan-zoom-product/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install anthropics/knowledge-work-plugins plan-zoom-product2Manually: put the files in place
.github/skills/plan-zoom-product/SKILL.md1Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill plan-zoom-product -a gemini-cli2Platform CLI
gemini skills install https://github.com/anthropics/knowledge-work-plugins --path partner-built/zoom-plugin/skills/plan-zoom-productManually: put the files in place
.devin/skills/plan-zoom-product/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill plan-zoom-product -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set133
The whole set →Similar
Questions about plan-zoom-product
How do I install plan-zoom-product in Claude Code?
Run npx skills add anthropics/knowledge-work-plugins --skill plan-zoom-product -a claude-code twice. The skill will be available at ~/.claude/skills/plan-zoom-product/SKILL.md.
What does plan-zoom-product do?
It analyzes your Zoom use case, recommends the right building surface (REST API, Meeting SDK, Video SDK, etc.), explains the tradeoffs, and gives you a concrete implementation plan.
When should I use Video SDK instead of Meeting SDK?
Use Video SDK when you need full control over video components and the UI. Meeting SDK works if you're happy to embed a standard Zoom meeting with minimal customization.
Source text
SKILL.md · Apache-2.0
--- name: plan-zoom-product description: Choose the right Zoom building surface for a use case and explain the tradeoffs clearly. Use when deciding between REST API, Webhooks, WebSockets, Meeting SDK, Video SDK, Zoom Apps SDK, Phone, Contact Center, or MCP for a specific product idea or integration goal. argument-hint: "<product idea, app type, or integration goal>" user-invocable: false --- # /plan-zoom-product > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md). Choose between Zoom REST API, Webhooks, WebSockets, Meeting SDK, Video SDK, Zoom Apps SDK, Phone, Contact Center, or MCP for a specific use case. ## Usage ```text /plan-zoom-product $ARGUMENTS ``` ## Workflow 1. Identify the user's actual goal. 2. Classify whether the problem is automation, embedded meetings, custom video, in-client app behavior, event delivery, AI tooling, or support/phone/contact-center work. 3. If the request is ambiguous, ask one short clarifier before locking the recommendation. 4. Recommend the primary Zoom surface and list the minimum supporting pieces. 5. Explain why the rejected alternatives are worse for this case. 6. End with a concrete next-step plan. ## Output - Recommended Zoom surface - Supporting components required - Key tradeoffs and constraints - Suggested implementation sequence - Relevant skill links for the next step ## Related Skills - [start](../start/SKILL.md) - [choose-zoom-approach](../choose-zoom-approach/SKILL.md) - [design-mcp-workflow](../design-mcp-workflow/SKILL.md)
© anthropics · Apache-2.0 · anthropics/knowledge-work-plugins