Plan Zoom Integration
Turn a vague Zoom app or MCP idea into a phased build plan with OAuth, webhooks, and launch risks spelled out before you write integration code.
Overview
Plan Zoom Integration is an agent skill most often used in Build (also Validate) that turns a Zoom integration idea into an architecture summary, auth checklist, phased delivery plan, and risk list with a concrete next a
Install
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill plan-zoom-integrationWhat is this skill?
- Six-step workflow from user flow and success criteria through smallest architecture-proving deliverable
- Explicit early risk callouts: OAuth setup, webhook verification, SDK limits, marketplace review, MCP client constraints
- Auth and scope checklist tied to account assumptions
- Phased delivery sequence: prototype, core integration, reliability, launch
- Related skill chain: setup-zoom-oauth, build-zoom-meeting-app, build-zoom-bot
- 6-step workflow
- 4 delivery phases (prototype, core, reliability, launch)
Adoption & trust: 838 installs on skills.sh; 19.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You want to build on Zoom but only have a rough feature idea—without a chosen surface, OAuth scopes, webhook strategy, or ordered milestones you will rework auth and review blockers late.
Who is it for?
Solo builders scoping a Zoom OAuth app, meeting extension, bot, or agent MCP client who need a written plan before touching the Marketplace or SDK.
Skip if: Teams that already have an approved spec and environment; use setup-zoom-oauth or build-zoom skills directly instead of replanning.
When should I use this skill?
Turn a Zoom integration idea into an implementation plan with architecture, auth, and delivery milestones when you need a practical build plan, phased delivery sequence, risk list, and next-step recommendation.
What do I get? / Deliverables
You get a practical Zoom integration plan with phases, scoped APIs, and flagged risks so you can invoke setup-zoom-oauth or a build-zoom skill on the smallest proof deliverable first.
- Architecture summary and Zoom products/APIs list
- Auth and scope checklist with delivery phases and risk register
- Immediate next action toward smallest architecture proof
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Integration delivery is the canonical shelf because the skill outputs architecture, API surface, and phased implementation milestones aimed at shipping Zoom-connected software. Integrations subphase fits the explicit focus on Zoom OAuth, webhooks, SDKs, meeting apps, bots, and marketplace constraints rather than generic product management.
Where it fits
Define success criteria and minimum Zoom surface before committing to a Marketplace submission timeline.
Sequence prototype OAuth, core API calls, webhook verification, and bot SDK work with explicit scope checklist.
Call out marketplace review and reliability phases so launch milestones are not treated as an afterthought.
How it compares
Use instead of ad-hoc chat architecture for Zoom—this skill is a structured planning ritual, not a one-shot API snippet generator.
Common Questions / FAQ
Who is plan-zoom-integration for?
Indie and solo developers planning Zoom Marketplace apps, internal integrations, meeting workflows, or agent tools that need Zoom APIs, with limited time to discover OAuth and webhook pitfalls upfront.
When should I use plan-zoom-integration?
Use it in Validate when narrowing scope for a Zoom feature, in Build before wiring OAuth and webhooks, or early Ship when marketplace review and reliability phases need to be sequenced—especially when MCP or multi-product Zoom surfaces are involved.
Is plan-zoom-integration safe to install?
It is documentation-driven planning with no built-in network calls; review the Security Audits panel on this Prism page and inspect the plugin source before trusting any related skills that perform OAuth or deployment.
Workflow Chain
Then invoke: setup zoom oauth, build zoom meeting app
SKILL.md
READMESKILL.md - Plan Zoom Integration
# /plan-zoom-integration > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md). Create a practical build plan for a Zoom integration or app. ## Usage ```text /plan-zoom-integration $ARGUMENTS ``` ## Workflow 1. Capture the target user flow and success criteria. 2. Choose the correct Zoom surface and supporting services. 3. Define auth requirements, scopes, and account assumptions. 4. Break implementation into phases: prototype, core integration, reliability, and launch. 5. Call out hard risks early: OAuth setup, webhook verification, SDK environment limits, marketplace review, or MCP client constraints. 6. End with the smallest deliverable that proves the architecture. ## Output - Architecture summary - Zoom products and APIs required - Auth and scope checklist - Delivery phases - Risks, open questions, and immediate next action ## Related Skills - [start](../start/SKILL.md) - [setup-zoom-oauth](../setup-zoom-oauth/SKILL.md) - [build-zoom-meeting-app](../build-zoom-meeting-app/SKILL.md) - [build-zoom-bot](../build-zoom-bot/SKILL.md)