plan-zoom-product
anthropics/knowledge-work-plugins
How to install plan-zoom-product
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill plan-zoom-productFull 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
- 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
Related Skills
Related skills
More from anthropics/knowledge-work-plugins and the wider catalog.
data-visualization
Pick the right chart and generate publication-quality Python visualizations with built-in design and accessibility best practices.
code-review
Review code changes for security, performance, and correctness. Trigger with a PR URL or diff, "review this before I merge", "is this code safe?", or when checking a change for N+1 queries, injection risks, missing edge cases, or error handling gaps.
documentation
Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing — API docs, architecture docs, or operational runbooks.
build-dashboard
Build an interactive HTML dashboard with charts, filters, and tables. Use when creating an executive overview with KPI cards, turning query results into a shareable self-contained report, building a team monitoring snapshot, or needing multiple charts with filters in one browser-openable file.
task-management
Simple task management using a shared TASKS.md file. Reference this when the user asks about their tasks, wants to add/complete tasks, or needs help tracking commitments.
memory-management
Two-tier memory system that makes Claude a true workplace collaborator. Decodes shorthand, acronyms, nicknames, and internal language so Claude understands requests like a colleague would. CLAUDE.md for working memory, memory/ directory for the full knowledge base.