Generated banner for Plan Zoom Product
Generated logo for Plan Zoom Product

Plan Zoom Product

AnthropicOfficialCreated by ZoomDistributed by Anthropic

  • Skill
  • Workflow
  • Software development
  • MIT
  • No issues found

From the author

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.
— the description by Zoom

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The plan-zoom-product skill provides a structured approach to evaluating Zoom's various development surfaces, including APIs, SDKs, and specialized platforms like Contact Center or MCP. It guides users through identifying their core product goals, classifying the technical requirements, and selecting the optimal Zoom integration path while providing clear justifications for why other alternatives were rejected.

What it does

  • Identifies the core goal of a product idea or integration.
  • Classifies the technical requirement into categories like automation, embedded meetings, or custom video.
  • Recommends the primary Zoom surface and necessary supporting components.
  • Provides a comparative analysis of rejected alternatives.
  • Outlines a concrete implementation sequence for the chosen path.

When to use it

  • When you are unsure which Zoom SDK or API is best for your specific product feature.
  • When you need to understand the tradeoffs between using the Meeting SDK versus the Video SDK.
  • When planning a new integration and needing a clear roadmap of required Zoom components.
  • When you need to justify a technical architectural choice for a Zoom-based application.

Advantages

  • Reduces architectural uncertainty by providing clear decision criteria.
  • Ensures all necessary supporting components are identified early.
  • Provides clear rationale for why specific Zoom surfaces are better suited than others.
  • Offers a structured implementation plan to get started quickly.

Usage examples

“/plan-zoom-product I want to build a custom video interface for my telehealth app that doesn't look like a standard Zoom meeting.”
The skill recommends the Zoom Video SDK, explains why the Meeting SDK is unsuitable for custom UI, and outlines the necessary authentication and session management components.
“/plan-zoom-product I need to trigger a database update whenever a meeting ends.”
The skill recommends using Webhooks for event delivery, suggests the appropriate event subscription, and provides a plan for setting up the webhook listener.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/anthropics/plan-zoom-product/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip plan-zoom-product.zip -d .agents/skills

Documentation by Zoom

/plan-zoom-product

If you see unfamiliar placeholders or need to check which tools are connected, see 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

/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

  • start

  • choose-zoom-approach

  • design-mcp-workflow

Files

Requirements and compatibility

Written for: Claude Code, Claude apps

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Claude Code frontmatter

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Zoom
Publisher
Anthropic (Official)
Distributed by
Anthropic
Source
anthropics/knowledge-work-plugins · partner-built/zoom-plugin/skills/plan-zoom-product · commit e050c2e
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from partner-built/zoom-plugin/LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Zoom or Anthropic.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download plan-zoom-product.zip