zoom-rtms · openai — Codex skill: Zoom streams and installation
This skill guides Zoom RTMS integrations, from WebSocket lifecycle design to media handling. Use it when working with meeting streams or contact-center voice media.
npx skills add openai/plugins --skill rtms -a codexWhat zoom-rtms does
The skill lays out an RTMS workflow: identify the stream source, then decide whether RTMS is enough or a Meeting SDK bot is needed. It covers the WebSocket lifecycle, including event subscriptions, connection checks, media start, heartbeat, reconnects, and shutdown.
Audio, video, screen share, chat, live transcripts, and metadata have different payload and timing needs. The skill also covers downstream pipelines for buffering, transcription, AI analysis, and recording. For debugging, it separates app setup, event delivery, stream authorization, network connectivity, and media decoding.
A bot that needs a visible participant identity, meeting controls, or UI-visible behavior calls for considering the Meeting SDK; RTMS alone does not meet that need.
What it helps with
- choose an RTMS source for a meeting or contact-center stream
- design a WebSocket lifecycle for media delivery
- handle audio, video, chat, and metadata according to their payload needs
- plan a stream pipeline for transcription or AI analysis
- trace failures across event delivery and media decoding
Example prompts for the agent
- Plan a Zoom RTMS integration that receives meeting audio, and outline its WebSocket connection steps.
- Compare RTMS with the Meeting SDK for a bot that needs a visible identity and meeting controls.
- Explain how to process an RTMS video stream and live transcript, including reconnect and shutdown.
How to install zoom-rtms
1Skills CLI (Vercel)
npx skills add openai/plugins --skill rtms -a codex2Manually: put the files in place
.agents/skills/rtms/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add openai/plugins --skill rtms -a claude-code2Manually: put the files in place
~/.claude/skills/rtms/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/rtms/
Manually: put the files in place
.cursor/skills/rtms/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install openai/plugins rtms2Manually: put the files in place
.github/skills/rtms/SKILL.mdPlatform CLI
gemini skills install https://github.com/openai/plugins --path plugins/zoom/skills/rtmsManually: put the files in place
.devin/skills/rtms/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-rtms
How do I install zoom-rtms in Codex?
Run npx skills add openai/plugins --skill rtms -a codex. The skill file is at .agents/skills/rtms/SKILL.md.
What does zoom-rtms do?
It guides the design of Zoom RTMS integrations, including WebSocket setup, media handling, and stream troubleshooting.
Can zoom-rtms help build a bot visible to meeting participants?
If the bot needs a visible identity, meeting controls, or UI-visible behavior, the skill says to consider the Meeting SDK rather than relying on RTMS alone.
Source text
SKILL.md · MIT
--- name: zoom-rtms description: Use when using RTMS. --- # Zoom Realtime Media Streams Use this skill when the integration needs real-time meeting or contact-center media as a backend stream. If the workflow needs a visible participant bot, compare against `build-zoom-bot` and `zoom-meeting-sdk-linux` before choosing RTMS. ## Workflow 1. Confirm the source surface: Meetings RTMS, Contact Center voice media, or another documented RTMS stream. 2. Decide whether RTMS is sufficient or whether a Meeting SDK bot is required for participant identity, meeting controls, or UI-visible behavior. 3. Implement the WebSocket lifecycle first: event subscription, connection validation, media start, heartbeat, reconnect, and shutdown. 4. Process media types intentionally: audio, video, screen share, chat, live transcript, and metadata have different payload and timing constraints. 5. Design downstream pipelines for buffering, transcription, AI analysis, recording, or tool invocation. 6. Debug by isolating app setup, webhook/event delivery, stream authorization, network connectivity, and media payload decoding. ## References - Full preserved guide: [references/full-guide.md](references/full-guide.md) - Connection architecture: [concepts/connection-architecture.md](concepts/connection-architecture.md) - Lifecycle flow: [concepts/lifecycle-flow.md](concepts/lifecycle-flow.md) - Media types: [references/media-types.md](references/media-types.md) - Data types: [references/data-types.md](references/data-types.md) - RTMS bot example: [examples/rtms-bot.md](examples/rtms-bot.md) - Common issues: [troubleshooting/common-issues.md](troubleshooting/common-issues.md)
© Zoom · MIT · openai/plugins
Similar skills
SKILL.md skills catalog →zoom-rtms by other authors comes first.