PluginBench
Skill
Official
Pass
Audit score 90

plan-zoom-integration

anthropics/knowledge-work-plugins

Turn a Zoom integration idea into a practical implementation plan with architecture, auth, and delivery milestones.

What is plan-zoom-integration?

This skill transforms a Zoom integration concept into a structured build plan. Use it when you need to define architecture, authentication requirements, phased delivery, and risk assessment before starting development.

  • Captures target user flow and success criteria
  • Identifies correct Zoom surfaces and supporting services
  • Defines auth requirements, scopes, and account assumptions
  • Breaks implementation into phases: prototype, core integration, reliability, and launch
  • Identifies hard risks early: OAuth setup, webhook verification, SDK limits, marketplace review
  • Recommends smallest deliverable to prove the architecture

How to install plan-zoom-integration

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

How to use plan-zoom-integration

  1. 1.Invoke the skill with a description of what you want to build (e.g., 'a Zoom bot that summarizes meetings')
  2. 2.Review the generated architecture summary and Zoom products/APIs required
  3. 3.Check the auth and scope checklist against your app's needs
  4. 4.Examine the phased delivery plan and identify your starting point
  5. 5.Address the listed risks and open questions before beginning development
  6. 6.Use the recommended next action to take the first concrete step

Use cases

Good for
  • Planning a Zoom meeting app integration with clear phases and milestones
  • Designing a Zoom bot with OAuth and webhook requirements mapped out
  • Scoping a Zoom integration before development to identify blockers and risks
  • Creating a delivery roadmap for marketplace-bound Zoom applications
  • Evaluating authentication and scope needs for Zoom API access
Who it's for
  • Engineering managers planning Zoom integrations
  • Developers scoping new Zoom app projects
  • Product teams defining phased rollouts for Zoom features
  • Architects evaluating Zoom API options and constraints

plan-zoom-integration FAQ

When should I use this skill?

Use it early in planning when you have a Zoom integration idea but need to understand the architecture, auth flow, and delivery sequence before coding.

What Zoom products and APIs does this cover?

The skill helps identify which Zoom surfaces (meetings, webinars, chat, etc.) and APIs (REST, SDK, webhooks, OAuth) are needed for your specific use case.

Does this skill set up OAuth for me?

No, it defines the OAuth requirements and scopes you'll need. Use the related skill 'setup-zoom-oauth' to configure OAuth after planning.

What risks does this skill identify?

It calls out common blockers: OAuth setup complexity, webhook verification, SDK environment limits, marketplace review requirements, and MCP client constraints.

What is the output format?

The skill produces an architecture summary, required Zoom products/APIs, auth checklist, phased delivery plan, risks, open questions, and a recommended next action.

Full instructions (SKILL.md)

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


name: plan-zoom-integration description: Turn a Zoom integration idea into an implementation plan with architecture, auth, and delivery milestones. Use when you need a practical build plan, phased delivery sequence, risk list, and next-step recommendation. argument-hint: "<what you want to build>" user-invocable: false

/plan-zoom-integration

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

Create a practical build plan for a Zoom integration or app.

Usage

/plan-zoom-integration $ARGUMENTS

Workflow

  1. Capture the target user flow and success criteria.
  2. Choose the correct Zoom surface and supporting services.
  3. Define auth requirements, scopes, and account assumptions.
  4. Break implementation into phases: prototype, core integration, reliability, and launch.
  5. Call out hard risks early: OAuth setup, webhook verification, SDK environment limits, marketplace review, or MCP client constraints.
  6. End with the smallest deliverable that proves the architecture.

Output

  • Architecture summary
  • Zoom products and APIs required
  • Auth and scope checklist
  • Delivery phases
  • Risks, open questions, and immediate next action

Related Skills

  • start
  • setup-zoom-oauth
  • build-zoom-meeting-app
  • build-zoom-bot