Labsco
anthropics logo

plan-zoom-product

โœ“ Officialโ˜… 22,378

by anthropic ยท part of anthropics/knowledge-work-plugins

There are nine different ways to build on Zoom; this works out which one fits what you are making, and why the others do not.

๐Ÿ”ฅ๐Ÿ”ฅโœ“ VerifiedFreeQuick setup
๐Ÿงฉ One of 177 skills in the anthropics/knowledge-work-plugins package โ€” works on its own, and pairs well with its siblings.

WHEN YOUR AGENT SHOULD USE IT

A QUICK BOUNDARY

USE FOR

  • Decide between the REST API, Webhooks, Meeting SDK, Video SDK, or MCP for an idea.
  • Work out whether a problem is automation, embedded meetings, or custom video.
  • Turn a vague Zoom idea into an ordered list of what to build first.

This is the playbook your agent receives when the skill activates โ€” you don't need to read it to use the skill, but it's here to audit before installing.

/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