anthropics/knowledge-work-plugins

build-zoom-contact-center-app

Reference skill for Zoom Contact Center.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill build-zoom-contact-center-app

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

/build-zoom-contact-center-app

Background reference for Zoom Contact Center integrations across app, web, and native mobile surfaces.

Implementation guidance for Zoom Contact Center across:

  • Contact Center apps in the Zoom client (Zoom Apps SDK path)
  • Web channel embeds (chat/video/campaign)
  • Native mobile SDKs (Android/iOS)

Official docs:

  • https://developers.zoom.us/docs/contact-center/
  • https://developers.zoom.us/docs/contact-center/web/sdk-reference/
  • https://marketplacefront.zoom.us/sdk/contact/android/index.html
  • https://marketplacefront.zoom.us/sdk/contact/ios/index.html

Routing Guardrail

  • If the user is building an app inside the Zoom Contact Center desktop client, stay on the Zoom Apps SDK path and use this skill plus zoom-apps-sdk.
  • If the user is embedding chat/video widgets on a website, route to web/SKILL.md.
  • If the user is integrating native Android or iOS SDK binaries, route to android/SKILL.md or ios/SKILL.md.
  • If the user needs Contact Center call-control or queue APIs, chain with ../rest-api/SKILL.md.

Quick Links

Start here:

  1. concepts/architecture-and-lifecycle.md
  2. scenarios/high-level-scenarios.md
  3. references/forum-top-questions.md
  4. references/versioning-and-compatibility.md
  5. references/samples-validation.md
  6. references/environment-variables.md
  7. troubleshooting/common-drift-and-breaks.md
  8. RUNBOOK.md

Platform skills:

Documentation Structure

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

Common Lifecycle Pattern

  1. Initialize platform context early.
  2. Build a channel item (entryId for chat/video/ZVA, apiKey for scheduled callback and campaign flows).
  3. Get service/client instance.
  4. Register listeners/delegates before user interaction.
  5. Start flow (fetchUI, startVideo, or web SDK open/show path).
  6. Handle engagement state changes (start, hold, resume, end) and context switching.
  7. End flow and release resources (endChat/endVideo, logout/logoff, uninitialize/release).

High-Level Scenarios

  • Agent side-panel app that stores notes per engagementId and survives context switching.
  • Browser chat/video campaigns launched from web tags.
  • Native mobile customer app for chat/video/scheduled callback.
  • Campaign-driven channel selection (chat, ZVA, video, scheduled callback).
  • Rejoin flow for dropped video engagements on mobile.
  • Smart Embed CRM softphone with postMessage event contracts.

See scenarios/high-level-scenarios.md for details.

Chaining

Environment Variables

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
anthropics
公式

contract-review

Lightweight NDA, MSA, and vendor contract review for SMBs without legal on staff. Reads contracts from local files, mail attachments (Gmail or M365), a connected file store (Google Drive or M365), or DocuSign envelopes; flags non-standard terms; explains risks in plain English; and outputs a marked-up redline as a separate DOCX. Use when the user says "review this contract," "what am I signing," "red flags," "flag any concerns," "check the payment terms," or uploads/forwards a contract or legal

1時間の導入数
2
GitHub Stars
3.7万
更新日
11月21日
anthropics
公式

process-doc

Document a business process — flowcharts, RACI, and SOPs. Use when formalizing a process that lives in someone's head, building a RACI to clarify who owns what, writing an SOP for a handoff or audit, or capturing the exceptions and edge cases of how work actually gets done.

1時間の導入数
1
GitHub Stars
3.7万
更新日
11月20日
anthropics
公式

data-visualization

Create effective data visualizations with Python (matplotlib, seaborn, plotly). Use when building charts, choosing the right chart type for a dataset, creating publication-quality figures, or applying design principles like accessibility and color theory.

1時間の導入数
5
GitHub Stars
3.7万
更新日
11月20日
anthropics
公式

accessibility-review

Run a WCAG 2.1 AA accessibility audit on a design or page. Trigger with "audit accessibility", "check a11y", "is this accessible?", or when reviewing a design for color contrast, keyboard navigation, touch target size, or screen reader behavior before handoff.

1時間の導入数
4
GitHub Stars
3.7万
更新日
11月20日