build-zoom-meeting-sdk-app — Codex command: setup and install
Guides the assistant through integrating the Zoom Meeting SDK, setting up backend auth signatures, client join flows, and verification without logging credentials.
~/.codex/prompts/build-zoom-meeting-sdk-app.mdWhat build-zoom-meeting-sdk-app does
This command guides an agent to integrate the Zoom Meeting SDK into an application. The preflight check confirms the project requires a real Zoom meeting rather than an in-client Zoom app or custom video session. Target platforms include web, mobile, Electron, React Native, Unreal, and Linux bots.
The plan implements a minimal join or start flow alongside the required backend auth path. Generic wrappers cause maintenance friction: the instructions keep platform-specific SDK behaviors explicit. Credentials, passwords, and signature material must never appear in logs or terminal output.
Verification runs locally against the updated client and backend code. Advanced meeting controls wait until base connectivity works.
What it helps with
- embed Zoom meeting join or start flows via the Meeting SDK
- implement backend signature generation and auth handling
- initialize the SDK across web, mobile, or desktop clients
- verify join parameters before building advanced meeting controls
Example prompts for the agent
- Integrate the Zoom Meeting SDK into this Electron client with a backend auth path
- Configure Zoom meeting start flow for React Native without leaking secrets
- /build-zoom-meeting-sdk-app for the web client join flow
How to install build-zoom-meeting-sdk-app
Manually: put the files in place
~/.codex/prompts/build-zoom-meeting-sdk-app.mdCall it with /prompts:build-zoom-meeting-sdk-app. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.claude/commands/build-zoom-meeting-sdk-app.mdCall it with /build-zoom-meeting-sdk-app. For all projects use ~/.claude/commands/
Manually: put the files in place
.github/prompts/build-zoom-meeting-sdk-app.prompt.mdManually: put the files in place
.gemini/commands/build-zoom-meeting-sdk-app.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about build-zoom-meeting-sdk-app
How do I install build-zoom-meeting-sdk-app in Codex?
Save the prompt file to ~/.codex/prompts/build-zoom-meeting-sdk-app.md.
What does build-zoom-meeting-sdk-app do?
It provides a step-by-step workflow to inspect the repo, configure backend auth, initialize the Meeting SDK on the client, and verify join calls.
What if the project needs custom video sessions instead?
Switch to /build-zoom-video-sdk-app. This command is designed strictly for joining or starting real Zoom meetings through the Meeting SDK.
Source text
build-zoom-meeting-sdk-app.md · MIT
--- description: Implement a Zoom Meeting SDK integration with the right platform-specific join or start flow, auth path, and verification loop. --- # Build Zoom Meeting SDK App Use this command when the repo needs to join, start, or embed real Zoom meetings through the Meeting SDK rather than a broader meeting workflow. ## Preflight 1. Inspect the codebase for existing Meeting SDK usage, target platform code, backend signature helpers, and meeting join UI. 2. Confirm the requirement is a real Zoom meeting and not a custom video session or an in-client Zoom app. 3. Identify the target platform: web, Android, iOS, macOS, Windows, Electron, React Native, Unreal, or Linux bot. 4. Check whether the required auth and meeting inputs exist without printing secrets: meeting number, password path, role, SDK auth material, and host start requirements. ## Plan Before making changes: - state the target Meeting SDK platform and user flow - list the files that will be changed - state the auth path, join or start flow, and any required backend pieces - state how the implementation will be verified locally ## Commands 1. Add or correct Meeting SDK initialization at the appropriate client layer for the target platform. 2. Implement the smallest working join or start flow before adding advanced meeting controls or raw data features. 3. Add or correct the backend auth path needed for the chosen platform. 4. Keep platform-specific behavior explicit instead of forcing a generic abstraction over materially different SDKs. 5. Avoid leaking meeting credentials, signatures, or tokens in logs or command output. ## Verification 1. Re-read the client Meeting SDK code and supporting backend auth code after changes. 2. Run the relevant local build or tests where available. 3. Verify the join or start call shape, auth path, and expected meeting inputs. 4. State any remaining blocker such as missing credentials, waiting room constraints, unsupported environment, or platform setup gaps. ## Summary ```text ## Result - Action: implemented or updated a Zoom Meeting SDK integration - Status: success | partial | failed - Details: platform, files changed, auth path, verification run ``` ## Next Steps - Test the flow with a real meeting on the target platform. - Add meeting controls or bot-like behavior only after the base join path works. - If the requirement changes to a custom session product, switch to `/build-zoom-video-sdk-app`.
© Zoom · MIT · openai/plugins