C✳CODEZ.WIN
🌐 English

Localized reading guide

probe-sdkPurpose, usage and source

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.

Source retrieved:

Source repository
anthropics/knowledge-work-plugins
SKILL.md
partner-built/zoom-plugin/skills/probe-sdk/SKILL.md
Repository stars
34,049
Repository updated
2026-10-30
Categories
Automation
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

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.

How the upstream workflow works

Zoom Probe SDK

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

Upstream passage · L17 ↗

Common Lifecycle Pattern

Initialize Prober / Reporter. Request media permissions and enumerate devices.

Upstream passage · L51 ↗

High-Level Scenarios

Pre-join diagnostics page before Meeting SDK join action. Support workflow that captures structured report for customer troubleshooting.

Upstream passage · L60 ↗

Requirements and setup

Environment Variables

See references/environment-variables.md for optional .env keys and how to source values.

Upstream passage · L75 ↗

Limits and quality checks

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.

Upstream passage · L28 ↗

Start with a safe trial

  1. 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.
  2. 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.
  3. 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.
  4. 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.

Skill format and directory specification ↗

Read further in the source

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.

Source retrieved
Source commit
2574e29377c7173d0cecffef29a6ecbd7f8ccb5d
Source SHA-256
a2cbce7b0f77a91f9ea0580772b25b7807635e7c24d222370f6650a4ba1c699b
Back to the full Skill catalog