Zoom General
OpenAIOfficialCreated by ZoomDistributed by OpenAI
- Skill
- Tool integration
- Automation and integrations
- MIT
- Medium risk
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
Zoom General serves as a strategic starting point for developers and architects to navigate the Zoom ecosystem. It provides a structured workflow to classify integration requirements, identify the correct Zoom product surface (such as APIs, SDKs, or webhooks), and determine the necessary authentication model. By guiding users through a decision-making process, it ensures that developers select the right tool for their specific use case before routing to more specialized skills.
What it does
- Classifies integration jobs based on desired outcomes like embedding meetings or automating resources.
- Maps requirements to specific Zoom surfaces including REST APIs, WebSockets, and various SDKs.
- Provides guidance on selecting the correct authentication and scope model for an integration.
- Facilitates routing to specialized skills once the product context is established.
- Offers comparative context for tasks that span multiple Zoom product boundaries.
When to use it
- When you are in the early stages of planning a Zoom integration and need to choose the right app type.
- When you need to compare different Zoom surfaces to determine which fits your technical requirements.
- When a task involves multiple Zoom products and requires a high-level architectural approach.
- When you need to confirm the correct authentication flow for a specific integration scenario.
Advantages
- Prevents premature selection of tools by enforcing a structured classification process.
- Clarifies the distinction between user-level OAuth, account-level OAuth, and SDK signatures.
- Reduces complexity by routing users to narrow, specialized skills after initial planning.
- Provides a clear decision matrix for choosing between General Apps, Server-to-Server OAuth, and Webhook Only apps.
Usage examples
- “I want to build an app that automates meeting reports. Which Zoom app type should I use?”
- The agent will guide you to classify the job as backend automation, leading to the recommendation of Server-to-Server OAuth for its lack of user interaction requirements.
- “Should I use the Meeting SDK or the Video SDK for my project?”
- The agent will help you compare the two based on your specific embedding needs and surface requirements, ensuring you choose the correct SDK for your use case.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/openai/zoom-general/downloadUnzip 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
Use this skill for cross-product platform context after the user’s goal is understood. For first-step routing, prefer start, plan-zoom-product, or plan-zoom-integration.
Workflow
Classify the job by outcome: embed meetings, custom video, automate resources, consume events, process media, use meeting intelligence, or publish a Marketplace app.
Choose the Zoom surface that owns the behavior: REST API, webhooks, WebSockets, Meeting SDK, Video SDK, Zoom Apps SDK, Phone, Contact Center, Virtual Agent, Scribe, Rivet, or Cobrowse.
Confirm auth and scope model before implementation; Zoom surfaces differ on user-level OAuth, account-level OAuth, and SDK signatures.
Route to the narrow skill once the surface is chosen rather than keeping broad guidance in context.
Use the preserved guide only when a task crosses product boundaries or needs detailed comparison tables.
References
Full preserved guide: references/full-guide.md
App types: references/app-types.md
Authentication: references/authentication.md
Scopes: references/scopes.md
Marketplace: references/marketplace.md
Query routing playbook: references/query-routing-playbook.md
Files
- ATTRIBUTION.mdAdded by AutoGineer866 B
- LICENSELicence file added by AutoGineer1.1 KiB
- RUNBOOK.md2.4 KiB
- SKILL.md1.4 KiB
- agents/openai.yaml133 B
- references/app-types.md2.6 KiB
- references/authentication.md2.0 KiB
- references/authorization-patterns.md21.2 KiB
- references/automatic-skill-chaining-rest-webhooks.md5.5 KiB
- references/community-repos.md9.1 KiB
- references/distributed-meeting-fallback-architecture.md14.0 KiB
- references/environment-variables.md3.0 KiB
- references/full-guide.md5.3 KiB
- references/interview-answer-routing.md796 B
- references/known-limitations.md2.5 KiB
- references/marketplace.md1.6 KiB
- references/meeting-webhooks-oauth-refresh-orchestration.md5.3 KiB
- references/query-routing-playbook.md2.7 KiB
- references/routing-implementation.md3.7 KiB
- references/scopes.md3.4 KiB
- references/sdk-logs-troubleshooting.md5.7 KiB
- references/sdk-upgrade-guide.md4.1 KiB
- references/sdk-upgrade-workflow.md3.5 KiB
- use-cases/ai-companion-integration.md9.8 KiB
- use-cases/ai-integration.md7.2 KiB
- use-cases/backend-automation-s2s-oauth.md4.9 KiB
- use-cases/collaborative-apps.md2.6 KiB
- use-cases/contact-center-app-lifecycle-and-context-switching.md1.2 KiB
- use-cases/contact-center-integration.md1.1 KiB
- use-cases/custom-meeting-ui-web.md2.8 KiB
- use-cases/custom-video.md5.6 KiB
- use-cases/customer-support-cobrowsing.md12.5 KiB
- use-cases/electron-meeting-embed.md1020 B
- use-cases/embed-meetings.md4.8 KiB
- use-cases/enterprise-app-deployment.md1.0 KiB
- use-cases/flutter-video-sessions.md910 B
- use-cases/form-completion-assistant.md15.3 KiB
- use-cases/hd-video-resolution.md8.8 KiB
- use-cases/high-volume-meeting-platform.md1.9 KiB
- use-cases/immersive-experiences.md2.9 KiB
- use-cases/in-meeting-apps.md7.4 KiB
- use-cases/marketplace-publishing.md9.2 KiB
- use-cases/meeting-automation.md6.1 KiB
- use-cases/meeting-bots.md10.6 KiB
- use-cases/meeting-details-with-events.md20.8 KiB
- use-cases/meeting-links-vs-embedding.md988 B
- use-cases/minutes-calculation.md22.5 KiB
- use-cases/native-meeting-sdk-multi-platform.md1.5 KiB
- use-cases/native-video-sdk-multi-platform.md1.2 KiB
- use-cases/prebuilt-video-ui.md12.4 KiB
- use-cases/probe-sdk-preflight-readiness-gate.md1.2 KiB
- use-cases/qss-monitoring.md2.7 KiB
- use-cases/raw-recording.md5.1 KiB
- use-cases/react-native-meeting-embed.md1.0 KiB
- use-cases/react-native-video-sessions.md953 B
- use-cases/real-time-media-streams.md5.4 KiB
- use-cases/recording-download-pipeline.md8.7 KiB
- use-cases/recording-transcription.md7.2 KiB
- use-cases/retrieve-meeting-and-subscribe-events.md32.9 KiB
- use-cases/rivet-event-driven-api-orchestrator.md1.3 KiB
- use-cases/saas-app-oauth-integration.md4.8 KiB
- use-cases/scribe-transcription-pipeline.md1.8 KiB
- use-cases/sdk-size-optimization.md5.0 KiB
- use-cases/sdk-wrappers-gui.md18.4 KiB
- use-cases/server-to-server-oauth-with-webhooks.md1.7 KiB
- use-cases/team-chat-llm-bot.md6.7 KiB
- use-cases/testing-development.md7.2 KiB
- use-cases/token-and-scope-troubleshooting.md2.4 KiB
- use-cases/transcription-bot-linux.md14.3 KiB
- use-cases/usage-reporting-analytics.md8.5 KiB
- use-cases/user-and-meeting-creation.md16.9 KiB
- use-cases/video-sdk-bring-your-own-storage.md6.9 KiB
- use-cases/virtual-agent-campaign-web-mobile-wrapper.md1.4 KiB
- use-cases/virtual-agent-knowledge-base-sync-pipeline.md1.1 KiB
- use-cases/web-sdk-embedding.md4.5 KiB
- use-cases/zoom-phone-smart-embed-crm.md876 B
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 an LLM provider for natural language understanding and can be chained with other Zoom skills.
Scenario
Create a chatbot that:
Responds to natural language queries
Can trigger Zoom Meeting creation
Can search and retrieve chat history
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 provider
↓
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 callLLM(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 llmClient = createLLMClient({
apiKey: process.env.LLM_API_KEY,
model: process.env.LLM_MODEL
});
async function callLLM(userMessage) {
const response = await llmClient.generate({
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:
zoom-team-chat: Receives command via webhook
LLM parses: "create_meeting" intent
zoom-rest-api: Creates meeting
zoom-team-chat: Sends confirmation with buttons
Example 2: Find User and Start DM
User: /bot who is John Doe?
Flow:
zoom-team-chat: Receives query
LLM identifies: "find_user" intent
zoom-rest-api: Searches users
zoom-team-chat: Shows user info with "Send DM" button
Example 3: Search Chat History
User: /bot find messages about project alpha
Flow:
zoom-team-chat: Receives search query
zoom-rest-api: Searches chat messages
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
LLM_API_KEY=
LLM_MODEL=
# Server
PORT=4000Advanced: 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
Next Steps
Build basic chatbot using Chatbot Setup
Add LLM integration
Implement intent parsing
Add REST API calls for meetings
Test end-to-end flow
Deploy to production
Requirements and compatibility
Written for: OpenAI Codex
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.
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
- OpenAI (Official)
- Distributed by
- OpenAI
- Source
- openai/plugins · plugins/zoom/skills/general · commit d420d13
- Licence
- MIT License (redistribution allowed)
- LICENSE (added by AutoGineer from plugins/zoom/LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Zoom or OpenAI.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download zoom-general.zip