Plan Zoom Integration

AnthropicOfficialCreated by ZoomDistributed by Anthropic

Skill
Content generator
Automation and integrations
MIT
No issues found

From the author

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.

— the description by Zoom

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The plan-zoom-integration skill provides a systematic approach to scoping and planning Zoom-based applications. It guides users through defining user flows, selecting appropriate Zoom surfaces, identifying authentication requirements, and establishing a phased delivery roadmap. By highlighting potential technical risks early, it helps developers move from an initial idea to a concrete, actionable build strategy.

What it does

Defines the architecture and required Zoom APIs for a proposed integration.
Outlines authentication requirements and necessary OAuth scopes.
Structures the development process into logical phases from prototyping to launch.
Identifies critical project risks such as webhook verification and marketplace review requirements.
Recommends the smallest viable deliverable to validate the proposed architecture.

When to use it

When you have an idea for a Zoom app but need a technical roadmap.
When you need to identify the specific Zoom APIs and surfaces required for a feature.
When you are preparing to navigate Zoom's authentication and marketplace review processes.
When you need to break a complex integration project into manageable delivery milestones.

Advantages

Reduces ambiguity by forcing clear definition of user flows and success criteria.
Proactively identifies common integration pitfalls like OAuth and webhook constraints.
Provides a clear, phased path to production.
Helps align technical architecture with project goals.

Usage examples

“/plan-zoom-integration Build a bot that summarizes meeting transcripts and posts them to Slack.”: A detailed plan including the necessary Zoom Meeting APIs, OAuth scopes for reading transcripts, a phased development schedule, and risks related to webhook latency and data privacy.

Install

Download the skill as a ZIP:
https://autogineer.com/agent-skills/anthropics/plan-zoom-integration/download

Unzip it into the cross-client skills folder of your project:

mkdir -p .agents/skills && unzip plan-zoom-integration.zip -d .agents/skills

Documentation by Zoom

/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

Capture the target user flow and success criteria.
Choose the correct Zoom surface and supporting services.
Define auth requirements, scopes, and account assumptions.
Break implementation into phases: prototype, core integration, reliability, and launch.
Call out hard risks early: OAuth setup, webhook verification, SDK environment limits, marketplace review, or MCP client constraints.
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

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

Files

ATTRIBUTION.mdAdded by AutoGineer998 B
LICENSELicence file added by AutoGineer1.1 KiB
SKILL.md1.4 KiB

SKILL.md

/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

Capture the target user flow and success criteria.
Choose the correct Zoom surface and supporting services.
Define auth requirements, scopes, and account assumptions.
Break implementation into phases: prototype, core integration, reliability, and launch.
Call out hard risks early: OAuth setup, webhook verification, SDK environment limits, marketplace review, or MCP client constraints.
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

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

Requirements and compatibility

Written for: Claude Code, Claude apps

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Claude Code frontmatter

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by

Publisher

Anthropic (Official)

Distributed by

Anthropic

Source

anthropics/knowledge-work-plugins · partner-built/zoom-plugin/skills/plan-zoom-integration · commit e050c2e

Licence

MIT License (redistribution allowed)

LICENSE (added by AutoGineer from partner-built/zoom-plugin/LICENSE)
ATTRIBUTION.md (written by AutoGineer)

Synced

2026-11-09

AutoGineer is not affiliated with or endorsed by Zoom or Anthropic.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download plan-zoom-integration.zip