Generated banner for Zoom General
Generated logo for Zoom General

Zoom General

OpenAIOfficialCreated by ZoomDistributed by OpenAI

  • Skill
  • Tool integration
  • Automation and integrations
  • MIT
  • Medium risk

From the author

Use when comparing products.
— the description by Zoom

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

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/openai/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

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

  1. Classify the job by outcome: embed meetings, custom video, automate resources, consume events, process media, use meeting intelligence, or publish a Marketplace app.

  2. 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.

  3. Confirm auth and scope model before implementation; Zoom surfaces differ on user-level OAuth, account-level OAuth, and SDK signatures.

  4. Route to the narrow skill once the surface is chosen rather than keeping broad guidance in context.

  5. Use the preserved guide only when a task crosses product boundaries or needs detailed comparison tables.

References

Files

references/sdk-logs-troubleshooting.md

SDK Logs & Troubleshooting

Collecting SDK logs for debugging and support.

Official Log Retrieval Guides

IMPORTANT: Always refer to the official Zoom log retrieval guides for the most up-to-date instructions:

If these URLs are unavailable, search for "zoom sdk log retrieval" to find the current documentation.

Overview

SDK logs help diagnose issues during development and for Zoom support escalations.

Enabling Logs

Web SDK
// Enable verbose logging
ZoomMtg.setLogLevel('verbose');

// Or for Video SDK
client.init('en-US', 'CDN', { debug: true });

Web Tracking ID: For Web SDK troubleshooting, get the Web Tracking ID which helps Zoom support trace your session.

Meeting SDK Web:

  1. Open browser DevTools → Network tab

  2. Look for a request starting with info?meetingNumber...

  3. Click on the request and check the Response Headers

  4. Find the x-zm-trackingid header value

  5. Copy this ID for support tickets

Video SDK Web:

  1. Open browser DevTools → Network tab

  2. Look for a request starting with lsdk?topic...

  3. Click on the request and check the Response Headers

  4. Find the x-zm-trackingid header value

  5. Copy this ID for support tickets

Example header:
x-zm-trackingid: v=2.0;clid=us04;rid=WEB_abc123xyz...

The Web Tracking ID is essential for Zoom support to investigate Web SDK issues.

To get help with logs and tracking IDs:

Include the tracking ID and relevant logs when requesting assistance.

iOS SDK
// Set log file path
let initParams = MobileRTCSDKInitParams()
initParams.enableLog = true
initParams.logFilePrefix = "zoom_sdk"
Android SDK
val initParams = ZoomSDKInitParams().apply {
    enableLog = true
    logSize = 5 // MB
}
Desktop SDKs (Windows/macOS/Linux)
initParam.enableLogByDefault = true;
initParam.logFilePrefix = L"zoom_sdk";

Log Locations

PlatformDefault Location
iOSApp's Documents directory
AndroidApp's files directory
Windows%APPDATA%\ZoomSDK\
macOS~/Library/Logs/ZoomSDK/
LinuxWorking directory

Common Issues and Solutions

IssuePossible CauseSolution
Join failedInvalid signatureCheck JWT generation (exp should be ~10s after iat, but iat can be up to 2 hours in past)
Join failedMeeting not foundVerify meeting number and that meeting hasn't ended
No audioPermission deniedRequest microphone permission before joining
No videoPermission deniedRequest camera permission before joining
Video scales downContainer too smallEnsure container is at least 1280x720 for 720p
SharedArrayBuffer errorMissing headersAdd COOP/COEP headers to server
Error code 0Actually successCheck SDK docs - 0 often means success, not error
SDK crashProGuard enabledDisable ProGuard/R8 for Zoom SDK classes
DLL not foundMissing filesCopy ALL DLLs from SDK bin folder
Debugging Join Failures
// Web SDK - enable verbose logging
ZoomMtg.setLogLevel('verbose');

// Check signature
console.log('Signature:', signature);
console.log('Meeting:', meetingNumber);

// Verify callback
client.join({
  // ...params
  success: (res) => console.log('Join success:', res),
  error: (err) => console.error('Join error:', err)
});
Debugging Audio/Video Issues
// Check device availability
const devices = await navigator.mediaDevices.enumerateDevices();
console.log('Audio inputs:', devices.filter(d => d.kind === 'audioinput'));
console.log('Video inputs:', devices.filter(d => d.kind === 'videoinput'));

// Check permissions
const micPermission = await navigator.permissions.query({ name: 'microphone' });
const camPermission = await navigator.permissions.query({ name: 'camera' });
console.log('Mic:', micPermission.state);
console.log('Cam:', camPermission.state);
Native SDK Crash Debugging

iOS:

// Enable crash reporting
MobileRTC.shared().setEnableCrashReport(true)

// Get logs
let logPath = MobileRTC.shared().getLogPath()
print("Logs at: \(logPath)")

Android:

// Check logcat for crashes
adb logcat -s ZoomSDK:V

// Disable ProGuard for Zoom
// In proguard-rules.pro:
-keep class us.zoom.** { *; }
-keep interface us.zoom.** { *; }
Error Code Reference
CodeMeaningPlatform
0Success (NOT error!)All
1Generic errorAll
2Invalid argumentAll
3Invalid tokenAll
4TimeoutAll
8SDK not authorizedWindows
100000400Meeting join failedWindows
MobileRTCMeetError_SuccessSuccessiOS
MEETING_STATUS_INMEETINGIn meetingAndroid

Getting Support

When contacting Zoom support:

  1. Include SDK version

  2. Attach log files

  3. Describe steps to reproduce

  4. Include error codes (check if 0 means success!)

Resources

Note for LLMs/Agents: If the log retrieval URLs return 404 or have moved, perform a web search for "zoom sdk log retrieval instructions" to find the current documentation.

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