Generated banner for Zoom General
Generated logo for Zoom General

Zoom General

AnthropicOfficialCreated by ZoomDistributed by Anthropic

  • Skill
  • Meta (authoring, orchestration, planning, memory)
  • Agent tooling
  • MIT
  • Medium risk

From the author

Cross-product Zoom reference skill. Use after the workflow is clear when you need shared platform guidance, app-model comparisons, authentication context, scopes, marketplace considerations, or API-vs-MCP routing.
— the description by Zoom

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The zoom-general skill serves as the primary entry point and classification layer for developers working with the Zoom platform. It provides a structured framework to identify the correct Zoom product, SDK, or API path based on user intent. It includes logic for routing complex queries, chaining multiple skills (such as combining REST APIs with OAuth and webhooks), and resolving ambiguities between deterministic automation and AI-driven agentic workflows.

What it does

  • Classifies developer queries to identify the appropriate Zoom product or SDK.
  • Provides a routing matrix to distinguish between REST API, MCP, and SDK use cases.
  • Offers guidance on choosing the correct Zoom app type (General, S2S, or Webhook-only).
  • Facilitates skill chaining for multi-step integrations like OAuth and webhook setups.
  • Provides decision frameworks for API vs. MCP and SDK vs. REST implementation paths.
  • Acts as a central index for all specialized Zoom developer skills.

When to use it

  • When you are unsure which Zoom SDK or API is required for your project.
  • When you need to determine if your task requires REST APIs, MCP tools, or a hybrid approach.
  • When planning a complex integration that involves authentication, webhooks, and API orchestration.
  • When you need to compare different Zoom app types to match your architectural requirements.
  • When you need to resolve ambiguity between similar Zoom products like Meeting SDK and Video SDK.

Advantages

  • Reduces development friction by directing users to the most relevant documentation and skills.
  • Ensures architectural consistency by enforcing standard routing patterns.
  • Simplifies complex decision-making through clear matrices and guardrails.
  • Promotes best practices for authentication and event-driven design.
  • Provides a unified entry point for navigating the entire Zoom developer ecosystem.

Usage examples

“I want to build a custom video UI for a Zoom meeting on the web, what should I use?”
The skill identifies the requirement for a custom UI around a real meeting and routes the user to the zoom-meeting-sdk-web-component-view skill.
“Should I use the REST API or MCP for my AI agent?”
The skill provides the API vs. MCP routing matrix, explaining that REST is for deterministic automation while MCP is for dynamic AI tool orchestration.
“How do I set up a server-side integration that handles meetings and webhooks?”
The skill suggests the Rivet SDK for scaffolding or chains the zoom-rest-api, zoom-oauth, and zoom-webhooks skills.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/anthropics/zoom-general/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip zoom-general.zip -d .agents/skills

Documentation by Zoom

Zoom General (Cross-Product Skills)

Background reference for cross-product Zoom questions. Prefer the workflow skills first, then use this file for shared platform guidance and routing detail.

How zoom-general Routes a Complex Developer Query

Use zoom-general as the classifier and chaining layer:

  1. detect product signals in the query

  2. pick one primary skill

  3. attach secondary skills for auth, events, or deployment edges

  4. ask one short clarifier only when two routes match with similar confidence

Minimal implementation:

type SkillId =
  | 'zoom-general'
  | 'zoom-rest-api'
  | 'zoom-webhooks'
  | 'zoom-oauth'
  | 'zoom-meeting-sdk-web-component-view'
  | 'zoom-video-sdk'
  | 'zoom-mcp';

const hasAny = (q: string, words: string[]) => words.some((w) => q.includes(w));

function detectSignals(rawQuery: string) {
  const q = rawQuery.toLowerCase();
  return {
    meetingCustomUi: hasAny(q, ['zoom meeting', 'custom ui', 'component view', 'embed meeting']),
    customVideo: hasAny(q, ['video sdk', 'custom video session', 'peer-video-state-change']),
    restApi: hasAny(q, ['rest api', '/v2/', 'create meeting', 'list users', 's2s oauth']),
    webhooks: hasAny(q, ['webhook', 'x-zm-signature', 'event subscription', 'crc']),
    oauth: hasAny(q, ['oauth', 'pkce', 'token refresh', 'account_credentials']),
    mcp: hasAny(q, ['zoom mcp', 'agentic retrieval', 'tools/list', 'semantic meeting search']),
  };
}

function pickPrimarySkill(s: ReturnType<typeof detectSignals>): SkillId {
  if (s.meetingCustomUi) return 'zoom-meeting-sdk-web-component-view';
  if (s.mcp) return 'zoom-mcp';
  if (s.restApi) return 'zoom-rest-api';
  if (s.customVideo) return 'zoom-video-sdk';
  return 'zoom-general';
}

function buildChain(primary: SkillId, s: ReturnType<typeof detectSignals>): SkillId[] {
  const chain = [primary];
  if (s.oauth && !chain.includes('zoom-oauth')) chain.push('zoom-oauth');
  if (s.webhooks && !chain.includes('zoom-webhooks')) chain.push('zoom-webhooks');
  return chain;
}

Example:

  • Create a meeting, configure webhooks, and handle OAuth token refresh -> zoom-rest-api -> zoom-oauth -> zoom-webhooks

  • Build a custom video UI for a Zoom meeting on web -> zoom-meeting-sdk-web-component-view

For the full TypeScript implementation and handoff contract, use references/routing-implementation.md.

Choose Your Path

I want to...Use this skill
Build a custom web UI around a real Zoom meetingzoom-meeting-sdk-web-component-view
Build deterministic automation/configuration/reporting with explicit request controlzoom-rest-api
Receive event notifications (HTTP push)zoom-webhooks
Receive event notifications (WebSocket, low-latency)zoom-websockets
Embed Zoom meetings in my appzoom-meeting-sdk
Build custom video experiences (Web, React Native, Flutter, Android, iOS, macOS, Unity, Linux)zoom-video-sdk
Build an app that runs inside Zoom clientzoom-apps-sdk
Transcribe uploaded or stored media with AI Services Scribescribe
Access live audio/video/transcripts from meetingszoom-rtms
Enable collaborative browsing for supportzoom-cobrowse-sdk
Build Contact Center apps and channel integrationscontact-center
Build Virtual Agent web/mobile chatbot experiencesvirtual-agent
Build Zoom Phone integrations (Smart Embed, Phone API, webhooks, URI flows)phone
Build Team Chat apps and integrationszoom-team-chat
Build server-side integrations with Rivet (auth + webhooks + APIs)rivet-sdk
Run browser/device/network preflight diagnostics before joinprobe-sdk
Add pre-built UI components for Video SDKzoom-ui-toolkit
Implement OAuth authentication (all grant types)zoom-oauth
Build AI-driven tool workflows (AI Companion/agents) over Zoom datazoom-mcp
Build AI-driven Whiteboard workflows over Zoom Whiteboard MCPzoom-mcp/whiteboard
Build enterprise AI systems with stable API core + AI tool layerzoom-rest-api + zoom-mcp

Planning Checkpoint: Rivet SDK (Optional)

When a user starts planning a server-side integration that combines auth + webhooks + API calls, ask this first:

  • Rivet SDK is a Node.js framework that bundles Zoom auth handling, webhook receivers, and typed API wrappers.

  • Do you want to use Rivet SDK for faster scaffolding, or do you prefer a direct OAuth + REST implementation without Rivet?

Routing after answer:

  • If user chooses Rivet: chain rivet-sdk + oauth + rest-api.

  • If user declines Rivet: chain oauth + rest-api (+ webhooks or product skill as needed).

SDK vs REST Routing Matrix (Hard Stop)
User intentCorrect pathDo not route to
Embed Zoom meeting in app UIzoom-meeting-sdkREST-only join_url flow
Build custom web UI for a real Zoom meetingzoom-meeting-sdk-web-component-viewzoom-video-sdk
Build custom video UI/session appzoom-video-sdkMeeting SDK or REST meeting links
Get browser join links / manage meeting resourceszoom-rest-apiMeeting SDK join implementation

Routing guardrails:

  • If user asks for SDK embed/join behavior, stay in SDK path.

  • If the prompt says meeting plus custom UI/video/layout/embed, prefer zoom-meeting-sdk-web-component-view.

  • Only use zoom-video-sdk when the user is building a custom session product rather than a Zoom meeting.

  • Only use REST path for resource management, reporting, or link distribution unless user explicitly requests a mixed architecture.

  • For executable classification/chaining logic and error handling, see references/routing-implementation.md.

API vs MCP Routing Matrix (Hard Stop)
User intentCorrect pathWhy
Deterministic backend automation, account/user configuration, reporting, scheduled jobszoom-rest-apiExplicit request/response control and repeatable behavior
AI agent chooses tools dynamically, cross-platform AI tool interoperabilityzoom-mcpMCP is optimized for dynamic tool discovery and agentic workflows
Enterprise AI architecture (stable core + adaptive AI layer)zoom-rest-api + zoom-mcpAPIs run core system actions; MCP exposes curated AI tools/context

Routing guardrails:

  • Do not replace deterministic backend APIs with MCP-only routing.

  • Do not force raw REST-first routing when the task is AI-agent tool orchestration.

  • Prefer hybrid routing when the user needs both stable automation and AI-driven interactions.

  • MCP remote server works over Streamable HTTP/SSE; use this path when the target client/agent supports MCP transports (for example Claude or VS Code).

  • Do not design per-tenant custom MCP endpoint provisioning; Zoom MCP endpoints are shared at instance/cluster level.

  • Source: https://developers.zoom.us/docs/mcp/library/resources/apis-vs-mcp/

Ambiguity Resolution (Ask Before Routing)

When a prompt matches both API and MCP paths with similar confidence, ask one short clarifier before execution:

  • Do you want deterministic REST API automation, AI-agent MCP tooling, or a hybrid of both?

Then route as:

  • REST answer → zoom-rest-api

  • MCP answer → zoom-mcp

  • Hybrid answer → zoom-rest-api + zoom-mcp

MCP Availability and Topology Notes
  • Zoom-hosted MCP access is evolving; docs indicate a model where Zoom exposes product-scoped MCP servers (for example Meetings, Team Chat, Whiteboard).

  • Use zoom-mcp as the parent MCP entry point.

  • Route Whiteboard-specific MCP requests to zoom-mcp/whiteboard.

  • When a request is product-specific and MCP coverage exists, route to that MCP product surface first; otherwise use REST/SDK skills for deterministic implementation.

Webhooks vs WebSockets

Both receive event notifications, but differ in approach:

Aspectwebhookszoom-websockets
ConnectionHTTP POST to your endpointPersistent WebSocket
LatencyHigherLower
SecurityRequires public endpointNo exposed endpoint
SetupSimplerMore complex
Best forMost use casesReal-time, security-sensitive

Common Use Cases

Use CaseDescriptionSkills Needed
Meeting + Webhooks + OAuth RefreshCreate a meeting, process real-time updates, and refresh OAuth tokens safely in one designzoom-rest-api + zoom-oauth + zoom-webhooks
Scribe Transcription PipelineTranscribe uploaded files or S3 archives with AI Services Scribe using fast mode or batch jobsscribe + optional zoom-rest-api + optional zoom-webhooks
APIs vs MCP RoutingDecide whether to route to deterministic Zoom APIs, AI-driven MCP, or a hybrid designzoom-rest-api and/or zoom-mcp
Custom Meeting UI (Web)Build a custom video UI for a real Zoom meeting in a web app using Meeting SDK Component Viewzoom-meeting-sdk-web-component-view + zoom-oauth
Meeting AutomationSchedule, update, delete meetings programmaticallyzoom-rest-api
Meeting BotsBuild bots that join meetings for AI/transcription/recordingmeeting-sdk/linux + zoom-rest-api + optional zoom-webhooks
High-Volume Meeting PlatformDesign distributed meeting creation and event processing with retries, queues, and reconciliationzoom-rest-api + zoom-webhooks + zoom-oauth
Recording & TranscriptionDownload recordings, get transcriptszoom-webhooks + zoom-rest-api
Recording Download PipelineAuto-download recordings to your own storage (S3, GCS, etc.)zoom-webhooks + zoom-rest-api
Real-Time Media StreamsAccess live audio, video, transcripts via WebSocketzoom-rtms + zoom-webhooks
In-Meeting AppsBuild apps that run inside Zoom meetingszoom-apps-sdk + zoom-oauth
React Native Meeting EmbedEmbed meetings into iOS/Android React Native appszoom-meeting-sdk-react-native + zoom-oauth
Native Meeting SDK Multi-Platform DeliveryAlign Android, iOS, macOS, and Unreal Meeting SDK implementations under one auth/version strategyzoom-meeting-sdk + platform skills
Native Video SDK Multi-Platform DeliveryAlign Android, iOS, macOS, and Unity Video SDK implementations under one auth/version strategyzoom-video-sdk + platform skills
Electron Meeting EmbedEmbed meetings into desktop Electron appszoom-meeting-sdk-electron + zoom-oauth
Flutter Video SessionsBuild custom mobile video sessions in Flutterzoom-video-sdk-flutter + zoom-oauth
React Native Video SessionsBuild custom mobile video sessions in React Nativezoom-video-sdk-react-native + zoom-oauth
Immersive ExperiencesCustom video layouts with Layers APIzoom-apps-sdk
Collaborative AppsReal-time shared state in meetingszoom-apps-sdk
Contact Center App Lifecycle and Context SwitchingBuild Contact Center apps that handle engagement events and multi-engagement statecontact-center + zoom-apps-sdk
Virtual Agent Campaign Web and Mobile WrapperDeliver one campaign-driven bot flow across web and native mobile wrappersvirtual-agent + contact-center
Virtual Agent Knowledge Base Sync PipelineSync external knowledge content into Zoom Virtual Agent using web sync or custom API connectorsvirtual-agent + zoom-rest-api + zoom-oauth
Zoom Phone Smart Embed CRM IntegrationBuild CRM dialer and call logging flows using Smart Embed plus Phone APIsphone + zoom-oauth + zoom-webhooks
Rivet Event-Driven API OrchestratorBuild a Node.js backend that combines webhooks and API actions through Rivet module clientsrivet-sdk + zoom-oauth + zoom-rest-api
Probe SDK Preflight Readiness GateAdd browser/device/network diagnostics and readiness policy before Meeting SDK or Video SDK joinsprobe-sdk + zoom-meeting-sdk or zoom-video-sdk

Complete Use-Case Index

Prerequisites

  1. Zoom account (Pro, Business, or Enterprise)

  2. App created in Zoom App Marketplace

  3. OAuth credentials (Client ID and Secret)

References

Quick Start

  1. Go to marketplace.zoom.us

  2. Click Develop → Build App

  3. Select app type (see references/app-types.md)

  4. Configure OAuth and scopes

  5. Copy credentials to your application

Detailed References

SDK Maintenance

Resources

Environment Variables

Operations

  • RUNBOOK.md - 5-minute preflight and debugging checklist.

Files

use-cases/sdk-wrappers-gui.md

SDK Wrappers and GUI Integration

Building custom language wrappers and GUI applications with Zoom Meeting/Video SDKs.

Overview

The native Zoom SDKs are written in C++. To use them from other languages or with GUI frameworks, you need wrappers or direct integration.

PlatformWrapper/IntegrationUse Case
WindowsC++/CLI → C#WPF, WinForms, .NET apps
LinuxNative C++Qt, GTK desktop apps
LinuxDirect C++Headless bots, server-side

Windows: C++/CLI Wrapper for C#/.NET

Architecture
┌─────────────────────────────────────────────────────────────┐
│  C# Application Layer (WPF / WinForms / .NET)              │
│  - UI controls, business logic                              │
│  - Uses managed ZOOM_SDK_DOTNET_WRAP namespace             │
└─────────────────────────────────────────────────────────────┘
                          ↕ Managed/Unmanaged Boundary
┌─────────────────────────────────────────────────────────────┐
│  C++/CLI Wrapper Layer (zoom_sdk_dotnet_wrap.dll)          │
│  - Managed ref classes with ^ handles                       │
│  - Native C++ classes calling SDK                           │
│  - Event bridging: std::bind → C# delegates                │
└─────────────────────────────────────────────────────────────┘
                          ↕ Native C++ Interface
┌─────────────────────────────────────────────────────────────┐
│  Native Zoom SDK (videosdk.dll / sdk.dll)                  │
│  - Loaded dynamically via sdk_dll_path                      │
└─────────────────────────────────────────────────────────────┘
Why C++/CLI (Not P/Invoke)?
AspectP/InvokeC++/CLI
Complex C++ objects❌ Difficult✅ Native support
Callbacks/delegates❌ Manual marshaling✅ Automatic bridging
Object lifetime❌ Manual GC pinning✅ Automatic handling
std::function patterns❌ Not supported✅ Works with std::bind
Project Structure
videosdk-windows-dotnet-quickstart/
├── ZoomVideoSDK.CSharp.sln          # Visual Studio solution
├── config.json                       # Runtime configuration
├── sdk/                              # Zoom SDK files
│   └── x64/
│       ├── h/                        # C++ headers
│       ├── lib/                      # Static libraries (.lib)
│       └── bin/                      # Runtime DLLs (.dll)
├── ZoomVideoSDK.Wrapper/             # C++/CLI wrapper project
│   ├── ZoomVideoSDK.Wrapper.vcxproj  # CLRSupport=true
│   ├── ZoomSDKManager.h              # Managed wrapper class
│   └── ZoomSDKManager.cpp
├── ZoomVideoSDK.WinForms/            # C# WinForms app
│   ├── MainForm.cs
│   └── ZoomSDKInterop.cs
└── ZoomVideoSDK.WPF/                 # C# WPF app
    ├── MainWindow.xaml
    └── MainWindow.xaml.cs
C++/CLI Wrapper Implementation

Project Configuration (.vcxproj):

<PropertyGroup>
  <ConfigurationType>DynamicLibrary</ConfigurationType>
  <CLRSupport>true</CLRSupport>  <!-- Enable C++/CLI -->
  <CharacterSet>Unicode</CharacterSet>
</PropertyGroup>

Wrapper Class (C++/CLI):

// ZoomSDKManager.h
#pragma once

using namespace System;

namespace ZoomVideoSDK {
    namespace Wrapper {
        
        // Managed delegate (callable from C#)
        public delegate void SessionStatusChangedHandler(String^ status, String^ message);
        
        // Managed wrapper class
        public ref class ZoomSDKManager sealed {
        public:
            static property ZoomSDKManager^ Instance {
                ZoomSDKManager^ get() { return m_Instance; }
            }
            
            bool Initialize(String^ sdkDllPath);
            bool JoinSession(String^ sessionName, String^ token, String^ userName);
            void LeaveSession();
            
            // Events exposed to C#
            event SessionStatusChangedHandler^ SessionStatusChanged;
            
        private:
            static ZoomSDKManager^ m_Instance = gcnew ZoomSDKManager;
            
            // Bridge to invoke C# events from native callbacks
            void OnSessionStatusChanged(String^ status, String^ message) {
                SessionStatusChanged(status, message);
            }
        };
    }
}

Callback Bridging Pattern:

// Native C++ handler class (unmanaged)
class NativeEventHandler {
public:
    static NativeEventHandler& GetInst() {
        static NativeEventHandler inst;
        return inst;
    }
    
    void onSessionJoin() {
        // Forward to managed wrapper using QMetaObject pattern
        ZoomSDKManager::Instance->OnSessionStatusChanged("Joined", "Session joined successfully");
    }
};

// Binding native callbacks to handler
void ZoomSDKManager::BindEvents() {
    // Use std::bind to connect native callbacks
    ZOOM_SDK::GetSessionService().m_cbonSessionJoin = 
        std::bind(&NativeEventHandler::onSessionJoin, &NativeEventHandler::GetInst());
}
C# Application Usage

WPF Example:

using ZoomVideoSDK.Wrapper;

public partial class MainWindow : Window
{
    private ZoomSDKManager _sdk;
    
    public MainWindow()
    {
        InitializeComponent();
        
        _sdk = ZoomSDKManager.Instance;
        _sdk.SessionStatusChanged += OnSessionStatusChanged;
    }
    
    private void JoinButton_Click(object sender, RoutedEventArgs e)
    {
        bool initialized = _sdk.Initialize(@".\sdk\x64\bin");
        if (initialized)
        {
            _sdk.JoinSession(
                sessionName: SessionNameTextBox.Text,
                token: JwtTokenTextBox.Text,
                userName: UserNameTextBox.Text
            );
        }
    }
    
    private void OnSessionStatusChanged(string status, string message)
    {
        // Must invoke on UI thread
        Dispatcher.Invoke(() => {
            StatusLabel.Content = $"{status}: {message}";
        });
    }
}

WinForms Example:

public partial class MainForm : Form
{
    private ZoomSDKManager _sdk;
    
    private void OnSessionStatusChanged(string status, string message)
    {
        // Must invoke on UI thread
        this.Invoke((MethodInvoker)delegate {
            statusLabel.Text = $"{status}: {message}";
        });
    }
}
Build Configuration

DLL Dependencies:

C# App (managed)
    ↓ references
ZoomVideoSDK.Wrapper.dll (C++/CLI mixed-mode)
    ↓ loads dynamically at runtime
videosdk.dll + dependencies (native)

Post-Build Events:

REM Copy SDK DLLs to output directory
xcopy /Y "$(SolutionDir)sdk\x64\bin\*.dll" "$(OutDir)"

Linux: Qt GUI Integration

Architecture
┌─────────────────────────────────────────────────────────────┐
│  Qt Application (C++)                                       │
│  - Qt Widgets / QML                                         │
│  - Signals/Slots for event handling                         │
└─────────────────────────────────────────────────────────────┘
                          ↕ Direct C++ calls
┌─────────────────────────────────────────────────────────────┐
│  Native Zoom SDK (libvideosdk.so)                          │
│  - Video/Audio processing                                   │
│  - Network communication                                    │
└─────────────────────────────────────────────────────────────┘
Project Structure
videosdk-linux-qt-quickstart/
├── README.md
├── run_qt_demo.sh                    # Run script
├── src/
│   ├── CMakeLists.txt                # Qt6/Qt5 build config
│   ├── config.json                   # Session config
│   ├── bin/                          # Build output
│   │   └── VideoSDKQtDemo
│   ├── include/                      # SDK headers
│   ├── lib/                          # SDK libraries
│   └── Source Files:
│       ├── zoom_v-sdk_linux_bot_qt.cpp   # Main entry
│       ├── QtMainWindow.h/cpp            # Main window
│       ├── QtVideoWidget.h/cpp           # Video display
│       ├── QtVideoRenderer.h/cpp         # YUV→RGB rendering
│       ├── QtPreviewVideoHandler.h/cpp   # Self video
│       └── QtRemoteVideoHandler.h/cpp    # Remote video
Qt Video Rendering
// QtVideoWidget.h
class QtVideoWidget : public QWidget {
    Q_OBJECT
    
public:
    explicit QtVideoWidget(QWidget* parent = nullptr);
    void updateFrame(const QImage& frame);
    
protected:
    void paintEvent(QPaintEvent* event) override;
    
private:
    QImage m_currentFrame;
    QMutex m_mutex;
};

// QtVideoWidget.cpp
void QtVideoWidget::updateFrame(const QImage& frame) {
    QMutexLocker lock(&m_mutex);
    m_currentFrame = frame;
    update();  // Trigger repaint
}

void QtVideoWidget::paintEvent(QPaintEvent* event) {
    QPainter painter(this);
    QMutexLocker lock(&m_mutex);
    
    if (!m_currentFrame.isNull()) {
        // Scale to fit with aspect ratio
        QImage scaled = m_currentFrame.scaled(
            size(), Qt::KeepAspectRatio, Qt::SmoothTransformation);
        
        // Center the image
        int x = (width() - scaled.width()) / 2;
        int y = (height() - scaled.height()) / 2;
        painter.drawImage(x, y, scaled);
    }
}
YUV to RGB Conversion
// QtVideoRenderer.cpp
QImage convertYUV420ToRGB(const unsigned char* yuvData, int width, int height) {
    QImage image(width, height, QImage::Format_RGB888);
    
    const unsigned char* yPlane = yuvData;
    const unsigned char* uPlane = yuvData + width * height;
    const unsigned char* vPlane = uPlane + (width * height / 4);
    
    for (int y = 0; y < height; y++) {
        for (int x = 0; x < width; x++) {
            int yIndex = y * width + x;
            int uvIndex = (y / 2) * (width / 2) + (x / 2);
            
            int Y = yPlane[yIndex];
            int U = uPlane[uvIndex] - 128;
            int V = vPlane[uvIndex] - 128;
            
            // ITU-R BT.601 conversion
            int R = qBound(0, (int)(Y + 1.402 * V), 255);
            int G = qBound(0, (int)(Y - 0.344 * U - 0.714 * V), 255);
            int B = qBound(0, (int)(Y + 1.772 * U), 255);
            
            image.setPixel(x, y, qRgb(R, G, B));
        }
    }
    
    return image;
}
Qt Event Threading
// Invoke SDK callbacks on Qt main thread
class VideoCallback : public IZoomVideoSDKRawDataPipeDelegate {
public:
    void onRawDataFrameReceived(YUVRawDataI420* data) override {
        QImage frame = convertYUV420ToRGB(data->getBuffer(), 
                                           data->getWidth(), 
                                           data->getHeight());
        
        // Thread-safe UI update using Qt's event system
        QMetaObject::invokeMethod(m_videoWidget, [this, frame]() {
            m_videoWidget->updateFrame(frame);
        }, Qt::QueuedConnection);
    }
    
private:
    QtVideoWidget* m_videoWidget;
};
Build with CMake
cmake_minimum_required(VERSION 3.14)
project(VideoSDKQtDemo)

set(CMAKE_CXX_STANDARD 17)

# Find Qt
find_package(Qt6 COMPONENTS Core Widgets REQUIRED)
# Or: find_package(Qt5 COMPONENTS Core Widgets REQUIRED)

# Find ALSA for audio
find_package(ALSA REQUIRED)

# Source files
set(SOURCES
    zoom_v-sdk_linux_bot_qt.cpp
    QtMainWindow.cpp
    QtVideoWidget.cpp
    QtVideoRenderer.cpp
)

add_executable(VideoSDKQtDemo ${SOURCES})

target_link_libraries(VideoSDKQtDemo
    Qt6::Core Qt6::Widgets
    ${ALSA_LIBRARIES}
    ${CMAKE_SOURCE_DIR}/lib/libvideosdk.so
)

Linux: GTK GUI Integration

Architecture
┌─────────────────────────────────────────────────────────────┐
│  GTKmm Application (C++)                                    │
│  - GTK Widgets (Gtk::Window, Gtk::Box, etc.)               │
│  - Glib signals for event handling                          │
│  - SDL2 for video rendering                                 │
└─────────────────────────────────────────────────────────────┘
                          ↕ Direct C++ calls
┌─────────────────────────────────────────────────────────────┐
│  Native Zoom SDK (libvideosdk.so)                          │
└─────────────────────────────────────────────────────────────┘
Project Structure
videosdk-linux-gtk-quickstart/
├── README.md
├── src/
│   ├── CMakeLists.txt
│   ├── config.json
│   ├── bin/
│   │   └── SkeletonDemo
│   └── Source Files:
│       ├── zoom_v-sdk_linux_bot.cpp     # Main entry + GTK UI
│       ├── VideoRenderer.h/cpp          # SDL2 video rendering
│       ├── VideoDisplayBridge.h/cpp     # SDK→Renderer bridge
│       ├── PreviewVideoHandler.h/cpp    # Self video
│       └── RemoteVideoRawDataHandler.h/cpp  # Remote video
GTK Video Rendering (SDL2)
// VideoRenderer.h
class VideoRenderer {
public:
    VideoRenderer(Gtk::Widget* container);
    ~VideoRenderer();
    
    void renderFrame(const unsigned char* yuvData, int width, int height);
    
private:
    SDL_Window* m_window;
    SDL_Renderer* m_renderer;
    SDL_Texture* m_texture;
};

// VideoRenderer.cpp
void VideoRenderer::renderFrame(const unsigned char* yuvData, int width, int height) {
    // Update YUV texture directly (SDL handles conversion)
    SDL_UpdateYUVTexture(m_texture, nullptr,
        yuvData,                           // Y plane
        width,                             // Y pitch
        yuvData + width * height,          // U plane
        width / 2,                         // U pitch
        yuvData + width * height * 5/4,    // V plane
        width / 2);                        // V pitch
    
    SDL_RenderClear(m_renderer);
    SDL_RenderCopy(m_renderer, m_texture, nullptr, nullptr);
    SDL_RenderPresent(m_renderer);
}
GTK Main Window
// zoom_v-sdk_linux_bot.cpp
class MainWindow : public Gtk::Window {
public:
    MainWindow() {
        set_title("Zoom Video SDK Demo");
        set_default_size(1200, 800);
        
        // Create layout
        auto mainBox = Gtk::make_managed<Gtk::Box>(Gtk::ORIENTATION_VERTICAL);
        
        // Device selection
        m_cameraCombo = Gtk::make_managed<Gtk::ComboBoxText>();
        m_micCombo = Gtk::make_managed<Gtk::ComboBoxText>();
        m_speakerCombo = Gtk::make_managed<Gtk::ComboBoxText>();
        
        // Control buttons
        m_joinButton = Gtk::make_managed<Gtk::Button>("Join Session");
        m_leaveButton = Gtk::make_managed<Gtk::Button>("Leave Session");
        
        // Video areas (SDL embedded)
        m_selfVideoArea = Gtk::make_managed<Gtk::DrawingArea>();
        m_remoteVideoArea = Gtk::make_managed<Gtk::DrawingArea>();
        
        // Connect signals
        m_joinButton->signal_clicked().connect(
            sigc::mem_fun(*this, &MainWindow::on_join_clicked));
        
        add(*mainBox);
        show_all_children();
    }
    
private:
    void on_join_clicked() {
        // Initialize SDK and join session
        ZoomVideoSDKInitParams params;
        params.domain = "https://zoom.us";
        m_sdk->initialize(params);
        
        ZoomVideoSDKSessionContext context;
        context.sessionName = m_sessionEntry->get_text().c_str();
        context.token = m_tokenEntry->get_text().c_str();
        m_sdk->joinSession(context);
    }
};
Build Dependencies
# Ubuntu/Debian
sudo apt install build-essential cmake
sudo apt install libgtkmm-3.0-dev libsdl2-dev
sudo apt install libasound2-dev libcurl4-openssl-dev
# CMakeLists.txt
find_package(PkgConfig REQUIRED)
pkg_check_modules(GTKMM REQUIRED gtkmm-3.0)
pkg_check_modules(SDL2 REQUIRED sdl2)
pkg_check_modules(ALSA REQUIRED alsa)

target_link_libraries(SkeletonDemo
    ${GTKMM_LIBRARIES}
    ${SDL2_LIBRARIES}
    ${ALSA_LIBRARIES}
    ${CMAKE_SOURCE_DIR}/lib/libvideosdk.so
)

Comparison: Qt vs GTK

AspectQtGTK
LanguageC++ (native)C++ (GTKmm wrapper)
Video RenderingQPainter / QImageSDL2 / Cairo
ThreadingSignals/Slots + QMetaObjectGlib main loop + idle callbacks
Build SystemCMake / qmakeCMake
Look & FeelPlatform-nativeGTK theme
Learning CurveModerateModerate

Resources

Sample Repositories
Official Documentation

Requirements and compatibility

Written for: Claude Code, Claude apps

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Claude Code frontmatter, Needs an MCP server

Security

What our scanner noticed· Medium risk

  • Possible data-exfiltration endpoints
  • Instructions that use the network

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Zoom
Publisher
Anthropic (Official)
Distributed by
Anthropic
Source
anthropics/knowledge-work-plugins · partner-built/zoom-plugin/skills/general · commit e050c2e
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from partner-built/zoom-plugin/LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Zoom or Anthropic.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download zoom-general.zip