Knowledge-work-plugins build-zoom-virtual-agent
Reference skill for Zoom Virtual Agent. Use after routing to a virtual-agent workflow when implementing web embeds, Android or iOS wrapper integrations, knowledge-base sync, lifecycle handling, or troubleshooting.
install
source · Clone the upstream repo
git clone https://github.com/anthropics/knowledge-work-plugins
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/anthropics/knowledge-work-plugins "$T" && mkdir -p ~/.claude/skills && cp -r "$T/partner-built/zoom-plugin/skills/virtual-agent" ~/.claude/skills/anthropics-knowledge-work-plugins-build-zoom-virtual-agent && rm -rf "$T"
manifest:
partner-built/zoom-plugin/skills/virtual-agent/SKILL.mdsource content
/build-zoom-virtual-agent
Background reference for Zoom Virtual Agent across:
- Web campaign/chat embeds.
- Android WebView wrappers.
- iOS WKWebView wrappers.
- Knowledge-base sync and custom API ingestion.
Official docs:
- https://developers.zoom.us/docs/virtual-agent/
- https://developers.zoom.us/docs/virtual-agent/web/
- https://developers.zoom.us/docs/virtual-agent/android/
- https://developers.zoom.us/docs/virtual-agent/ios/
Routing Guardrail
- If the user is implementing Contact Center app surfaces inside Zoom client, chain with ../contact-center/SKILL.md.
- If the user needs backend knowledge-base CRUD or automation scripts, chain with ../rest-api/SKILL.md and ../oauth/SKILL.md.
- If the user asks only for website bot embed and campaign controls, stay on web/SKILL.md.
- If the user asks for mobile native wrappers around web chat, route to android/SKILL.md or ios/SKILL.md.
Quick Links
- concepts/architecture-and-lifecycle.md
- scenarios/high-level-scenarios.md
- references/versioning-and-drift.md
- references/samples-validation.md
- references/environment-variables.md
- troubleshooting/common-drift-and-breaks.md
- RUNBOOK.md
Platform skills:
Common Lifecycle Pattern
- Configure campaign or entry ID in Virtual Agent admin.
- Initialize SDK in web or WebView container.
- Wait for readiness (
orzoomCampaignSdk:ready
) before calling APIs.waitForReady() - Register bridge handlers (
,exitHandler
,commonHandler
) when native orchestration is needed.support_handoff - Handle conversation lifecycle (
,engagement_started
) and UI state.engagement_ended - End chat (
) and clean up listeners.endChat
High-Level Scenarios
- Website campaign launcher with contextual customer attributes.
- Mobile app WebView chat with native close/handoff bridge.
- External URL handling via system browser vs in-app browser policy.
- Knowledge-base sync from external systems using custom API connector.
- Cross-team support flow that escalates from bot to live support with handoff payload.
Chaining
- Contact Center app/web/mobile patterns: ../contact-center/SKILL.md
- OAuth app setup and tokens: ../oauth/SKILL.md
- API workflows for KB automation: ../rest-api/SKILL.md
- Event-driven backend follow-up: ../webhooks/SKILL.md
Operations
- RUNBOOK.md - 5-minute preflight and debugging checklist.