Plan Zoom Product
Pick the correct Zoom surface—REST, webhooks, WebSockets, Meeting SDK, Video SDK, Apps SDK, Phone, Contact Center, or MCP—for a product idea with tradeoffs and a sequenced implementation plan.
Overview
Plan Zoom Product is an agent skill most often used in Validate (also Build integrations) that recommends the right Zoom API, SDK, webhook, or MCP surface for a product idea with tradeoffs and next steps.
Install
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill plan-zoom-productWhat is this skill?
- Six-step workflow: goal, classify problem type, optional clarifier, primary surface, rejected alternatives, concrete nex
- Classifies automation vs embedded meetings vs custom video vs in-client apps vs event delivery vs AI tooling vs phone/CC
- Output sections: recommended surface, supporting components, tradeoffs, implementation sequence, related skill links
- Explicit comparison across REST API, Webhooks, WebSockets, Meeting SDK, Video SDK, Zoom Apps SDK, Phone, Contact Center,
- Argument-hint driven: product idea, app type, or integration goal
- 6-step workflow ending in concrete next-step plan
- Compares 9 Zoom surfaces including MCP
Adoption & trust: 851 installs on skills.sh; 19.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have a Zoom-related product idea but cannot tell whether you need REST automation, an embedded SDK, webhooks, or MCP—and picking wrong wastes weeks.
Who is it for?
Indie builders scoping video, meetings, phone, or AI-agent Zoom integrations before writing code.
Skip if: Teams with an approved Zoom architecture doc already, or products with zero real-time communication needs.
When should I use this skill?
When deciding between Zoom REST API, Webhooks, WebSockets, Meeting SDK, Video SDK, Zoom Apps SDK, Phone, Contact Center, or MCP for a product idea or integration goal.
What do I get? / Deliverables
You leave with a primary Zoom surface, required supporting components, rejected options explained, and a sequenced plan linked to deeper Zoom skills.
- Recommended Zoom surface with supporting components list
- Tradeoffs, constraints, implementation sequence, and related skill links
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Surface choice happens while scoping an integration before you commit engineering weeks to the wrong SDK or event model. Scope subphase is canonical because the workflow starts from a product idea or integration goal and ends with rejected alternatives and next steps—not production deploy.
Where it fits
Brainstorm whether your AI copilot should join meetings via MCP or only post summaries through REST after you map user jobs.
Compare Meeting SDK embed cost versus Video SDK custom UI before committing your two-week prototype milestone.
Re-run the workflow when webhook delivery gaps force you to add WebSockets or Phone APIs mid-sprint.
How it compares
Use instead of guessing from Zoom marketing pages when you want a structured surface decision, not a low-level OAuth or webhook signing checklist skill.
Common Questions / FAQ
Who is plan-zoom-product for?
Solo founders and small teams planning Zoom-powered SaaS, embedded video, meeting apps, or agent tools who need a reasoned platform choice before implementation.
When should I use plan-zoom-product?
In Validate when scoping an integration goal; in Build integrations when re-evaluating SDK vs API vs MCP after a prototype; anytime you must explain tradeoffs to yourself or a contractor.
Is plan-zoom-product safe to install?
It is planning documentation without shell or network side effects; review the Security Audits panel on this Prism page for the plugin bundle you import.
Workflow Chain
Then invoke: choose zoom approach
SKILL.md
READMESKILL.md - Plan Zoom Product
# /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)