AutoGineer
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
Download ZIP

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-upgrade-workflow.md

SDK Upgrade Workflow (Changelog + RSS)

Reusable process for upgrading Zoom SDK integrations from an older customer version to latest with low regression risk.

Use This When

  • Customer is multiple versions behind.

  • Breaking changes may exist between current and latest.

  • You need a defensible, version-by-version upgrade plan.

Inputs Required

  1. Product and platform

  • Example: Meeting SDK Android, Video SDK iOS, Contact Center Web.

  1. Current version in production

  • Example: 6.3.1, 2.1.0.

  1. Target version

  • Usually latest stable from changelog.

  1. Critical features in use

  • Example: custom UI, raw data, recording, chat, live transcription, token flow.

Canonical Source

Workflow

1) Scope the upgrade lane

  • Confirm exact product + platform lane before collecting releases.

  • Do not mix lanes (for example, Meeting SDK Web and Meeting SDK iOS must be treated separately).

2) Locate the platform-specific RSS feed

From https://developers.zoom.us/changelog/:

  • Filter by product/platform.

  • Find the RSS link for that filtered lane.

  • Use only that feed for release collection.

If feed discovery is unclear:

  • Open the filtered changelog page and locate the RSS icon/link.

  • Confirm feed entries match the same product/platform lane.

3) Build the release ledger

Collect all releases from:

  • current_version (exclusive) up to target_version (inclusive), then latest if target is latest.

For each release entry capture:

  • Version

  • Release date

  • Release URL

  • Breaking/deprecated notes

  • Required migration actions

Sort upgrade steps in ascending version order.

4) Plan upgrade hops

Default strategy:

  • Patch/minor jumps can often be grouped.

  • Major changes should be isolated into dedicated hops.

Recommended hop pattern:

  1. current -> next safe checkpoint

  2. checkpoint -> next major boundary

  3. Repeat until latest

5) Extract required actions per hop

For each hop, classify actions under:

  • Auth/token contract changes

  • API renames/signature changes

  • Initialization/lifecycle changes

  • Event payload/callback changes

  • Build/dependency/runtime requirements

  • Feature removals/deprecations

6) Apply compatibility guards

  • Wrap renamed/deprecated calls behind adapters.

  • Keep temporary compatibility mappings for payload changes.

  • Add feature flags for behavior toggles when needed.

7) Validate each hop before continuing

Minimum validation set:

  • SDK init/auth

  • Join/start/session entry flow

  • Core media flows (audio/video/share) if applicable

  • Critical product-specific features used by customer

  • Cleanup/leave/disconnect behavior

Do not skip to next hop if the current hop is unstable.

8) Produce final upgrade package

Deliver:

  • Step-by-step upgrade matrix

  • Per-hop code/config change list

  • Deprecated-to-replacement map

  • Risks and rollback notes

  • Final target-state checklist

Output Template

## Upgrade Plan: <product/platform>

- Current: <x.y.z>
- Target: <a.b.c or latest>
- Source feed: <rss_url>

### Hop 1: <x.y.z -> x.y+1.z>
- Release notes:
  - <url>
- Breaking/deprecations:
  - <item>
- Required changes:
  - <item>
- Validation:
  - <item>

### Hop 2: <...>
...

## Deprecated -> Replacement Map
- <old> -> <new>

## Risks
- <risk>

## Rollback
- <rollback step>

Operating Rules

  • Never assume only latest release notes are sufficient.

  • Always process intermediate releases between customer version and target.

  • Prefer smallest-risk path over fastest path for production upgrades.

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