Zoom General

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

Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/openai/zoom-general/download

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

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

RUNBOOK.md

General Skill 5-Minute Preflight Runbook

Use this before deep debugging.

Skill Doc Standard Note

Skill entrypoint is SKILL.md.
This runbook is an operational convention (recommended), not a required skill file.
SDK/API names can drift by version; validate current names against docs/raw-docs before release.

1) Confirm Integration Surface

Use general as the routing hub for cross-product intent selection.
Confirm each use-case links to the correct product skill chain.
Use this runbook before troubleshooting multi-product integrations.

2) Confirm Required Credentials

Validate OAuth model selection (User OAuth vs Server-to-Server OAuth) before implementation.
Ensure required scopes are documented in each use-case.
Keep credential storage server-side; only expose short-lived tokens to clients.

3) Confirm Lifecycle Order

Pick product path (REST, Meeting SDK, Video SDK, Apps SDK, Phone, Contact Center, etc.).
Map auth flow and required scopes.
Define event model (webhooks or websockets) and correlation IDs.
Validate deployment model and operational monitoring requirements.

4) Confirm Event/State Handling

Keep use-case assumptions explicit when combining multiple products.
Store cross-system identifiers (meeting/session/call/engagement IDs) for traceability.
Document fallback behavior when API names/fields drift between versions.

5) Confirm Cleanup + Upgrade Posture

Remove stale route links whenever skills are renamed or moved.
Keep .env key references centralized in environment variable reference docs.
Refresh compatibility notes after each major SDK/API update cycle.

6) Quick Probes

Routing matrix still points to existing SKILL.md files.
Use-cases include at least one concrete implementation chain.
OAuth/scopes guidance matches current Marketplace app model.

7) Fast Decision Tree

Unsure between Meeting SDK and Video SDK -> route by UX model (Zoom meeting UI vs fully custom session).
Need lowest-latency events -> use websockets; otherwise webhooks are acceptable.
Scope/auth failures in execution -> pause and re-authorize with correct app type and scopes.

8) Source Checkpoints

Official docs

Raw docs in repo

raw-docs/developers.zoom.us/docs/
raw-docs/marketplacefront.zoom.us/sdk/

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.

Build MCP App
AnthropicOfficial
Build interactive UI widgets for MCP servers to render forms, pickers, and dashboards directly within the chat interface.
Automation and integrationsClaude CodeClaude appsOpenAI Codex+14 more
Apache-2.0GitHub stars of the source repository46.3k
MCP Integration
AnthropicOfficial
Comprehensive guide for integrating Model Context Protocol (MCP) servers into Claude Code plugins.
Automation and integrationsClaude CodeClaude appsOpenAI Codex+14 more
Apache-2.0GitHub stars of the source repository46.3k
Social Publishing
Seth Hobson· Community
Programmatically schedule and publish content across 13 social media platforms using the SocialClaw API.
Automation and integrationsClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository42.3k
Hermes Tweet
Seth Hobson· Community
Integrates X/Twitter research and action capabilities into the Hermes Agent framework with strict approval-gated security.
Automation and integrationsClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository42.3k
Paypal Integration
Seth Hobson· Community
A guide to integrating PayPal payment processing, including checkout flows, subscriptions, and IPN webhook handling.
Automation and integrationsClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository42.3k
Social Publishing Publisher
Seth Hobson· Community
An agent-driven social media publishing specialist for multi-platform campaign management via the SocialClaw API.
Automation and integrationsClaude Code
MITGitHub stars of the source repository42.3k

Download ZIP

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