build-zoom-video-sdk-app — Codex command: what it does, how to install
Configures a custom Zoom Video SDK session flow with backend auth tokens and local verification instead of the standard Zoom meeting UI.
~/.codex/prompts/build-zoom-video-sdk-app.mdWhat build-zoom-video-sdk-app does
This command sets up custom video experiences rather than standard Zoom meetings. First, the agent inspects the repository for client stacks, existing video code, and authentication helpers without exposing secrets. It then outlines the files to edit, the session lifecycle plan, and how to verify everything locally.
The implementation focuses on initializing the Video SDK, joining sessions, and writing the backend endpoint that mints auth tokens. The first pass stays minimal, avoiding extra media controls until the base pipeline works.
Video SDK logic should never mix with Meeting SDK assumptions. If your project needs actual Zoom meetings, switch to /build-zoom-meeting-app.
What it helps with
- implement custom Zoom Video SDK sessions without the standard meeting UI
- set up backend auth token generation for video sessions
- verify client join flows and session lifecycle locally
- separate Video SDK implementation from Meeting SDK assumptions
Example prompts for the agent
- Run
/build-zoom-video-sdk-appto scaffold a custom video session and backend auth - Use
/build-zoom-video-sdk-appto set up token minting and join handling for Video SDK - Execute
/build-zoom-video-sdk-appto plan and verify our custom video workflow
How to install build-zoom-video-sdk-app
Manually: put the files in place
~/.codex/prompts/build-zoom-video-sdk-app.mdCall it with /prompts:build-zoom-video-sdk-app. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.claude/commands/build-zoom-video-sdk-app.mdCall it with /build-zoom-video-sdk-app. For all projects use ~/.claude/commands/
Manually: put the files in place
.github/prompts/build-zoom-video-sdk-app.prompt.mdManually: put the files in place
.gemini/commands/build-zoom-video-sdk-app.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about build-zoom-video-sdk-app
How do I install build-zoom-video-sdk-app in Codex?
Save the prompt file to ~/.codex/prompts/build-zoom-video-sdk-app.md.
What does build-zoom-video-sdk-app do?
It inspects your project, plans the custom session flow, and sets up Video SDK initialization alongside backend token minting.
Can I use this command to join standard Zoom meetings?
No, this command is built specifically for custom Video SDK sessions. Use /build-zoom-meeting-app if you need standard Zoom meetings.
Source text
build-zoom-video-sdk-app.md · MIT
--- description: Implement a custom Zoom Video SDK session workflow with the right auth, session lifecycle, and verification path. --- # Build Zoom Video SDK App Use this command when the repo needs a custom video experience rather than an actual Zoom meeting UI. ## Preflight 1. Inspect the codebase for existing video session code, frontend stack, backend support, and auth helpers. 2. Confirm the use case is a custom session workflow and not a standard Zoom meeting flow. 3. Identify the target platform and expected media features. 4. Check whether the required server-side auth or session token path already exists without printing secrets. ## Plan Before making changes: - state the target platform and custom session goal - list the files that will be changed - state the auth path, session lifecycle responsibilities, and media features in scope - state how the implementation will be verified locally ## Commands 1. Add or correct Video SDK initialization, session join flow, auth handling, and lifecycle management. 2. Keep the implementation aligned with the platform’s existing architecture. 3. Limit the first pass to the minimum working session path unless the user explicitly asks for broader UI or media controls. 4. Add or update the supporting server code needed to mint the correct auth material. 5. Avoid mixing Meeting SDK assumptions into Video SDK code. ## Verification 1. Re-read the client and server files that changed. 2. Run the relevant local build or tests. 3. Verify the session auth shape and the basic connect flow. 4. State any remaining blocker such as missing credentials, unsupported environment, or unresolved media prerequisites. ## Summary ```text ## Result - Action: implemented or updated a Zoom Video SDK workflow - Status: success | partial | failed - Details: platform, files changed, auth path, verification run ``` ## Next Steps - Test the session with real participants or a controlled local environment. - Add advanced media features only after the base session path works. - If the requirement is actually to join real Zoom meetings, switch to `/build-zoom-meeting-app`.
© Zoom · MIT · openai/plugins