AutoGineer
Generated banner for Zoom General
Generated logo for Zoom General

Zoom General

AnthropicOfficialCreated by ZoomDistributed by Anthropic

  • Skill
  • Meta (authoring, orchestration, planning, memory)
  • Agent tooling
  • MIT
  • Medium risk
Download ZIP

From the author

Cross-product Zoom reference skill. Use after the workflow is clear when you need shared platform guidance, app-model comparisons, authentication context, scopes, marketplace considerations, or API-vs-MCP routing.
— the description by Zoom

AutoGineer summary

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

The zoom-general skill serves as the primary entry point and classification layer for developers working with the Zoom platform. It provides a structured framework to identify the correct Zoom product, SDK, or API path based on user intent. It includes logic for routing complex queries, chaining multiple skills (such as combining REST APIs with OAuth and webhooks), and resolving ambiguities between deterministic automation and AI-driven agentic workflows.

What it does

  • Classifies developer queries to identify the appropriate Zoom product or SDK.
  • Provides a routing matrix to distinguish between REST API, MCP, and SDK use cases.
  • Offers guidance on choosing the correct Zoom app type (General, S2S, or Webhook-only).
  • Facilitates skill chaining for multi-step integrations like OAuth and webhook setups.
  • Provides decision frameworks for API vs. MCP and SDK vs. REST implementation paths.
  • Acts as a central index for all specialized Zoom developer skills.

When to use it

  • When you are unsure which Zoom SDK or API is required for your project.
  • When you need to determine if your task requires REST APIs, MCP tools, or a hybrid approach.
  • When planning a complex integration that involves authentication, webhooks, and API orchestration.
  • When you need to compare different Zoom app types to match your architectural requirements.
  • When you need to resolve ambiguity between similar Zoom products like Meeting SDK and Video SDK.

Advantages

  • Reduces development friction by directing users to the most relevant documentation and skills.
  • Ensures architectural consistency by enforcing standard routing patterns.
  • Simplifies complex decision-making through clear matrices and guardrails.
  • Promotes best practices for authentication and event-driven design.
  • Provides a unified entry point for navigating the entire Zoom developer ecosystem.

Usage examples

“I want to build a custom video UI for a Zoom meeting on the web, what should I use?”
The skill identifies the requirement for a custom UI around a real meeting and routes the user to the zoom-meeting-sdk-web-component-view skill.
“Should I use the REST API or MCP for my AI agent?”
The skill provides the API vs. MCP routing matrix, explaining that REST is for deterministic automation while MCP is for dynamic AI tool orchestration.
“How do I set up a server-side integration that handles meetings and webhooks?”
The skill suggests the Rivet SDK for scaffolding or chains the zoom-rest-api, zoom-oauth, and zoom-webhooks skills.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/anthropics/zoom-general/download

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

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

Documentation by Zoom

Zoom General (Cross-Product Skills)

Background reference for cross-product Zoom questions. Prefer the workflow skills first, then use this file for shared platform guidance and routing detail.

How zoom-general Routes a Complex Developer Query

Use zoom-general as the classifier and chaining layer:

  1. detect product signals in the query

  2. pick one primary skill

  3. attach secondary skills for auth, events, or deployment edges

  4. ask one short clarifier only when two routes match with similar confidence

Minimal implementation:

type SkillId =
  | 'zoom-general'
  | 'zoom-rest-api'
  | 'zoom-webhooks'
  | 'zoom-oauth'
  | 'zoom-meeting-sdk-web-component-view'
  | 'zoom-video-sdk'
  | 'zoom-mcp';

const hasAny = (q: string, words: string[]) => words.some((w) => q.includes(w));

function detectSignals(rawQuery: string) {
  const q = rawQuery.toLowerCase();
  return {
    meetingCustomUi: hasAny(q, ['zoom meeting', 'custom ui', 'component view', 'embed meeting']),
    customVideo: hasAny(q, ['video sdk', 'custom video session', 'peer-video-state-change']),
    restApi: hasAny(q, ['rest api', '/v2/', 'create meeting', 'list users', 's2s oauth']),
    webhooks: hasAny(q, ['webhook', 'x-zm-signature', 'event subscription', 'crc']),
    oauth: hasAny(q, ['oauth', 'pkce', 'token refresh', 'account_credentials']),
    mcp: hasAny(q, ['zoom mcp', 'agentic retrieval', 'tools/list', 'semantic meeting search']),
  };
}

function pickPrimarySkill(s: ReturnType<typeof detectSignals>): SkillId {
  if (s.meetingCustomUi) return 'zoom-meeting-sdk-web-component-view';
  if (s.mcp) return 'zoom-mcp';
  if (s.restApi) return 'zoom-rest-api';
  if (s.customVideo) return 'zoom-video-sdk';
  return 'zoom-general';
}

function buildChain(primary: SkillId, s: ReturnType<typeof detectSignals>): SkillId[] {
  const chain = [primary];
  if (s.oauth && !chain.includes('zoom-oauth')) chain.push('zoom-oauth');
  if (s.webhooks && !chain.includes('zoom-webhooks')) chain.push('zoom-webhooks');
  return chain;
}

Example:

  • Create a meeting, configure webhooks, and handle OAuth token refresh -> zoom-rest-api -> zoom-oauth -> zoom-webhooks

  • Build a custom video UI for a Zoom meeting on web -> zoom-meeting-sdk-web-component-view

For the full TypeScript implementation and handoff contract, use references/routing-implementation.md.

Choose Your Path

I want to...Use this skill
Build a custom web UI around a real Zoom meetingzoom-meeting-sdk-web-component-view
Build deterministic automation/configuration/reporting with explicit request controlzoom-rest-api
Receive event notifications (HTTP push)zoom-webhooks
Receive event notifications (WebSocket, low-latency)zoom-websockets
Embed Zoom meetings in my appzoom-meeting-sdk
Build custom video experiences (Web, React Native, Flutter, Android, iOS, macOS, Unity, Linux)zoom-video-sdk
Build an app that runs inside Zoom clientzoom-apps-sdk
Transcribe uploaded or stored media with AI Services Scribescribe
Access live audio/video/transcripts from meetingszoom-rtms
Enable collaborative browsing for supportzoom-cobrowse-sdk
Build Contact Center apps and channel integrationscontact-center
Build Virtual Agent web/mobile chatbot experiencesvirtual-agent
Build Zoom Phone integrations (Smart Embed, Phone API, webhooks, URI flows)phone
Build Team Chat apps and integrationszoom-team-chat
Build server-side integrations with Rivet (auth + webhooks + APIs)rivet-sdk
Run browser/device/network preflight diagnostics before joinprobe-sdk
Add pre-built UI components for Video SDKzoom-ui-toolkit
Implement OAuth authentication (all grant types)zoom-oauth
Build AI-driven tool workflows (AI Companion/agents) over Zoom datazoom-mcp
Build AI-driven Whiteboard workflows over Zoom Whiteboard MCPzoom-mcp/whiteboard
Build enterprise AI systems with stable API core + AI tool layerzoom-rest-api + zoom-mcp

Planning Checkpoint: Rivet SDK (Optional)

When a user starts planning a server-side integration that combines auth + webhooks + API calls, ask this first:

  • Rivet SDK is a Node.js framework that bundles Zoom auth handling, webhook receivers, and typed API wrappers.

  • Do you want to use Rivet SDK for faster scaffolding, or do you prefer a direct OAuth + REST implementation without Rivet?

Routing after answer:

  • If user chooses Rivet: chain rivet-sdk + oauth + rest-api.

  • If user declines Rivet: chain oauth + rest-api (+ webhooks or product skill as needed).

SDK vs REST Routing Matrix (Hard Stop)
User intentCorrect pathDo not route to
Embed Zoom meeting in app UIzoom-meeting-sdkREST-only join_url flow
Build custom web UI for a real Zoom meetingzoom-meeting-sdk-web-component-viewzoom-video-sdk
Build custom video UI/session appzoom-video-sdkMeeting SDK or REST meeting links
Get browser join links / manage meeting resourceszoom-rest-apiMeeting SDK join implementation

Routing guardrails:

  • If user asks for SDK embed/join behavior, stay in SDK path.

  • If the prompt says meeting plus custom UI/video/layout/embed, prefer zoom-meeting-sdk-web-component-view.

  • Only use zoom-video-sdk when the user is building a custom session product rather than a Zoom meeting.

  • Only use REST path for resource management, reporting, or link distribution unless user explicitly requests a mixed architecture.

  • For executable classification/chaining logic and error handling, see references/routing-implementation.md.

API vs MCP Routing Matrix (Hard Stop)
User intentCorrect pathWhy
Deterministic backend automation, account/user configuration, reporting, scheduled jobszoom-rest-apiExplicit request/response control and repeatable behavior
AI agent chooses tools dynamically, cross-platform AI tool interoperabilityzoom-mcpMCP is optimized for dynamic tool discovery and agentic workflows
Enterprise AI architecture (stable core + adaptive AI layer)zoom-rest-api + zoom-mcpAPIs run core system actions; MCP exposes curated AI tools/context

Routing guardrails:

  • Do not replace deterministic backend APIs with MCP-only routing.

  • Do not force raw REST-first routing when the task is AI-agent tool orchestration.

  • Prefer hybrid routing when the user needs both stable automation and AI-driven interactions.

  • MCP remote server works over Streamable HTTP/SSE; use this path when the target client/agent supports MCP transports (for example Claude or VS Code).

  • Do not design per-tenant custom MCP endpoint provisioning; Zoom MCP endpoints are shared at instance/cluster level.

  • Source: https://developers.zoom.us/docs/mcp/library/resources/apis-vs-mcp/

Ambiguity Resolution (Ask Before Routing)

When a prompt matches both API and MCP paths with similar confidence, ask one short clarifier before execution:

  • Do you want deterministic REST API automation, AI-agent MCP tooling, or a hybrid of both?

Then route as:

  • REST answer → zoom-rest-api

  • MCP answer → zoom-mcp

  • Hybrid answer → zoom-rest-api + zoom-mcp

MCP Availability and Topology Notes

  • Zoom-hosted MCP access is evolving; docs indicate a model where Zoom exposes product-scoped MCP servers (for example Meetings, Team Chat, Whiteboard).

  • Use zoom-mcp as the parent MCP entry point.

  • Route Whiteboard-specific MCP requests to zoom-mcp/whiteboard.

  • When a request is product-specific and MCP coverage exists, route to that MCP product surface first; otherwise use REST/SDK skills for deterministic implementation.

Webhooks vs WebSockets

Both receive event notifications, but differ in approach:

Aspectwebhookszoom-websockets
ConnectionHTTP POST to your endpointPersistent WebSocket
LatencyHigherLower
SecurityRequires public endpointNo exposed endpoint
SetupSimplerMore complex
Best forMost use casesReal-time, security-sensitive

Common Use Cases

Use CaseDescriptionSkills Needed
Meeting + Webhooks + OAuth RefreshCreate a meeting, process real-time updates, and refresh OAuth tokens safely in one designzoom-rest-api + zoom-oauth + zoom-webhooks
Scribe Transcription PipelineTranscribe uploaded files or S3 archives with AI Services Scribe using fast mode or batch jobsscribe + optional zoom-rest-api + optional zoom-webhooks
APIs vs MCP RoutingDecide whether to route to deterministic Zoom APIs, AI-driven MCP, or a hybrid designzoom-rest-api and/or zoom-mcp
Custom Meeting UI (Web)Build a custom video UI for a real Zoom meeting in a web app using Meeting SDK Component Viewzoom-meeting-sdk-web-component-view + zoom-oauth
Meeting AutomationSchedule, update, delete meetings programmaticallyzoom-rest-api
Meeting BotsBuild bots that join meetings for AI/transcription/recordingmeeting-sdk/linux + zoom-rest-api + optional zoom-webhooks
High-Volume Meeting PlatformDesign distributed meeting creation and event processing with retries, queues, and reconciliationzoom-rest-api + zoom-webhooks + zoom-oauth
Recording & TranscriptionDownload recordings, get transcriptszoom-webhooks + zoom-rest-api
Recording Download PipelineAuto-download recordings to your own storage (S3, GCS, etc.)zoom-webhooks + zoom-rest-api
Real-Time Media StreamsAccess live audio, video, transcripts via WebSocketzoom-rtms + zoom-webhooks
In-Meeting AppsBuild apps that run inside Zoom meetingszoom-apps-sdk + zoom-oauth
React Native Meeting EmbedEmbed meetings into iOS/Android React Native appszoom-meeting-sdk-react-native + zoom-oauth
Native Meeting SDK Multi-Platform DeliveryAlign Android, iOS, macOS, and Unreal Meeting SDK implementations under one auth/version strategyzoom-meeting-sdk + platform skills
Native Video SDK Multi-Platform DeliveryAlign Android, iOS, macOS, and Unity Video SDK implementations under one auth/version strategyzoom-video-sdk + platform skills
Electron Meeting EmbedEmbed meetings into desktop Electron appszoom-meeting-sdk-electron + zoom-oauth
Flutter Video SessionsBuild custom mobile video sessions in Flutterzoom-video-sdk-flutter + zoom-oauth
React Native Video SessionsBuild custom mobile video sessions in React Nativezoom-video-sdk-react-native + zoom-oauth
Immersive ExperiencesCustom video layouts with Layers APIzoom-apps-sdk
Collaborative AppsReal-time shared state in meetingszoom-apps-sdk
Contact Center App Lifecycle and Context SwitchingBuild Contact Center apps that handle engagement events and multi-engagement statecontact-center + zoom-apps-sdk
Virtual Agent Campaign Web and Mobile WrapperDeliver one campaign-driven bot flow across web and native mobile wrappersvirtual-agent + contact-center
Virtual Agent Knowledge Base Sync PipelineSync external knowledge content into Zoom Virtual Agent using web sync or custom API connectorsvirtual-agent + zoom-rest-api + zoom-oauth
Zoom Phone Smart Embed CRM IntegrationBuild CRM dialer and call logging flows using Smart Embed plus Phone APIsphone + zoom-oauth + zoom-webhooks
Rivet Event-Driven API OrchestratorBuild a Node.js backend that combines webhooks and API actions through Rivet module clientsrivet-sdk + zoom-oauth + zoom-rest-api
Probe SDK Preflight Readiness GateAdd browser/device/network diagnostics and readiness policy before Meeting SDK or Video SDK joinsprobe-sdk + zoom-meeting-sdk or zoom-video-sdk

Complete Use-Case Index

Prerequisites

  1. Zoom account (Pro, Business, or Enterprise)

  2. App created in Zoom App Marketplace

  3. OAuth credentials (Client ID and Secret)

References

Quick Start

  1. Go to marketplace.zoom.us

  2. Click Develop → Build App

  3. Select app type (see references/app-types.md)

  4. Configure OAuth and scopes

  5. Copy credentials to your application

Detailed References

SDK Maintenance

Resources

Environment Variables

Operations

  • RUNBOOK.md - 5-minute preflight and debugging checklist.

Files

use-cases/team-chat-llm-bot.md

Use Case: AI-Powered Team Chat Bot with LLM Integration

Build an intelligent Zoom Team Chat bot that uses Claude/GPT for natural language understanding and can be chained with other Zoom skills.

Scenario

Create a chatbot that:

  1. Responds to natural language queries

  2. Can trigger Zoom Meeting creation

  3. Can search and retrieve chat history

  4. Provides intelligent assistance across Zoom products

Skills Required

  • zoom-team-chat - Primary skill for chatbot functionality

  • zoom-rest-api - For meeting creation, user management

  • oauth - For user authentication flows (optional)

  • zoom-meeting-sdk - For advanced meeting integrations (optional)

Architecture

User sends message → Team Chat Bot receives webhook
                            ↓
                     Call LLM (Claude/GPT)
                            ↓
                     Parse LLM response for intent
                            ↓
         ┌──────────────────┼──────────────────┐
         │                  │                  │
    Create Meeting    Get User Info    Send Response
    (REST API)        (REST API)       (Team Chat)

Implementation Steps

1. Setup Team Chat Bot

Skill: zoom-team-chat

// Handle bot notification
case 'bot_notification': {
  const { toJid, cmd, accountId } = payload;
  
  // Call LLM
  const llmResponse = await callClaude(cmd);
  
  // Check for intents
  const intent = parseIntent(llmResponse);
  
  if (intent.type === 'create_meeting') {
    await handleCreateMeeting(toJid, accountId, intent);
  } else {
    await sendTextMessage(toJid, accountId, llmResponse);
  }
}
2. Create Meeting Intent

Skills: zoom-team-chat + zoom-rest-api

async function handleCreateMeeting(toJid, accountId, intent) {
  // Extract meeting details from LLM response
  const { topic, start_time, duration } = intent.details;
  
  // Create meeting using REST API
  const meeting = await fetch('https://api.zoom.us/v2/users/me/meetings', {
    method: 'POST',
    headers: {
      'Authorization': `Bearer ${userAccessToken}`,
      'Content-Type': 'application/json'
    },
    body: JSON.stringify({
      topic,
      type: 2, // Scheduled meeting
      start_time,
      duration
    })
  });
  
  const meetingData = await meeting.json();
  
  // Send meeting details back to Team Chat
  await sendChatbotMessage(toJid, accountId, {
    head: { text: 'Meeting Created' },
    body: [
      { type: 'message', text: `Meeting "${topic}" created successfully!` },
      {
        type: 'fields',
        items: [
          { key: 'Start Time', value: start_time },
          { key: 'Duration', value: `${duration} minutes` },
          { key: 'Join URL', value: meetingData.join_url }
        ]
      },
      {
        type: 'actions',
        items: [
          { text: 'Join Meeting', value: `join_${meetingData.id}`, style: 'Primary' },
          { text: 'Share Link', value: `share_${meetingData.id}`, style: 'Default' }
        ]
      }
    ]
  });
}
3. LLM Integration with Intent Parsing

Skill: zoom-team-chat

const Anthropic = require('@anthropic-ai/sdk');
const anthropic = new Anthropic({ apiKey: process.env.ANTHROPIC_API_KEY });

async function callClaude(userMessage) {
  const response = await anthropic.messages.create({
    model: 'claude-sonnet-4-20250514',
    max_tokens: 1024,
    system: `You are a Zoom assistant bot. You can help users with:
- Creating meetings
- Finding user information
- Answering questions about Zoom
- General assistance

When a user wants to create a meeting, respond with JSON:
{
  "intent": "create_meeting",
  "details": {
    "topic": "Meeting topic",
    "start_time": "ISO 8601 format",
    "duration": 60
  }
}

Otherwise, provide a helpful text response.`,
    messages: [{ role: 'user', content: userMessage }]
  });
  
  return response.content[0].text;
}

function parseIntent(llmResponse) {
  try {
    // Check if response is JSON
    if (llmResponse.trim().startsWith('{')) {
      const intent = JSON.parse(llmResponse);
      return intent;
    }
  } catch (e) {
    // Not JSON, regular text response
  }
  
  return { type: 'text_response', message: llmResponse };
}

Skill Chaining Examples

Example 1: Create Meeting from Chat

User: /bot schedule a team standup tomorrow at 10am for 30 minutes

Flow:

  1. zoom-team-chat: Receives command via webhook

  2. LLM parses: "create_meeting" intent

  3. zoom-rest-api: Creates meeting

  4. zoom-team-chat: Sends confirmation with buttons

Example 2: Find User and Start DM

User: /bot who is John Doe?

Flow:

  1. zoom-team-chat: Receives query

  2. LLM identifies: "find_user" intent

  3. zoom-rest-api: Searches users

  4. zoom-team-chat: Shows user info with "Send DM" button

Example 3: Search Chat History

User: /bot find messages about project alpha

Flow:

  1. zoom-team-chat: Receives search query

  2. zoom-rest-api: Searches chat messages

  3. zoom-team-chat: Displays results with links

Environment Variables

# Team Chat (from zoom-team-chat skill)
ZOOM_CLIENT_ID=
ZOOM_CLIENT_SECRET=
ZOOM_BOT_JID=
ZOOM_VERIFICATION_TOKEN=
ZOOM_ACCOUNT_ID=

# LLM Integration
ANTHROPIC_API_KEY=    # or OPENAI_API_KEY

# Server
PORT=4000

Advanced: Multi-Skill Integration

With webhooks

Subscribe to meeting events and notify in Team Chat:

// Webhook handler for meeting events
app.post('/meeting-webhook', (req, res) => {
  const { event, payload } = req.body;
  
  if (event === 'meeting.started') {
    // Notify in Team Chat
    await sendChatbotMessage(channelJid, accountId, {
      body: [
        { type: 'message', text: `Meeting "${payload.object.topic}" has started!` },
        {
          type: 'actions',
          items: [
            { text: 'Join Now', value: `join_${payload.object.id}`, style: 'Primary' }
          ]
        }
      ]
    });
  }
  
  res.status(200).send();
});

Testing Checklist

  • [ ] Bot responds to natural language queries

  • [ ] Can create meetings from chat commands

  • [ ] Meeting details sent back to Team Chat

  • [ ] Buttons trigger appropriate actions

  • [ ] LLM intent parsing works correctly

  • [ ] Error handling for failed API calls

  • [ ] Multi-turn conversation support

Resources

  • zoom-team-chat skill

  • zoom-rest-api skill

  • oauth skill

  • Chatbot Setup Example

  • LLM Integration Example

  • Claude Chatbot Sample

Next Steps

  1. Build basic chatbot using Chatbot Setup

  2. Add LLM integration

  3. Implement intent parsing

  4. Add REST API calls for meetings

  5. Test end-to-end flow

  6. Deploy to production

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, Needs an MCP server

Security

What our scanner noticed· Medium risk

  • Possible data-exfiltration endpoints
  • Instructions that use the network

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
Zoom
Publisher
Anthropic (Official)
Distributed by
Anthropic
Source
anthropics/knowledge-work-plugins · partner-built/zoom-plugin/skills/general · commit e050c2e
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from partner-built/zoom-plugin/LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

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 zoom-general.zip