Zoom Probe SDK in Codex: Plan an Accessible Pre-Join Check
Plan what your app should check before a user joins a video session. Turn device and network results into clear screen states that you can test without a live meeting.
中文Setup for Codex (Zoom plugin)
Codex with the Zoom plugin. The walkthrough uses mocked browser, camera, and network results. Real device testing uses a browser and a development integration.
- Install Zoom through /plugins in Codex, then start a project session.
- Choose $probe-sdk explicitly. Have it open the plugin’s readiness workflow and sample diagnostic page before drafting screen states.
- Define which checks affect the join action and which should show a warning. Use mock outcomes for the first exercise.
Example task
Use $probe-sdk to make a state table for a virtual open house. Fixture A has a supported browser, camera ready, and adequate connection. Fixture B has a supported browser and adequate connection, but the camera permission was denied. Our event permits camera-off participants. Describe a visible next step for each fixture and the join behavior.Expected result
Both fixtures allow the attendee to continue. Fixture A reports devices ready. Fixture B includes a camera-off message and a way to recheck permission. The state table keeps the device outcome separate from the later join action.
Upstream documentation
Original SKILL.md on GitHub · MIT license · Source reviewed
Frequently asked question
Which failed checks should block joining?
Match blocking rules to the event requirements. Camera denial can be a warning at an event that accepts camera-off attendance. Use a test fixture for each allowed path and a clear explanation for any actual blocker.