debug-zoom
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.
Security Assessment
About debug-zoom
Debug Zoom is a diagnostic routing skill for troubleshooting broken Zoom integrations. Rather than wandering through the entire Zoom documentation set, it isolates the failing layer, produces a ranked list of likely causes, and routes the developer to the most relevant deep-reference skills, then gives a short verification plan. It solves the frustration of debugging opaque failures across auth, API, webhook, SDK, and MCP behavior.
Given a symptom, error, or failing flow as its argument, the skill runs a five-step workflow: identify the failing layer (auth, API request, webhook, SDK init, media/session behavior, or MCP transport); ask for the minimum missing evidence such as the exact error, platform, request/response, or event payload; produce two to four plausible causes ranked by likelihood; route to the most relevant references in the plugin's `skills/` directory; and provide a short verification plan to confirm the fix. Its output is structured: most likely failure layer, ranked hypotheses, targeted fix steps, a verification checklist, and links to related skills such as debug-zoom-integration, setup-zoom-oauth, and design-mcp-workflow.
It targets developers whose Zoom auth, API, webhook, SDK, or MCP integration is failing and who want a fast, evidence-driven triage instead of a broad documentation search. Typical use cases are diagnosing OAuth failures, webhooks not firing, SDK initialization errors, and MCP transport problems. This is a lightweight, single-file guidance skill that orchestrates diagnosis and hands off to specialized references; it does not itself perform any privileged or destructive actions.
FAQ
What does this skill do?
It triages a broken Zoom integration by isolating the failing layer, producing a ranked list of likely causes, routing to the right reference skills, and giving a verification plan to confirm the fix.
What input does it need?
A description of the symptoms, error, or failing flow. It then asks for the minimum missing evidence such as the exact error, platform, request/response, or event payload.
Which failure layers can it diagnose?
Auth, API requests, webhooks, SDK initialization, media/session behavior, and MCP transport.
What does the output look like?
The most likely failure layer, two to four ranked hypotheses, targeted fix steps, a verification checklist, and links to relevant skills like debug-zoom-integration and setup-zoom-oauth.
Does it fix issues automatically?
No. It is a diagnostic and routing helper that ranks causes and points to deep references and verification steps; the actual fixes are applied by the developer using the linked skills.
Install debug-zoom
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
anthropics/knowledge-work-plugins