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

use-cases/token-and-scope-troubleshooting.md

Token and Scope Troubleshooting (Highest-Frequency Pattern)

This is the most common failure mode across Zoom REST API integrations and SDK backends:

  • Invalid access token

  • Access token is expired

  • does not contain scopes:[...]

  • "works for me but not for other users/accounts"

Skills Needed

OrderSkillPurpose
1zoom-oauthUnderstand which grant type you are using and why
2zoom-rest-apiTie the failing endpoint to required scopes and app type
3zoom-webhooks (optional)Verify you are validating webhook requests correctly

Triage Checklist

1. Identify Which Token You Are Using

Ask:

  • Which app type: Server-to-Server OAuth, General App (User OAuth), Chatbot, Meeting SDK, Video SDK?

  • Which token: user OAuth access token, S2S OAuth access token, bot token, SDK JWT?

Rule of thumb:

  • REST calls generally require OAuth access tokens (S2S or user-based depending on endpoint).

  • SDK join flows require SDK JWT/signature plus product-specific tokens (for some cases).

2. Confirm the Exact Endpoint and Operation

Token scope errors are endpoint-specific. Capture:

  • HTTP method + path (example: GET /v2/users/me/token?type=zak)

  • full error response body from Zoom

  • the token’s scope string (if present in token response)

3. Map Endpoint -> Required Scopes

Do not guess scopes.

  • Use zoom-rest-api references for the endpoint.

  • Use general/references/authorization-patterns.md for RBAC and scope validation strategies.

If you add scopes after users already installed/authorized:

  • existing users may need to reauthorize so the new scopes are granted

5. “Works on My Account” Usually Means One of These
  • different account plan/features enabled

  • missing admin role / privilege

  • endpoint requires :admin scope but token only has user scope

  • using the wrong me semantics for the app type

Common Fix Patterns

  • Add missing scopes, then reauthorize users (User OAuth).

  • Ensure you are using the correct grant (S2S for backend automation across an account; User OAuth when acting on behalf of users).

  • Validate that the endpoint actually supports your app type (some endpoints are not usable with some token types).

  • ../references/authorization-patterns.md

  • ../../rest-api/troubleshooting/token-scope-playbook.md

  • ../../oauth/SKILL.md

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