build-zoom-contact-center-app · openai — Codex skill: what it does and install
Guides development for Zoom Contact Center across web, iOS, and Android. It structures session lifecycles and context passing to external CRM tools.
npx skills add openai/plugins --skill contact-center -a codexWhat build-zoom-contact-center-app does
This skill directs implementation when targeting Zoom Contact Center instead of general meetings, team chat, or phone APIs. It guides the setup toward platform-specific references once the client channel is clear, whether web, Android, or iOS.
The workflow structures the entire interaction lifecycle: initialization, engagement start, context retrieval, state transitions, handoffs, and final cleanup. Engagement context functions as shared state that passes directly into CRM or ticketing workflows.
Contact Center SDKs differ across platforms. Event names and lifecycle hooks vary between web and mobile wrappers. Choosing the platform reference before writing code prevents drift against specific SDK versions and app configurations.
What it helps with
- Separate Zoom Contact Center logic from standard Zoom Meetings APIs
- Map the interaction lifecycle from initialization to teardown
- Route engagement context into external CRM or ticketing systems
- Resolve version drift between web, Android, and iOS SDKs
Example prompts for the agent
- Plan a Zoom Contact Center web engagement that passes customer context to our CRM
- Implement the cleanup and virtual agent handoff lifecycle in the iOS Contact Center SDK
- Check state transition event names for an Android Contact Center implementation
How to install build-zoom-contact-center-app
1Skills CLI (Vercel)
npx skills add openai/plugins --skill contact-center -a codex2Manually: put the files in place
.agents/skills/contact-center/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add openai/plugins --skill contact-center -a claude-code2Manually: put the files in place
~/.claude/skills/contact-center/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/contact-center/
Manually: put the files in place
.cursor/skills/contact-center/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install openai/plugins contact-center2Manually: put the files in place
.github/skills/contact-center/SKILL.mdPlatform CLI
gemini skills install https://github.com/openai/plugins --path plugins/zoom/skills/contact-centerManually: put the files in place
.devin/skills/contact-center/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 build-zoom-contact-center-app
How to install build-zoom-contact-center-app in Codex?
Run npx skills add openai/plugins --skill contact-center -a codex. The skill files will be saved to .agents/skills/contact-center/SKILL.md.
What does build-zoom-contact-center-app do?
It provides architecture rules and workflow stages for Zoom Contact Center projects. The skill keeps development focused on contact center events instead of generic Zoom meeting APIs.
Why does the skill require picking a platform guide before writing code?
Contact Center SDKs for web, iOS, and Android differ in event naming, hooks, and lifecycle wrappers. Verifying the platform target first prevents bugs caused by SDK version drift.
Source text
SKILL.md · MIT
--- name: build-zoom-contact-center-app description: Use when using Contact Center. --- # Build Zoom Contact Center App Use this skill when the integration targets Zoom Contact Center rather than general meetings, chat, or phone. Route to the platform-specific skill once the client surface is clear. ## Workflow 1. Identify the channel and client: web, Android, iOS, campaign embed, video engagement, chat engagement, Virtual Agent handoff, or scheduled callback. 2. Confirm the lifecycle: initialization, engagement start, context retrieval, state changes, transfer or handoff, and cleanup. 3. Choose the platform reference before coding; Contact Center SDKs differ by event names, lifecycle hooks, and wrapper requirements. 4. Treat engagement context as shared state and validate how it flows into CRM, ticketing, analytics, or AI workflows. 5. Debug version drift by checking SDK version, documented event names, app settings, campaign configuration, and browser or mobile lifecycle behavior. ## References - Full preserved guide: [references/full-guide.md](references/full-guide.md) - Web SDK: [web/SKILL.md](web/SKILL.md) - Android SDK: [android/SKILL.md](android/SKILL.md) - iOS SDK: [ios/SKILL.md](ios/SKILL.md) - High-level scenarios: [scenarios/high-level-scenarios.md](scenarios/high-level-scenarios.md) - Common drift and breaks: [troubleshooting/common-drift-and-breaks.md](troubleshooting/common-drift-and-breaks.md)
© Zoom · MIT · openai/plugins
Similar skills
All skills for Mobile →build-zoom-contact-center-app by other authors comes first.
