zoom-general · openai — Codex skill: what it does, how to install
Helps choose the right Zoom tool for your project and verifies the authentication model across APIs and SDKs before implementation.
npx skills add openai/plugins --skill general -a codexWhat zoom-general does
This skill provides cross-product platform context for Zoom once you define your integration goal. It classifies projects by expected outcome: embedding meetings, building custom video interfaces, automating resources, consuming events, processing media, or publishing to the Zoom Marketplace.
Once the goal is clear, it maps requirements to specific Zoom surfaces. Supported components include the REST API, webhooks, WebSockets, Meeting SDK, Video SDK, Zoom Apps SDK, Phone, Contact Center, Virtual Agent, Scribe, Rivet, and Cobrowse. The workflow verifies authentication models early, separating user-level OAuth, account-level OAuth, and SDK signatures before implementation begins.
For early routing, the documentation suggests using start, plan-zoom-product, or plan-zoom-integration instead. Running zoom-general is intended specifically for tasks that cross product boundaries or require detailed comparison tables.
What it helps with
- compare capabilities of Meeting SDK and Video SDK for video features
- choose between user-level OAuth and account-level OAuth models
- select the appropriate Zoom surface for webhook consumption or automation
- prepare technical structure for publishing on Zoom Marketplace
Example prompts for the agent
- Compare Meeting SDK and Video SDK capabilities for my custom video app
- Which authorization model and scopes are required for the Zoom REST API?
- Help me pick the right Zoom surface to consume webhooks and process media
How to install zoom-general
1Skills CLI (Vercel)
npx skills add openai/plugins --skill general -a codex2Manually: put the files in place
.agents/skills/general/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add openai/plugins --skill general -a claude-code2Manually: put the files in place
~/.claude/skills/general/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/general/
Manually: put the files in place
.cursor/skills/general/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install openai/plugins general2Manually: put the files in place
.github/skills/general/SKILL.mdPlatform CLI
gemini skills install https://github.com/openai/plugins --path plugins/zoom/skills/generalManually: put the files in place
.devin/skills/general/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: Codex skills: how to install, where they live, how to call them
Questions about zoom-general
How do I install zoom-general in Codex?
Run npx skills add openai/plugins --skill general -a codex in your terminal.
What does zoom-general do?
It maps project goals to suitable Zoom surfaces, such as the REST API or SDKs, and confirms required authentication scopes before coding.
When should I choose zoom-general over other Zoom skills?
First-step task routing relies on start, plan-zoom-product, or plan-zoom-integration. Reach for zoom-general only when your work spans multiple Zoom surfaces or requires comparative feature tables.
Source text
SKILL.md · MIT
--- name: zoom-general description: Use when comparing products. --- # 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 - Full preserved guide: [references/full-guide.md](references/full-guide.md) - App types: [references/app-types.md](references/app-types.md) - Authentication: [references/authentication.md](references/authentication.md) - Scopes: [references/scopes.md](references/scopes.md) - Marketplace: [references/marketplace.md](references/marketplace.md) - Query routing playbook: [references/query-routing-playbook.md](references/query-routing-playbook.md)
© Zoom · MIT · openai/plugins
Similar skills
All skills for Agent setup: memory, context, orchestration →zoom-general by other authors comes first.
