Zoom Probe SDK
Background reference for preflight diagnostics on user devices and networks before meeting or session workflows.
Official docs:
https://developers.zoom.us/docs/probe-sdk/
https://marketplacefront.zoom.us/sdk/probe/index.html
Reference sample:
https://github.com/zoom/probesdk-web
Routing Guardrail
Use Probe SDK when the user needs client-side diagnostics and readiness scoring (device/network/browser capability), not meeting/session join.
If user needs embedded meeting flows, route to ../meeting-sdk/SKILL.md.
If user needs custom real-time session UX, route to ../video-sdk/SKILL.md.
If user needs backend orchestration of events/APIs, chain with ../rivet-sdk/SKILL.md, ../oauth/SKILL.md, and ../rest-api/SKILL.md.
Quick Links
related skills
semantically similar in the cross-vendor index
don't have the plugin yet? install it then click "run inline in claude" again.
+clear routing guardrails that disambiguate probe-sdk from meeting-sdk, video-sdk, and backend integration paths
+external documentation references point to official zoom sources and working sample code
+identifies specific use case (client-side diagnostics and readiness scoring) rather than generic integration
weaknesses
~no structured intent/inputs/procedure/outputs; skill is metadata and routing only, lacks actionable workflow steps
~no decision trees, failure modes, or edge case coverage (what happens if diagnostics fail? how to retry or degrade gracefully?)
~documentation reads as a reference skeleton rather than a task guide; no concrete example of invoking probe-sdk or interpreting results
