Zoom Debug Skill in Codex for an SDK Initialization Failure
Identify the failing layer of a Zoom integration from a small set of reproducible facts and a short verification checklist.
中文Setup for Codex (Zoom plugin)
Use the full Zoom plugin in Codex. The example uses an artificial console message and a local capture with project identifiers omitted.
- In Codex, open /plugins and install Zoom. Use the full plugin package so its sibling skills and references are available.
- Invoke the bundled skill as $debug-zoom in a scratch workspace. Keep the example on the local or demo inputs described below.
Example task
Invoke $debug-zoom with: Account connection succeeds in the test browser, but a refreshed demo test page renders a blank in-client panel. The mock console says SDK init did not run, and there was no network action. Ask for two hypotheses and the first local verification step.Expected result
The diagnosis starts with SDK initialization or client running context. It suggests checking the initialized state before investigating remote API or event delivery.
Upstream documentation
Original SKILL.md on GitHub · MIT license · Source reviewed
Frequently asked question
What information is most useful when opening a debug run?
Provide the affected client, SDK and version, a sanitized error, the smallest reproduction, and one comparable scenario that succeeds.