PluginBench
Skill
Official
Pass
Audit score 90

plan-zoom-product

anthropics/knowledge-work-plugins

Choose the right Zoom building surface for your use case and explain the tradeoffs.

What is plan-zoom-product?

This skill helps you select the optimal Zoom integration approach—whether REST API, Webhooks, WebSockets, Meeting SDK, Video SDK, Zoom Apps SDK, Phone, Contact Center, or MCP—for a specific product idea or integration goal. Use it when deciding which Zoom surface best fits your requirements.

  • Classifies your use case into categories: automation, embedded meetings, custom video, in-client behavior, event delivery, AI tooling, or support/contact-center work
  • Recommends the primary Zoom surface and lists minimum supporting components
  • Explains why rejected alternatives are worse for your specific case
  • Provides key tradeoffs and constraints for the chosen approach
  • Suggests a concrete implementation sequence and next steps

How to install plan-zoom-product

npx skills add https://github.com/anthropics/knowledge-work-plugins --skill plan-zoom-product
Claude Code
Cursor
Windsurf
Cline

How to use plan-zoom-product

  1. 1.Describe your product idea, app type, or integration goal to the skill
  2. 2.Provide clarification if the skill asks a short follow-up question
  3. 3.Review the recommended Zoom surface and supporting components
  4. 4.Examine the tradeoffs and constraints for your use case
  5. 5.Follow the suggested implementation sequence and next-step links

Use cases

Good for
  • Deciding whether to use REST API or Webhooks for meeting automation
  • Choosing between Meeting SDK and Video SDK for an embedded video experience
  • Determining if Zoom Apps SDK or MCP is better for in-client integrations
  • Planning a contact-center or phone-based workflow on Zoom
  • Evaluating WebSockets vs. Webhooks for real-time event delivery
Who it's for
  • Product managers evaluating Zoom integration options
  • Developers planning Zoom-based applications
  • Architects designing meeting or video workflows
  • Integration engineers choosing between Zoom building surfaces

plan-zoom-product FAQ

When should I use REST API vs. Webhooks?

Use REST API for on-demand operations (create meetings, manage users). Use Webhooks for event-driven automation (react to meeting starts, participant joins).

What's the difference between Meeting SDK and Video SDK?

Meeting SDK provides full meeting UI and controls; Video SDK lets you build custom video experiences from scratch.

Should I use Zoom Apps SDK or MCP?

Zoom Apps SDK embeds behavior directly in the Zoom client; MCP integrates Zoom with external AI agents and tools.

How do I know if WebSockets are necessary?

Use WebSockets only if you need sub-second real-time updates; Webhooks are simpler and sufficient for most event-driven workflows.

What's the next step after choosing a surface?

The skill provides concrete implementation links; typically you'll move to architecture design or SDK setup based on your chosen surface.

Full instructions (SKILL.md)

Source of truth, from anthropics/knowledge-work-plugins.


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.

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

Related Skills

  • start
  • choose-zoom-approach
  • design-mcp-workflow