name: debug-zoom description: Debug a broken Zoom integration by isolating the failure point and routing into the right Zoom references. Use when auth, API, webhook, SDK, or MCP behavior is failing and you need a ranked hypothesis list plus verification steps. argument-hint: "<symptoms, error, or failing flow>"
/debug-zoom
If you see unfamiliar placeholders or need to check which tools are connected, see
CONNECTORS.md.
Debug Zoom auth, API, webhook, SDK, or MCP issues without wandering through the entire docs set.
Usage
text
/debug-zoom $ARGUMENTS
Workflow
- Identify the failing layer: auth, API request, webhook, SDK init, media/session behavior, or MCP transport.
- Ask for the minimum missing evidence: exact error, platform, request/response, event payload, or code path.
- Produce 2-4 plausible causes ranked by likelihood.
- Route to the most relevant deep references in
skills/. - Give a short verification plan so the user can confirm the fix.
Output
- Most likely failure layer
- Ranked hypotheses
- Targeted fix steps
- Verification checklist
- Relevant skill links
Related Skills