Choose Zoom Approach

From the author

Use when choosing architecture.

— the description by Zoom

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a structured decision framework to help developers choose the most efficient Zoom integration approach. It emphasizes selecting the smallest necessary surface area to minimize complexity, guiding users toward the correct SDK or API based on specific problem types such as backend automation, custom video experiences, or in-client applications.

What it does

Maps common development problem types to specific Zoom integration surfaces.
Provides a hierarchy for selecting the smallest correct integration path.
Outlines guardrails to prevent common architectural misalignments.
Defines the required output format for architectural recommendations.

When to use it

When starting a new project that requires Zoom integration.
When evaluating which Zoom SDK or API is best suited for a specific feature.
When you need to ensure your integration architecture remains minimal and efficient.

Advantages

Reduces architectural bloat by encouraging minimal surface area usage.
Prevents common pitfalls like choosing the Video SDK for meeting-based features.
Standardizes the decision-making process for Zoom-related development.

Usage examples

“I need to build a custom video experience that does not use standard Zoom meeting UI. Which approach should I take?”: The agent will recommend the Video SDK, explaining that it is designed for fully custom video experiences rather than standard meeting semantics.
“We need to automate account management and reporting tasks. What is the best way to handle this?”: The agent will recommend using the REST API, as it is the primary surface for deterministic backend automation and reporting.

Install

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

Unzip it into the cross-client skills folder of your project:

mkdir -p .agents/skills && unzip choose-zoom-approach.zip -d .agents/skills

Documentation by Zoom

Pick the smallest correct Zoom surface for the job, then layer in only the supporting pieces that are actually required.

Decision Framework

Problem Type	Primary Zoom Surface
Deterministic backend automation, account management, reporting, scheduled jobs	rest-api
Event delivery to your backend	webhooks or websockets
Embed Zoom meetings into your app	meeting-sdk
Build a fully custom video experience	video-sdk
Build inside the Zoom client	zoom-apps-sdk
Real-time media extraction or meeting bots	rtms plus meeting-sdk when needed
Phone workflows	phone
Contact Center or Virtual Agent flows	contact-center or virtual-agent

Guardrails

Do not recommend Video SDK when the user actually needs Zoom meeting semantics.
Do not recommend Meeting SDK when the user needs a fully custom session product.
Keep deterministic backend automation in REST APIs and event-driven code.

What To Produce

One recommended path
Minimum supporting components
Hard constraints and tradeoffs
Immediate next implementation step

Files

ATTRIBUTION.mdAdded by AutoGineer887 B
LICENSELicence file added by AutoGineer1.1 KiB
SKILL.md1.4 KiB
agents/openai.yaml144 B

agents/openai.yaml

interface:
  display_name: Choose Zoom Approach
  short_description: Use when choosing architecture.
policy:
  allow_implicit_invocation: false

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

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Setup TS Deep Modules
Matt Pocock· Community
Configures dependency-cruiser to enforce deep module boundaries in TypeScript repositories.
Software developmentClaude CodeClaude appsOpenAI Codex+14 more
MITLow riskHas scriptsGitHub stars of the source repository317.5k
To Spec
Matt Pocock· Community
Synthesizes conversation context into a structured technical specification and publishes it to a project issue tracker.
Software developmentClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository317.5k
Improve Codebase Architecture
Matt Pocock· Community
A systematic process to identify, visualize, and refine architectural deepening opportunities in a codebase.
Software developmentClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository317.5k
Domain Modeling
Matt Pocock· Community
An expert assistant for defining project terminology, maintaining a glossary, and documenting architectural decisions.
Software developmentClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository317.5k
Codebase Design
Matt Pocock· Community
A shared vocabulary and set of principles for designing deep, testable, and maintainable software modules.
Software developmentClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository317.5k
Prototype
Matt Pocock· Community
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
Software developmentClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository317.5k