debug-zoom

anthropics/knowledge-work-plugins

Debug Zoom integration failures by isolating the layer and ranking hypotheses with verification steps.

What is debug-zoom?

Systematically diagnoses broken Zoom auth, API, webhook, SDK, or MCP integrations. Use this when you have a failing Zoom flow and need a ranked list of likely causes plus targeted verification steps to confirm the fix.

Identifies which layer is failing: auth, API request, webhook, SDK init, media/session, or MCP transport
Gathers minimum evidence needed to diagnose: error messages, platform details, request/response data, or code paths
Produces 2-4 ranked hypotheses ordered by likelihood
Routes to relevant deep-dive skills and Zoom references
Provides a short verification checklist to confirm the fix

How to install debug-zoom

npx skills add https://github.com/anthropics/knowledge-work-plugins --skill debug-zoom

Claude Code

Cursor

Windsurf

Cline

How to use debug-zoom

1.Run `/debug-zoom` with a description of the symptom, error message, or failing flow
2.Provide the failing layer if known (auth, API, webhook, SDK, media, or MCP)
3.Share relevant context: exact error text, platform/language, request/response samples, or code snippet
4.Review the ranked hypotheses and follow the targeted fix steps
5.Execute the verification checklist to confirm the issue is resolved

Use cases

Good for

OAuth token refresh failing during a Zoom meeting integration
Webhook events not being received after configuration
SDK initialization throwing cryptic errors on startup
API request returning 401 or 403 when credentials appear valid
MCP transport layer unable to communicate with Zoom servers

Who it's for

Backend engineers integrating Zoom APIs
Full-stack developers building Zoom meeting features
DevOps or platform engineers troubleshooting Zoom webhooks
Developers using Zoom SDKs in Node.js, Python, or other runtimes

debug-zoom FAQ

What if I don't know which layer is failing?

Describe the symptom (e.g., 'meeting won't start' or 'token refresh times out') and the skill will help isolate it by asking for error messages and request details.

Can this skill fix the issue directly?

No, it diagnoses the problem and routes you to the right references and verification steps. You implement the fix based on the hypotheses and targeted guidance.

What's the difference between debug-zoom and debug-zoom-integration?

debug-zoom is for rapid diagnosis of any Zoom layer failure; debug-zoom-integration is a deeper skill for end-to-end integration design and troubleshooting.

Do I need API credentials to use this skill?

Not to run the diagnostic. You may need credentials (OAuth tokens, API keys, webhook signing secrets) to verify fixes.

Full instructions (SKILL.md)

Source of truth, from anthropics/knowledge-work-plugins.

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

/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.