New to Claude Skills? Learn how to install them →

anthropics on GitHub

Zoom Probe SDK

OfficialFree

Ensure device readiness before Zoom meetings.

Get this skill

Free · Opens the source repo

What Zoom Probe SDK does

The Zoom Probe SDK serves as a comprehensive reference tool designed for preflight diagnostics on user devices and networks prior to joining a Zoom meeting or session. It provides developers with the necessary instructions to assess browser compatibility, media permissions, and network readiness, ensuring that users have a smooth experience when they join a meeting. By utilizing this SDK, developers can implement client-side diagnostics that evaluate device capabilities, which is crucial for applications that rely heavily on real-time communication.

The SDK guides users through a systematic process that starts with initializing the Prober or Reporter, followed by requesting media permissions and enumerating available devices. It includes targeted diagnostics for audio and video, as well as comprehensive network diagnostics, producing a final report that indicates the user's readiness to join a meeting. This structured approach not only helps in identifying potential issues but also enhances the overall user experience by ensuring that necessary conditions are met before the user attempts to connect.

This skill is particularly useful for developers building applications that integrate with Zoom, especially those that require pre-join checks to ensure device and network compatibility. It can be employed in various scenarios, such as creating a pre-join diagnostics page, supporting customer troubleshooting workflows, or certifying devices in controlled environments. By leveraging the Zoom Probe SDK, developers can create robust applications that minimize connectivity issues and enhance user satisfaction during meetings.

While the Zoom Probe SDK is an excellent tool for preflight diagnostics, it is not intended for use in scenarios where embedded meeting flows or custom real-time session experiences are required. For those use cases, developers should consider utilizing the Meeting SDK or Video SDK instead. Additionally, it does not handle backend orchestration of events or APIs, which would require integration with other SDKs such as Rivet or REST APIs.

When to use it

Use the Zoom Probe SDK when you need to perform client-side diagnostics and readiness checks prior to user sessions.

When not to use it

Do not use this SDK for embedded meeting flows or backend orchestration tasks.

What you can build with it

Pre-Join Diagnostics Page

Implement a diagnostics page that assesses user device readiness before they join a Zoom meeting.

Customer Troubleshooting Support

Capture structured reports to assist customers in troubleshooting connectivity issues during meetings.

Device Certification for Kiosks

Use the SDK to certify devices in controlled environments, ensuring they meet necessary requirements for Zoom meetings.

How to install Zoom Probe SDK

View source

1. Install with the skills CLI

npx skills add anthropics/knowledge-work-plugins/probe-sdk --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by anthropics

Zoom Probe SDK

Background reference for preflight diagnostics on user devices and networks before meeting or session workflows.

Official docs:

Reference sample:

Routing Guardrail

Quick Links

Start here:

  1. probe-sdk.md
  2. concepts/architecture-and-lifecycle.md
  3. scenarios/high-level-scenarios.md
  4. examples/diagnostic-page-pattern.md
  5. examples/comprehensive-network-pattern.md
  6. references/probe-reference-map.md
  7. references/environment-variables.md
  8. references/versioning-and-compatibility.md
  9. references/samples-validation.md
  10. references/source-map.md
  11. troubleshooting/common-issues.md
  12. RUNBOOK.md

Common Lifecycle Pattern

  1. Initialize Prober / Reporter.
  2. Request media permissions and enumerate devices.
  3. Run targeted diagnostics (diagnoseAudio, diagnoseVideo).
  4. Run comprehensive network diagnostic (startToDiagnose) and stream stats to UI.
  5. Produce final report and apply readiness gates.
  6. Stop/cleanup (stopToDiagnose, stopToDiagnoseVideo, releaseMediaStream, cleanup).

High-Level Scenarios

  • Pre-join diagnostics page before Meeting SDK join action.
  • Support workflow that captures structured report for customer troubleshooting.
  • Device certification flow for kiosk or controlled endpoint environments.
  • Browser capability gating for advanced media features.

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

Chaining

Environment Variables

Operations

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

Frequently asked questions about Zoom Probe SDK

Similar skills