debug-zoom

Diagnose Zoom integration failures with ranked hypotheses and verification steps.

7|2|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/zoom/zoom-plugin --skill debug-zoom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-zoom
Source: https://github.com/zoom/zoom-plugin/tree/main/skills/debug-zoom
Command: npx skills add https://github.com/zoom/zoom-plugin --skill debug-zoom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debug Zoom auth, API, webhook, SDK, or MCP issues without wandering through the entire docs set.

Core Features & Use Cases

  • Identify the failing layer: auth, API request, webhook, SDK init, or MCP transport.
  • Produce 2-4 plausible causes ranked by likelihood.
  • Route to the most relevant deep references in skills/.
  • Provide a short verification plan so the user can confirm the fix.

Quick Start

Describe the symptoms and generate 2-4 ranked hypotheses with verification steps.

Frequently Asked Questions about debug-zoom

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug Zoom OAuth authentication failures?

Debug Zoom OAuth authentication failures by generating a ranked list of plausible hypotheses targeting token generation, scope mismatches, or credential errors. The skill prioritizes likely causes and provides verification steps using error messages and payload details to confirm the root cause.

Why is my Zoom webhook not receiving event notifications?

Zoom webhook failures are diagnosed by evaluating hypotheses around endpoint URL validation, event subscription configuration, and payload signature verification. The skill ranks these potential causes by likelihood and outlines a short verification plan to test endpoint responsiveness and event payload accuracy.

What is the best way to troubleshoot Zoom SDK initialization errors?

Troubleshoot Zoom SDK initialization errors by identifying the failing transport or initialization layer and producing 2-4 ranked hypotheses. The skill focuses on platform details and error outputs to validate each hypothesis, routing you to the most relevant references for confirming the fix.

How do I identify the failing layer in a Zoom API integration?

Identify the failing layer in a Zoom API integration by isolating the issue across authentication, API requests, webhooks, SDK initialization, or MCP transport. The skill enforces structured reasoning to pinpoint the exact failure point and provides actionable verification steps.

Can I use this to debug Zoom MCP transport issues?

Yes, you can debug Zoom MCP transport issues by generating prioritized hypotheses focused on transport channel failures. The skill scopes common failure scenarios across transport layers and provides guidance to validate each hypothesis against minimal evidence like error details.

What should I do when my Zoom API request returns an error?

When a Zoom API request returns an error, generate 2-4 ranked hypotheses focused on authentication, API requests, or SDK initialization. The skill guides you to validate each hypothesis against minimal evidence such as error messages and payloads, ensuring structured reasoning to confirm the fix.