Reference skill for Zoom Probe SDK. Use after routing to a preflight workflow when testing browser compatibility, media permissions, audio or video diagnostics, and network readiness before users join.
This reference skill covers the Zoom Probe SDK, a browser-side diagnostics SDK used to check media devices, network quality, and browser capability before a user joins a meeting or session. It solves the preflight-readiness problem: answering whether a given user, device, and network can support an acceptable real-time media experience, so applications can gate joins with allow/warn/block decisions.
The skill documents the Probe SDK lifecycle — initialize `Prober`/`Reporter`, request media permissions and enumerate devices, run targeted audio and video diagnostics (`diagnoseAudio`, `diagnoseVideo`), run a comprehensive network diagnostic (`startToDiagnose`) streaming live stats to the UI, produce a final report, then clean up. It includes architecture notes, high-level scenarios (pre-join diagnostics pages, support troubleshooting reports, kiosk device certification, browser capability gating), a reference map of core classes/methods/enums, environment-variable conventions, versioning notes, and troubleshooting. Notably, it states that Probe SDK requires no Zoom Marketplace OAuth credentials for core diagnostics, making it a lightweight preflight page before auth-sensitive flows; optional env keys only override runtime URLs, domain, and durations.
It targets web developers building pre-join readiness gates, support workflows that capture structured diagnostic reports, and controlled-endpoint certification flows. The content is documentation and code-pattern reference grounded in the official Zoom Probe SDK docs and the probesdk-web sample; it performs read-only client diagnostics and requires no credentials or exfiltration.
It runs client-side preflight diagnostics on media devices, network quality, and browser capability, producing a readiness report used to allow, warn, or block a join.
No. The skill states no Zoom Marketplace OAuth credentials are required for core diagnostics; only optional env keys override the probe runtime URLs, domain, and durations.
Initialize Prober/Reporter, request media permissions and enumerate devices, run targeted audio/video diagnostics, run a comprehensive network diagnostic with a live stats callback, produce a final report, then stop and clean up.
Pre-join diagnostics pages before a Meeting SDK join, support workflows that capture a structured report, kiosk/controlled-endpoint certification, and browser capability gating.
Keep the readiness policy product-specific and versioned, define explicit allow/warn/block thresholds per signal, recalibrate on SDK or browser-baseline changes, and log the policy version with each report.
Quick Setup:
.claude/skills/Repository
anthropics/knowledge-work-plugins