Ciying AI Directory
AI DirectorySkills
中文
Ciying AI Directory

Choose Zoom Approach in Codex: Meeting SDK or Video SDK?

Decide which Zoom SDK fits a product requirement before adding dependencies. Distinguish a regular Zoom meeting embedded in a site from a custom video session.

中文

Setup for Codex (Zoom plugin)

Codex with the Zoom plugin. A planning exercise can use a fictional requirement without connecting live meeting data. Use the full curated plugin for bundled references.

  1. Open /plugins in Codex and install Zoom when available in your marketplace.
  2. Start a project session and explicitly select $choose-zoom-approach from the Zoom skills.
  3. State where participants join, which existing meeting features matter, and how much of the interface your app needs to control.

Example task

Use $choose-zoom-approach to choose an SDK for a fictional museum workshop. Existing instructors already schedule ordinary Zoom meetings. Visitors should join those same meetings without leaving the museum website. Give a primary SDK, one prerequisite to confirm, and a small prototype goal.

Expected result

The recommendation selects Meeting SDK because visitors join existing Zoom meetings. It proposes a test of one join flow in a development project and identifies which meeting access or host assumptions need confirmation.

Upstream documentation

Original SKILL.md on GitHub · MIT license · Source reviewed

Frequently asked question

When does a fully custom video product call for Video SDK?

Choose Video SDK when your product owns the session experience, interface, and its own session identifiers. Use Meeting SDK for an embedded version of a regular Zoom meeting when you need Zoom’s existing meeting semantics.