Debug Zoom
Triage failing Zoom auth, APIs, webhooks, SDK init, or MCP transport with ranked hypotheses and a short verification plan.
Overview
debug-zoom is an agent skill most often used in Operate (also Build integrations, Ship testing) that isolates Zoom failures across auth, API, webhook, SDK, and MCP and returns ranked hypotheses plus verification steps.
Install
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill debug-zoomWhat is this skill?
- 5-step workflow: identify failing layer, gather minimum evidence, 2–4 ranked hypotheses, route to deep Zoom skill refs,
- Layers covered: auth, API request, webhook, SDK init, media/session behavior, MCP transport
- Output bundle: likely failure layer, hypotheses, targeted fixes, verification checklist, relevant skill links
- Argument-driven entry via symptoms, error text, or failing flow
- Pairs with debug-zoom-integration, setup-zoom-oauth, and design-mcp-workflow related skills
- 2–4 ranked plausible causes per invocation
- 5-step debug workflow ending in verification
Adoption & trust: 834 installs on skills.sh; 19.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your Zoom integration fails with an opaque auth, API, webhook, SDK, or MCP error and you do not know which layer to fix first.
Who is it for?
Builders who have a reproducible Zoom failure and need structured triage before editing code or rotating credentials.
Skip if: Greenfield Zoom architecture decisions with no failure yet—use build or setup skills first—or non-Zoom bugs outside the listed layers.
When should I use this skill?
Auth, API, webhook, SDK, or MCP behavior is failing and you need a ranked hypothesis list plus verification steps.
What do I get? / Deliverables
You get a ranked hypothesis list, targeted fix steps, a verification checklist, and links to the most relevant Zoom reference skills for your failure layer.
- Ranked failure hypotheses by layer
- Targeted fix steps and verification checklist with skill deep links
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Operate because the skill is invoked when something already integrated is failing in production or during hardening. It isolates error layers (auth, API, webhook, SDK, MCP) and outputs fix steps plus verification—classic production error response.
Where it fits
Meeting SDK join succeeds locally but fails on staging—use layer isolation before changing OAuth scopes.
Pre-launch webhook signature tests fail—rank webhook vs auth causes and verify with a minimal payload replay.
Production Zoom MCP tool returns transport errors—separate MCP transport from REST auth using the verification checklist.
How it compares
Structured Zoom layer triage with verification—instead of scrolling all Zoom docs or generic “try again” debugging chat.
Common Questions / FAQ
Who is debug-zoom for?
Solo developers maintaining Zoom OAuth, REST, webhooks, SDK embeds, or Zoom-related MCP workflows when something regresses or breaks in a specific flow.
When should I use debug-zoom?
During Operate when auth or webhooks fail in production; during Build when SDK init or join flows break; during Ship when pre-release API or MCP transport tests fail—invoke with the exact error and platform.
Is debug-zoom safe to install?
Check the Security Audits panel on this page; the skill may prompt you to share errors or payloads—redact secrets and tokens before pasting into the agent.
SKILL.md
READMESKILL.md - Debug Zoom
# /debug-zoom > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md). Debug Zoom auth, API, webhook, SDK, or MCP issues without wandering through the entire docs set. ## Usage ```text /debug-zoom $ARGUMENTS ``` ## Workflow 1. Identify the failing layer: auth, API request, webhook, SDK init, media/session behavior, or MCP transport. 2. Ask for the minimum missing evidence: exact error, platform, request/response, event payload, or code path. 3. Produce 2-4 plausible causes ranked by likelihood. 4. Route to the most relevant deep references in `skills/`. 5. 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 - [debug-zoom-integration](../debug-zoom-integration/SKILL.md) - [setup-zoom-oauth](../setup-zoom-oauth/SKILL.md) - [design-mcp-workflow](../design-mcp-workflow/SKILL.md)