mcpbeat

Plan Zoom Product

anthropics/plan-zoom-product

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.

395 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
23273
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill plan-zoom-product

The instruction itself

5 sections, as written by the author

/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

  • Identify the user's actual goal.
  • Classify whether the problem is automation, embedded meetings, custom video, in-client app behavior, event delivery, AI tooling, or support/phone/contact-center work.
  • If the request is ambiguous, ask one short clarifier before locking the recommendation.
  • Recommend the primary Zoom surface and list the minimum supporting pieces.
  • Explain why the rejected alternatives are worse for this case.
  • 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

How to use it

Copy the folder

Take anthropics/plan-zoom-product from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.