Debug Zoom Integration
Triage failing Zoom OAuth, REST, webhooks, Meeting/Video SDK, RTMS, or Zoom MCP implementations with a fixed evidence checklist and ranked hypotheses.
Overview
Debug Zoom Integration is an agent skill most often used in Build (also Operate) that isolates which layer of a broken Zoom stack—auth, API, webhooks, SDK, or MCP—is failing before proposing a fix.
Install
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill debug-zoom-integrationWhat is this skill?
- Five-layer triage order: auth config → requests/events → SDK init → media/session → MCP transport
- Evidence checklist: exact errors, platform/SDK, payloads, reproducibility
- Routes to sibling skills: oauth, rest-api, webhooks, meeting-sdk, video-sdk, rtms, zoom-mcp
- Output contract: failing layer, ranked hypotheses, short fix plan, verification steps
- Designed for post-build failures—not greenfield Zoom product design
- 5-step triage order
- 7 reference skill routes
Adoption & trust: 830 installs on skills.sh; 19.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your Zoom auth, webhooks, SDK join, or MCP workflow fails and you cannot tell whether the bug is credentials, payloads, platform mismatch, or media/session behavior.
Who is it for?
Indie developers mid-integration when Zoom errors are opaque and span multiple SDK or MCP surfaces.
Skip if: Greenfield Zoom app planning with no errors yet, or non-Zoom video providers.
When should I use this skill?
When Zoom auth, webhooks, SDK joins, MCP transport, or real-time media workflows are failing and you need to isolate the layer before proposing a fix.
What do I get? / Deliverables
You get a labeled failing layer, ordered hypotheses, a short fix plan, and concrete verification steps routed to the right Zoom reference skill.
- Identified failing layer
- Ranked hypotheses and fix plan
- Verification step list
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Zoom work is built during integrations; this skill is shelved there as the canonical fix playbook when an implementation already exists but breaks. Real-time meeting and API integrations belong on the integrations subphase even when debugging spans auth through media layers.
Where it fits
OAuth succeeds but REST meeting create returns 401—run auth-then-request triage before editing webhook handlers.
Staging webhook deliveries fail verification while local curl works—isolate event payload and signing secret layer.
Production MCP tool calls hang while SDK meetings still join—check MCP transport assumptions after media layer rules out.
Video SDK init fails on one platform only—collect SDK/runtime evidence at step three of the ordered checklist.
How it compares
Use this layered triage skill instead of guessing fixes from generic stack traces across OAuth, REST, and SDK docs separately.
Common Questions / FAQ
Who is debug-zoom-integration for?
Solo builders and small teams who already implemented Zoom OAuth, APIs, webhooks, SDKs, or Zoom MCP and need structured isolation before changing code.
When should I use debug-zoom-integration?
In Build while finishing Zoom integrations when joins or webhooks fail; in Operate when production Zoom automation breaks; whenever auth, SDK, RTMS, or MCP transport errors need evidence-first triage.
Is debug-zoom-integration safe to install?
It is a diagnostic procedure only—avoid pasting live secrets into chats; review the Security Audits panel on this Prism page for the parent plugin package.
SKILL.md
READMESKILL.md - Debug Zoom Integration
# Debug Zoom Integration Use this skill when the user already built something and it is failing. ## Triage Order 1. Auth and app configuration 2. Request construction or event verification 3. SDK initialization or platform mismatch 4. Media/session behavior 5. MCP transport and capability assumptions ## Evidence To Request - Exact error text - Platform and SDK/runtime - Relevant request or payload sample - What worked versus what failed - Whether the issue is reproducible or intermittent ## Reference Routing - [oauth](../oauth/SKILL.md) - [rest-api](../rest-api/SKILL.md) - [webhooks](../webhooks/SKILL.md) - [meeting-sdk](../meeting-sdk/SKILL.md) - [video-sdk](../video-sdk/SKILL.md) - [rtms](../rtms/SKILL.md) - [zoom-mcp](../zoom-mcp/SKILL.md) ## Output - Most likely failing layer - Ranked hypotheses - Short fix plan - Verification steps