Debug a Zoom Integration in Codex with a Triage Matrix
Compare two Zoom integration runs, locate the first difference, and choose the correct source references for a targeted check.
中文Setup for Codex (Zoom plugin)
Use the complete Zoom plugin. The example is a sanitized developer-side mock with request status and client behavior only.
- 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-integration in a scratch workspace. Keep the example on the local or demo inputs described below.
Example task
Invoke $debug-zoom-integration with a fixture: the expected event reaches the test adapter and receives a successful response, but the UI still shows Pending. The event handler writes state=done and the frontend polls a mock record with state='pending'. Ask for the likely failing layer and a local verification step.Expected result
The investigation checks the boundary between stored state and frontend retrieval. A local test that polls the same event ID after the state update distinguishes stale or mismatched records.
Upstream documentation
Original SKILL.md on GitHub · MIT license · Source reviewed
Frequently asked question
How is this useful when the exact cause is uncertain?
Ask for a ranked list of hypotheses and one test that separates them. Collect the next missing piece of evidence before making broader changes.