$ ~/registry/skill/anthropics-partner-built-zoom-plugin-skills-websockets

SKILL

setup-zoom-websockets

Name: setup-zoom-websockets
Author: anthropics

帮助开发者为 Zoom 事件流配置 WebSockets 低延迟持久连接方案。

星标

★ 22,528

来源

GitHub

更新于

2026-07-11

// 安全评估需留意

仅提示词，不执行代码
开源可审计

总评

该技能材料显示为开源的参考型提示/文档，系统检查也标记为 prompt-only；未见其自身要求执行代码、访问本地数据或向第三方外发数据。README 提到的 Zoom OAuth/WebSocket 仅属背景说明，但涉及敏感凭证与外部连接，使用时仍应按最小权限管理。

凭证密钥需留意

元数据写明该技能本身“无”必需密钥，但 README 明确涉及 Zoom Server-to-Server OAuth 的 Account ID、Client ID、Client Secret 与 access token；这些属于高敏感凭证。由于当前是参考文档而非可执行集成，未见技能自身收集或传输凭证的证据，但若按文档落地，需防止凭证暴露在代码、日志或 URL 中。

网络外发需留意

系统标注远程端点为“无”，说明该技能自身不声明联网；但 README 示例提到连接 Zoom OAuth 端点 `https://zoom.us/oauth/token` 以及 `wss://ws.zoom.us/ws`。这些属于与声明功能相关的已知 Zoom 端点，材料未显示向不明或无关第三方外发数据，因此为常规联网留意项而非高风险。

代码执行低风险

客观检查项为 prompt-only，当前材料表现为参考说明与示例代码片段，没有证据表明该技能自身会在本机启动进程、执行脚本或申请额外系统权限。

数据访问低风险

未见该技能声明读取/写入本地文件、数据库、剪贴板或其他用户资源；材料主要是概念说明与配置步骤。若用户自行实现 README 中示例，数据访问范围将取决于其自建代码，而非该技能本身。

来源供应链低风险

来源为 GitHub 上的开源仓库，具备可审计性，这是明显的降风险因素。虽然仓库 star 为 0、许可证未声明、维护状态未知，可信度不算强，但在未见闭源外发、恶意安装脚本或可疑注入迹象的情况下，整体仍偏低风险。

安全建议

若据此实现 Zoom WebSocket 集成，将 Client Secret 和 access token 存放在安全密钥管理中，不要硬编码或写入日志。
避免把 access token 放入可持久记录的 URL、监控或错误追踪系统；必要时做脱敏处理。
优先核对仓库最近提交、维护者身份与 README 对应代码位置，再将其作为生产参考。
仅向 Zoom 官方端点联网，并为 OAuth 应用和订阅事件配置最小必要权限。

审计模型: gpt-5.4 · 2026-06-17

// 安装

复制安装指令，让 AI 自动完成配置 · 推荐新手

请帮我安装 askskill 上的 "setup-zoom-websockets" 技能：
1. 下载 https://raw.githubusercontent.com/anthropics/knowledge-work-plugins/main/partner-built/zoom-plugin/skills/websockets/SKILL.md
2. 保存为 ~/.claude/skills/websockets/SKILL.md
3. 装好后重载技能，告诉我可以用了

// 下载

下载 SKILL.md机读安装清单 ↗

// 用法示例

配置实时事件连接

输入

请说明如何为 Zoom WebSockets 搭建实时事件连接方案，包括连接建立、认证方式、断线重连和事件处理的实现步骤。

预期产出

一份分步骤的接入指南，说明如何建立并维护 Zoom WebSockets 实时连接。

比较 WebSockets 与 Webhooks

输入

请比较 Zoom WebSockets 和 Webhooks 的适用场景，重点说明在低延迟、持久连接和安全限制下为什么应优先选择 WebSockets。

预期产出

一份场景对比与选型建议，帮助判断何时应使用 Zoom WebSockets。

设计安全连接策略

输入

请为 Zoom WebSockets 设计一套安全连接策略，涵盖认证、密钥管理、访问控制、异常监控和重试机制。

预期产出

一份面向生产环境的安全与稳定性方案，适合实时事件系统实施。

// 文档

/setup-zoom-websockets

Background reference for persistent Zoom event streams. Prefer workflow routing first, then use this file when WebSockets are plausibly better than webhooks.

WebSockets vs Webhooks

Aspect	WebSockets	Webhooks
Connection	Persistent, bidirectional	One-time HTTP POST
Latency	Lower (no HTTP overhead)	Higher (new connection per event)
Security	Direct connection, no exposed endpoint	Requires endpoint validation, IP whitelisting
Model	Pull (you connect to Zoom)	Push (Zoom connects to you)
State	Stateful (maintains connection)	Stateless (each event independent)
Setup	More complex (access token, connection)	Simpler (just endpoint URL)

Choose WebSockets when:

Real-time, low-latency updates are critical
Security is paramount (banking, healthcare, finance)
You don't want to expose a public endpoint
You need bidirectional communication

Choose Webhooks when:

Simpler setup is preferred
Small number of event notifications
Existing HTTP infrastructure

Prerequisites

Server-to-Server OAuth app in Zoom Marketplace
Account ID, Client ID, and Client Secret
WebSocket subscription with events enabled

Need help with S2S OAuth? See the zoom-oauth skill for complete authentication flows.

Start troubleshooting fast: Use the 5-Minute Runbook before deep debugging.

Quick Start

1. Create Server-to-Server OAuth App

Go to Zoom Marketplace
Create a Server-to-Server OAuth app
Copy Account ID, Client ID, Client Secret

2. Enable WebSocket Subscription

In your app, go to Feature → Event Subscriptions
Add an Event Subscription
Select WebSockets as the method type
Select events to subscribe to (e.g., meeting.created, meeting.started)
Save - an endpoint URL will be generated

3. Connect via WebSocket

const WebSocket = require('ws');
const axios = require('axios');

// Step 1: Get access token
async function getAccessToken() {
  const credentials = Buffer.from(`${CLIENT_ID}:${CLIENT_SECRET}`).toString('base64');
  
  const response = await axios.post(
    'https://zoom.us/oauth/token',
    new URLSearchParams({
      grant_type: 'account_credentials',
      account_id: ACCOUNT_ID
    }),
    {
      headers: {
        'Authorization': `Basic ${credentials}`,
        'Content-Type': 'application/x-www-form-urlencoded'
      }
    }
  );
  
  return response.data.access_token;
}

// Step 2: Connect to WebSocket
async function connectWebSocket() {
  const accessToken = await getAccessToken();
  
  // WebSocket URL from your subscription settings
  const wsUrl = `wss://ws.zoom.us/ws?subscriptionId=${SUBSCRIPTION_ID}&access_token=${accessToken}`;
  
  const ws = new WebSocket(wsUrl);
  
  ws.on('open', () => {
    console.log('WebSocket connection established');
  });
  
  ws.on('message', (data) => {
    const event = JSON.parse(data);
    console.log('Event received:', event.event);
    
    // Handle different event types
    switch (event.event) {
      case 'meeting.started':
        console.log(`Meeting started: ${event.payload.object.topic}`);
        break;
      case 'meeting.ended':
        console.log(`Meeting ended: ${event.payload.object.uuid}`);
        break;
      case 'meeting.participant_joined':
        console.log(`Participant joined: ${event.payload.object.participant.user_name}`);
        break;
    }
  });
  
  ws.on('close', (code, reason) => {
    console.log(`Connection closed: ${code} - ${reason}`);
    // Implement reconnection logic
  });
  
  ws.on('error', (error) => {
    console.error('WebSocket error:', error);
  });
  
  return ws;
}

connectWebSocket();

Event Format

Events received via WebSocket have the same format as webhook events:

…

查看完整文档 ↗

帮助开发者构建与排查 Zoom Virtual Agent 的嵌入、集成与知识库同步流程。

anthropics装→

$ loading_

请帮我安装 askskill 上的 "setup-zoom-websockets" 技能： 1. 下载 https://raw.githubusercontent.com/anthropics/knowledge-work-plugins/main/partner-built/zoom-plugin/skills/websockets/SKILL.md 2. 保存为 ~/.claude/skills/websockets/SKILL.md 3. 装好后重载技能，告诉我可以用了

// 用法示例

配置实时事件连接

输入

请说明如何为 Zoom WebSockets 搭建实时事件连接方案，包括连接建立、认证方式、断线重连和事件处理的实现步骤。

预期产出

一份分步骤的接入指南，说明如何建立并维护 Zoom WebSockets 实时连接。

比较 WebSockets 与 Webhooks

输入

请比较 Zoom WebSockets 和 Webhooks 的适用场景，重点说明在低延迟、持久连接和安全限制下为什么应优先选择 WebSockets。

预期产出

一份场景对比与选型建议，帮助判断何时应使用 Zoom WebSockets。

设计安全连接策略

输入

请为 Zoom WebSockets 设计一套安全连接策略，涵盖认证、密钥管理、访问控制、异常监控和重试机制。

预期产出

一份面向生产环境的安全与稳定性方案，适合实时事件系统实施。

// 文档

/setup-zoom-websockets

Background reference for persistent Zoom event streams. Prefer workflow routing first, then use this file when WebSockets are plausibly better than webhooks.

WebSockets vs Webhooks

Aspect	WebSockets	Webhooks
Connection	Persistent, bidirectional	One-time HTTP POST
Latency	Lower (no HTTP overhead)	Higher (new connection per event)
Security	Direct connection, no exposed endpoint	Requires endpoint validation, IP whitelisting
Model	Pull (you connect to Zoom)	Push (Zoom connects to you)
State	Stateful (maintains connection)	Stateless (each event independent)
Setup	More complex (access token, connection)	Simpler (just endpoint URL)

Choose WebSockets when:

Real-time, low-latency updates are critical
Security is paramount (banking, healthcare, finance)
You don't want to expose a public endpoint
You need bidirectional communication

Choose Webhooks when:

Simpler setup is preferred
Small number of event notifications
Existing HTTP infrastructure

Prerequisites

Server-to-Server OAuth app in Zoom Marketplace
Account ID, Client ID, and Client Secret
WebSocket subscription with events enabled

Need help with S2S OAuth? See the zoom-oauth skill for complete authentication flows.

Start troubleshooting fast: Use the 5-Minute Runbook before deep debugging.

Quick Start

1. Create Server-to-Server OAuth App

Go to Zoom Marketplace
Create a Server-to-Server OAuth app
Copy Account ID, Client ID, Client Secret

2. Enable WebSocket Subscription

In your app, go to Feature → Event Subscriptions
Add an Event Subscription
Select WebSockets as the method type
Select events to subscribe to (e.g., meeting.created, meeting.started)
Save - an endpoint URL will be generated

3. Connect via WebSocket

const WebSocket = require('ws');
const axios = require('axios');

// Step 1: Get access token
async function getAccessToken() {
  const credentials = Buffer.from(`${CLIENT_ID}:${CLIENT_SECRET}`).toString('base64');
  
  const response = await axios.post(
    'https://zoom.us/oauth/token',
    new URLSearchParams({
      grant_type: 'account_credentials',
      account_id: ACCOUNT_ID
    }),
    {
      headers: {
        'Authorization': `Basic ${credentials}`,
        'Content-Type': 'application/x-www-form-urlencoded'
      }
    }
  );
  
  return response.data.access_token;
}

// Step 2: Connect to WebSocket
async function connectWebSocket() {
  const accessToken = await getAccessToken();
  
  // WebSocket URL from your subscription settings
  const wsUrl = `wss://ws.zoom.us/ws?subscriptionId=${SUBSCRIPTION_ID}&access_token=${accessToken}`;
  
  const ws = new WebSocket(wsUrl);
  
  ws.on('open', () => {
    console.log('WebSocket connection established');
  });
  
  ws.on('message', (data) => {
    const event = JSON.parse(data);
    console.log('Event received:', event.event);
    
    // Handle different event types
    switch (event.event) {
      case 'meeting.started':
        console.log(`Meeting started: ${event.payload.object.topic}`);
        break;
      case 'meeting.ended':
        console.log(`Meeting ended: ${event.payload.object.uuid}`);
        break;
      case 'meeting.participant_joined':
        console.log(`Participant joined: ${event.payload.object.participant.user_name}`);
        break;
    }
  });
  
  ws.on('close', (code, reason) => {
    console.log(`Connection closed: ${code} - ${reason}`);
    // Implement reconnection logic
  });
  
  ws.on('error', (error) => {
    console.error('WebSocket error:', error);
  });
  
  return ws;
}

connectWebSocket();

Event Format

Events received via WebSocket have the same format as webhook events:

…

查看完整文档 ↗