Localized reading guide
video-sdk/windowsPurpose, usage and source
Zoom Video SDK for Windows - C++ integration for video sessions, raw audio/video capture, screen sharing, recording, and real-time communication
Source retrieved:
- Source repository
- anthropics/knowledge-work-plugins
- SKILL.md
partner-built/zoom-plugin/skills/video-sdk/windows/SKILL.md- Repository stars
- 34,049
- Repository updated
- 2026-10-30
- Categories
- Integrations
- Last collected
License: License file needs review
Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.
The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.
What this Skill does
Zoom Video SDK for Windows - C++ integration for video sessions, raw audio/video capture, screen sharing, recording, and real-time communication
How the upstream workflow works
Quick Start Path
If you're new to the SDK, follow this order: Overview → windows.md Read the architecture pattern → concepts/sdk-architecture-pattern.md Universal formula: Singleton → Delegate → Subscribe
Upstream passage · L765 ↗SDK Overview
The Zoom Video SDK for Windows is a C++ library that provides: Session Management: Join/leave video SDK sessions Raw Data Access: Capture raw audio/video frames (YUV420, PCM) Raw Data Injection: Send custom audio/video into sessions
Upstream passage · L48 ↗Core Concepts (Start Here!)
SDK Architecture Pattern - Universal 3-step pattern for ANY feature Singleton Hierarchy - 5-level navigation guide Canvas vs Raw Data - Choose your rendering approach
Upstream passage · L685 ↗using ZoomVideoSDK;
var sdkManager = new ZoomSDKManager();
sdkManager.Initialize();
sdkManager.JoinSession("my-session", "jwt-token", "User Name", "");Requirements and setup
System Requirements
OS: Windows 10 (1903 or later) or Windows 11 Architecture: x64 (recommended), x86, or ARM64
Upstream passage · L66 ↗Limits and quality checks
Thread Safety
SDK callbacks execute on SDK threads, not your main thread: Don't perform heavy operations in callbacks
Upstream passage · L262 ↗Start with a safe trial
- Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
- Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
- Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
- Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.
Read further in the source
- Zoom Video SDK - Windows Development
- Quick Links
- SDK Overview
- System Requirements
- Visual Studio Workloads
- Sample Applications
- ⚠️ CRITICAL: Windows Message Pump Required
- Audio Connection Strategy
- All Delegate Callbacks Must Be Implemented
- Memory Mode for Raw Data
- Thread Safety
- Consult Official Samples First
- Video Rendering - Two Approaches
- 🎯 Canvas API (Recommended for Most Use Cases)
- 🔧 Raw Data Pipe (Advanced Use Cases)
- Self Video vs Remote Users
- Event-Driven Subscription Pattern
- ⚠️ Screen Share Subscription (DIFFERENT from Video!)
- Multi-User Video Layout
- Complete Documentation Library
- Core Concepts (Start Here!)
- Complete Examples
- UI Framework Integration
- C++/CLI Wrapper Patterns (Wrapping ANY Native Library)
- Troubleshooting
- References
- Most Critical Issues (From Real Debugging)
- Key Insight
- Resources
- Quick Start Path
Related Skills
Translation and scope
This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.
This introduction refers to the pinned version below; current repository activity and collection time are shown separately.
- Pinned source
- Read the original ↗
- Source retrieved
- Source commit
2574e29377c7173d0cecffef29a6ecbd7f8ccb5d- Source SHA-256
0265131b1351d587abdc073fd91663836dd78effd309ef59d5cb1521af0466fe