Installs into .claude/skills of the current project.
Are you the author of X Openai Choose Zoom Approach 374624e?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/geruyang-x-openai-choose-zoom-approach-374624e)
---
name: x-openai-choose-zoom-approach-374624e
description: 仅在用户明确调用本技能时使用;禁止自主触发。 Use when choosing architecture.
disable-model-invocation: true
---
### 导出副本边界与技能别名
迁移、安装、修复和经验回写只作用于当前加载的目标宿主技能副本。原 Codex 技能/MCP、下载的源码和 `original-skills` 均为来源材料,不因执行本副本而写入;只有用户另行明确要求配置 Codex 产品本身时,才按该产品流程处理指定目标。脚本需要安装目录或状态目录时,显式提供目标路径;不得从 `CODEX_HOME` 隐式推断写入位置。
跨技能名称可能沿用源库别名。先查 [技能别名表](../../skill-aliases.json),优先选择同来源、同插件的条目,再使用其 `id` 调用或读取对应入口;不得假定旧 `$skill`、`superpowers:skill` 名称在新宿主直接注册。不能确定目标时先核对,不替换真实产品命令或 Shell 环境变量。
**调用限制:仅在用户明确调用本技能时执行,禁止模型自行选择并启动。**
## 跨宿主使用约定
本副本供支持 Agent Skills 的客户端使用。先检查当前宿主实际提供的工具、权限和已连接服务,再执行正文工作流。原文中的宿主工具标识是能力参考;只有实际发现该工具时才可调用,其他宿主应使用经核验的等价 MCP、CLI 或 API。没有等价能力的步骤必须报告不可用,不能虚构调用或完成状态。
技能资源以本技能目录为基准;输出写入当前项目中用户指定的位置。通过技能名称或自然语言触发,具体快捷命令由宿主决定。涉及真实产品、模型 API、协议字段和官方网址的名称保持原意。授权、审批、隐私和工具范围限制在迁移后仍然有效;不得为兼容而扩大权限。具体依赖与迁移说明见同目录 `PORTABILITY.md`。
# Choose Zoom Approach
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](../x-openai-build-zoom-rest-api-app-fa8ade3/SKILL.md) |
| Event delivery to your backend | [webhooks](../x-openai-setup-zoom-webhooks-e8837c7/SKILL.md) or [websockets](../x-openai-setup-zoom-websockets-c8c09ef/SKILL.md) |
| Embed Zoom meetings into your app | [meeting-sdk](../x-openai-build-zoom-meeting-sdk-app-f579820/SKILL.md) |
| Build a fully custom video experience | [video-sdk](../x-openai-build-zoom-video-sdk-app-93497e9/SKILL.md) |
| Build inside the Zoom client | [zoom-apps-sdk](../x-openai-zoom-apps-sdk-0178e47/SKILL.md) |
| Real-time media extraction or meeting bots | [rtms](../x-openai-zoom-rtms-ae86f57/SKILL.md) plus [meeting-sdk](../x-openai-build-zoom-meeting-sdk-app-f579820/SKILL.md) when needed |
| Phone workflows | [phone](../x-openai-build-zoom-phone-integration-e2a7e6c/SKILL.md) |
| Contact Center or Virtual Agent flows | [contact-center](../x-openai-build-zoom-contact-center-app-20fb7cf/SKILL.md) or [virtual-agent](../x-openai-build-zoom-virtual-agent-6f67c33/SKILL.md) |
## 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