$ loading_
Build and troubleshoot Zoom Contact Center integrations, state handling, and callbacks.
The materials indicate this is an open-source, prompt-only reference skill with no declared secrets, remote endpoints, or local execution capabilities, so overall risk is low. Caution is only needed because real integrations with Zoom Contact Center SDKs/APIs would introduce permissions and data flows at implementation time and should be assessed separately.
The materials explicitly state there are no required secrets or environment variables. This skill appears to be reference documentation and does not itself request or handle credentials, though it mentions downstream integration scenarios that may use an API key.
No remote endpoints are declared, and the system flags it as prompt-only. Based on the provided materials, the skill itself does not make network requests or exfiltrate user data; the README only contains static links to official Zoom documentation.
As a prompt-only/documentation skill, the materials show no ability to spawn local processes, run scripts, or access system capabilities. No install commands, executables, or tool-invocation behaviors are described.
The materials do not declare access to local files, databases, clipboard, or other user resources. Its stated role is integration guidance and routing, not operational data access.
The source is an open-source GitHub repository, which is a positive and lowers risk because the contents are auditable. However, the license is not declared, community adoption is 0 stars, and maintenance status is unknown, so supply-chain confidence is limited and warrants some caution.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "build-zoom-contact-center-app" skill from askskill: 1. Download https://raw.githubusercontent.com/anthropics/knowledge-work-plugins/main/partner-built/zoom-plugin/skills/contact-center/SKILL.md 2. Save it as ~/.claude/skills/contact-center/SKILL.md 3. Reload skills and tell me it's ready
Design a web integration for Zoom Contact Center: after a user enters a support workflow, the frontend must receive routing results, store engagement context, synchronize session state, and update the UI on transfer or completion. Output the architecture, key event flow, and frontend state management recommendations.
An integration plan with system architecture, event flow, and state management guidance.
I am building a native app integration with Zoom Contact Center and need to support outbound campaigns and customer callbacks. Provide implementation steps, key API interactions, edge-case handling, and how to keep callback state consistent with the agent UI.
A callback and campaign implementation guide covering flow, APIs, and error handling.
After an upgrade, our Zoom Contact Center integration shows state desynchronization and changed event fields. Help me create a version-drift troubleshooting checklist, including compatibility checks, log inspection methods, regression test recommendations, and ways to reduce future upgrade risk.
A version-drift troubleshooting and remediation checklist to speed diagnosis and reduce upgrade risk.
Background reference for Zoom Contact Center integrations across app, web, and native mobile surfaces.
Implementation guidance for Zoom Contact Center across:
Official docs:
zoom-apps-sdk.Start here:
Platform skills:
contact-center/
├── SKILL.md
├── RUNBOOK.md
├── concepts/
│ └── architecture-and-lifecycle.md
├── scenarios/
│ └── high-level-scenarios.md
├── references/
│ ├── versioning-and-compatibility.md
│ ├── samples-validation.md
│ └── environment-variables.md
├── troubleshooting/
│ └── common-drift-and-breaks.md
├── android/
│ ├── SKILL.md
│ ├── concepts/sdk-lifecycle.md
│ ├── examples/service-patterns.md
│ ├── references/android-reference-map.md
│ └── troubleshooting/common-issues.md
├── ios/
│ ├── SKILL.md
│ ├── concepts/sdk-lifecycle.md
│ ├── examples/service-patterns.md
│ ├── references/ios-reference-map.md
│ └── troubleshooting/common-issues.md
└── web/
├── SKILL.md
├── concepts/lifecycle-and-events.md
├── examples/app-context-and-state.md
├── references/web-reference-map.md
└── troubleshooting/common-issues.md
entryId for chat/video/ZVA, apiKey for scheduled callback and campaign flows).fetchUI, startVideo, or web SDK open/show path).start, hold, resume, end) and context switching.endChat/endVideo, logout/logoff, uninitialize/release).engagementId and survives context switching.See scenarios/high-level-scenarios.md for details.
…
Helps developers implement auth, webhooks, API wrappers, and modular Rivet integrations.
Build weighted sales forecasts with scenario planning, commit splits, and gap analysis.
Embed Zoom meeting features into web apps with full or component-based integration.
Track hiring stages, update candidate status, and monitor pipeline counts.
Prepare compliant month-end journal entries with debits, credits, and support.
Run preflight diagnostics for browser, media permissions, and network readiness.
Build Zoom Phone integrations, call workflows, and telephony automation features.
Embed contact center chat, video, and event workflows into web apps.
Build custom video session apps with full control using Zoom Video SDK
Implement Zoom Meeting SDK joins, auth flows, and platform-specific integrations.
Build Zoom Team Chat integrations, bots, and interactive messaging experiences.
Integrate Zoom Contact Center features into native iOS apps with chat and callbacks.