mcpField
P
probe-sdk

probe-sdk

github.com/anthropicsTesting & quality33.6k2.1k installsUpdated 1d ago
Repository

About probe-sdk

A reference skill for using Zoom Probe SDK to check device and network readiness before meeting or session workflows. It covers diagnostic lifecycle, reporting, and routing to related SDK guidance when a different workflow is needed.

Key features

  1. 01Device and network diagnostics
  2. 02Audio and video checks
  3. 03Network diagnostic statistics
  4. 04Readiness reports and gates
  5. 05Lifecycle and cleanup guidance

Use cases

  1. 01Pre-join checks before a Meeting SDK flow
  2. 02Collecting diagnostics for support
  3. 03Certifying controlled endpoint devices
  4. 04Checking browser media capabilities

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/anthropics/knowledge-work-plugins --skill probe-sdk

After installing, type/probe-sdkin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

probe-sdk.md
RUNBOOK.md
concepts/
architecture-and-lifecycle.md
examples/
comprehensive-network-pattern.md
diagnostic-page-pattern.md
references/
environment-variables.md
probe-reference-map.md
samples-validation.md
source-map.md
versioning-and-compatibility.md
scenarios/
high-level-scenarios.md
troubleshooting/
common-issues.md

Details

From the project README

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.

Comments

Markdown supported