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/sdk-size-optimization.md
SDK Size Optimization
Reduce mobile app binary size when integrating Zoom Meeting SDK or Video SDK on iOS and Android.
Overview
Zoom SDKs add significant size to mobile apps. This guide covers Zoom-recommended techniques from the official developer forum and blog to minimize the impact on your app's download size.
Skills Needed
zoom-meeting-sdk (iOS, Android)
zoom-video-sdk (iOS, Android)
SDK Size Reference
Meeting SDK
| Platform | Configuration | Size |
|---|---|---|
| iOS | Universal (all architectures) | ~107 MB |
| Android | arm64-v8a + armeabi-v7a | ~97-108 MB |
| Android | arm64-v8a only | ~71 MB |
| Android | armeabi-v7a only | ~47 MB |
Video SDK
| Platform | Size |
|---|---|
| iOS/Android | ~75 MB |
Android: Zoom-Recommended Methods
1. ABI Filtering (Official Recommendation)
This is the primary method recommended by Zoom to reduce APK size. Filter to only the CPU architectures you need.
// build.gradle (app module)
android {
defaultConfig {
ndk {
// Option 1: Modern devices only (smallest size)
abiFilters 'arm64-v8a'
// Option 2: Broader device support
// abiFilters 'arm64-v8a', 'armeabi-v7a'
}
}
}Size Impact (from Zoom Dev Forum):
| Configuration | APK Size |
|---|---|
| No Zoom SDK | ~11 MB |
| arm64-v8a + armeabi-v7a | ~97 MB |
| arm64-v8a only | ~71 MB |
| armeabi-v7a only | ~47 MB |
Note: Most modern Android devices (2017+) use arm64-v8a. Only include armeabi-v7a if you need to support older 32-bit devices.
2. Android App Bundle (AAB)
Use Android App Bundles for Play Store distribution. Google Play automatically generates device-specific APKs:
android {
bundle {
abi {
enableSplit = true
}
}
}Users only download the architecture matching their device, reducing download size.
iOS: Zoom-Recommended Methods
App Store App Thinning (Automatic)
iOS App Store automatically applies App Thinning:
Delivers only the architecture slice needed for each device
No manual configuration required
Happens automatically when distributing through App Store
Verify in Xcode: Window → Organizer → Archives → App Thinning Report
What Does NOT Work
Zoom has confirmed the following approaches are NOT supported:
No Feature/Module Exclusion
From Zoom Developer Forum (August 2024):
"There are no new updates regarding reducing size of SDK"
Cannot remove virtual background module
Cannot remove screen sharing module
Cannot exclude any bundled features
All features are compiled together
No Dynamic Feature Module Support
Zoom has confirmed they do NOT support Android Dynamic Feature Modules:
Resource linking errors occur
Resources$NotFoundExceptionat runtimeCommunity workarounds are unsupported and may break
ProGuard/R8 Not Fully Supported
Warning: ProGuard/R8 causes crashes with Zoom SDK, even with Zoom's provided rules. Users report runtime crashes. Use at your own risk.
Bitcode Not Supported (iOS)
Zoom SDK does NOT support iOS Bitcode due to internal dependencies. However, Bitcode is no longer required by Apple (Xcode 15+).
Alternative Approaches
If SDK size is prohibitive for your use case:
1. Web SDK in WebView
Load the Web SDK in a native WebView instead of using the native SDK:
// iOS
let webView = WKWebView(frame: view.bounds)
webView.load(URLRequest(url: URL(string: "https://your-app.com/zoom-meeting")!))// Android
webView.loadUrl("https://your-app.com/zoom-meeting")Trade-offs:
No native SDK size impact
Reduced native feature access
Requires WebView setup and web hosting
2. Deep Link to Zoom App
Open meetings in the native Zoom app instead of embedding:
// iOS
if let url = URL(string: "zoomus://zoom.us/join?confno=\(meetingNumber)") {
UIApplication.shared.open(url)
}// Android
val intent = Intent(Intent.ACTION_VIEW,
Uri.parse("zoomus://zoom.us/join?confno=$meetingNumber"))
startActivity(intent)Trade-offs:
Zero SDK size impact
Requires Zoom app to be installed
Less integrated user experience
Summary
| Platform | Recommended Method | Expected Savings |
|---|---|---|
| Android | abiFilters 'arm64-v8a' | ~26 MB |
| Android | App Bundle (AAB) | Automatic per-device |
| iOS | App Thinning (automatic) | Automatic per-device |
Key Limitation: Zoom does not currently offer modular SDK downloads or feature exclusion. The SDK includes all features bundled together.
Resources
Zoom Blog - Reduce APK Size: https://developers.zoom.us/blog/reduce-apk-size-zoom-meeting-sdk-android/
Zoom Developer Forum - SDK Size Discussion: https://devforum.zoom.us/t/reducing-the-size-of-the-zoom-meeting-sdk-ios-android/94302
Android ABI Management: https://developer.android.com/ndk/guides/abis
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