mcpbeat

Build Zoom Virtual Agent

anthropics/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.

6k tokens
context cost
the whole folder, loaded on every use
23
files
instructions only
0
copies elsewhere
how many repositories repackaged it
23273
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill build-zoom-virtual-agent

What comes with it

14 729 bytes besides the instruction
RUNBOOK.md
android/concepts/webview-lifecycle.md
android/examples/js-bridge-patterns.md
android/references/android-reference-map.md
android/troubleshooting/common-issues.md
concepts/architecture-and-lifecycle.md
ios/concepts/webview-lifecycle.md
ios/examples/js-bridge-patterns.md
ios/references/ios-reference-map.md
ios/troubleshooting/common-issues.md
references/environment-variables.md
references/samples-validation.md
references/versioning-and-drift.md
scenarios/high-level-scenarios.md
troubleshooting/common-drift-and-breaks.md
web/concepts/lifecycle-and-events.md
web/examples/campaign-and-entry-patterns.md
web/references/web-reference-map.md
web/troubleshooting/common-issues.md

The instruction itself

7 sections, as written by the author

/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.
  • 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:

  • web/SKILL.md
  • android/SKILL.md
  • ios/SKILL.md

Common Lifecycle Pattern

  • Configure campaign or entry ID in Virtual Agent admin.
  • Initialize SDK in web or WebView container.
  • Wait for readiness (zoomCampaignSdk:ready or waitForReady()) before calling APIs.
  • Register bridge handlers (exitHandler, commonHandler, support_handoff) when native orchestration is needed.
  • Handle conversation lifecycle (engagement_started, engagement_ended) and UI state.
  • End chat (endChat) and clean up listeners.

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.

How to use it

Copy the folder

Take anthropics/build-zoom-virtual-agent from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.