debug-zoom-integration
Debug broken Zoom implementations quickly. Use when auth, webhooks, SDK joins, MCP transport, or real-time media workflows are failing and you need to isolate the layer before proposing a fix.
Security Assessment
About debug-zoom-integration
The debug-zoom-integration skill is a diagnostic playbook for troubleshooting broken Zoom integrations. It addresses the common situation where a developer has already built something against Zoom's platform, such as OAuth authentication, webhooks, SDK meeting joins, MCP transport, or real-time media workflows, and it is failing. Rather than jumping to a guessed fix, the skill guides Claude to isolate which layer is actually at fault before proposing a solution.
The skill works by applying a fixed triage order: authentication and app configuration first, then request construction or event verification, then SDK initialization or platform mismatch, then media and session behavior, and finally MCP transport and capability assumptions. It also prescribes the evidence to collect first, including exact error text, the platform and SDK/runtime in use, a relevant request or payload sample, a comparison of what worked versus what failed, and whether the problem is reproducible or intermittent. It then routes to sibling reference skills (oauth, rest-api, webhooks, meeting-sdk, video-sdk, rtms, zoom-mcp) for depth, and produces a ranked set of hypotheses, the most likely failing layer, a short fix plan, and verification steps.
This is a thin, routing-oriented catalogue entry aimed at developers building on Zoom who are stuck debugging. It contains no executable code or credentials of its own; it is a structured debugging methodology that leans on the broader Zoom plugin's other skills for implementation detail. It is most useful as the entry point when an existing Zoom build misbehaves and the developer needs to narrow the cause systematically.
FAQ
When should I use this skill?
Use it when you have already built a Zoom integration and it is failing, for example broken auth, webhooks that do not verify, SDK joins that fail, or MCP transport problems. It is a debugging aid, not a build guide.
What information should I have ready?
The skill asks for the exact error text, your platform and SDK/runtime, a relevant request or payload sample, what worked versus what failed, and whether the issue is reproducible or intermittent.
Does this skill fix the problem for me?
It isolates the most likely failing layer and gives ranked hypotheses, a short fix plan, and verification steps. For implementation depth it routes you to companion skills such as oauth, rest-api, webhooks, meeting-sdk, video-sdk, rtms, and zoom-mcp.
Is this a standalone tool?
No. It is a triage and routing skill within the Zoom partner-built plugin and depends on the sibling reference skills for the actual technical detail. It is marked not user-invocable, meaning it is meant to be routed to rather than called directly.
Install debug-zoom-integration
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
anthropics/knowledge-work-plugins