Skip to content
Business
Skill

/plan-zoom-integration

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.

From plugin
knowledge-work-plugins
24k192 skills5 agents15 commands40 MCP
Install
$ npx -y skills add anthropics/knowledge-work-plugins --skill plan-zoom-integration --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/plan-zoom-integration

Context preview

The summary Claude sees to decide when to auto-load this skill.

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.

SKILL.md

plan-zoom-integration.SKILL.md
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](../../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](../start/SKILL.md)
  • [setup-zoom-oauth](../setup-zoom-oauth/SKILL.md)
  • [build-zoom-meeting-app](../build-zoom-meeting-app/SKILL.md)
  • [build-zoom-bot](../build-zoom-bot/SKILL.md)
Read more
Ships withknowledge-work-plugins

Plugins that turn Claude into a specialist for your role, team, and company. Built for Claude Cowork, also compatible with Claude Code.

Get the whole plugin

Other skills on knowledge-work-plugins.