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.
Works with
--- 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. license: Apache-2.0 --- # /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)
More Debugging skills
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
explore-code
lllllllama/rigorpilot-skills
Rigor Improve implementation leaf skill for auditable candidate implementation in deep learning research repositories. Use when the researcher explicitly authorizes exploratory work on an isolated branch or worktree to transplant modules, adapt a backbone, add LoRA or adapter layers, replace a head, or stitch together meaningful low-risk migration ideas with rollback-aware records in `explore_outputs/`. Do not use for end-to-end exploration orchestration on top of `current_research`, trusted baseline reproduction, conservative debugging, environment setup, verified contribution claims, or default repository analysis.
safe-debug
lllllllama/rigorpilot-skills
Rigor Debug / Rigor Audit skill for deep learning research work. Use when the user pastes a traceback, terminal error, CUDA OOM, checkpoint load failure, shape mismatch, NaN loss symptom, or training failure and wants conservative diagnosis before any patching, with debug fixes clearly separated from research contributions. Do not use for broad refactoring, speculative adaptation, automatic exploratory patching, or general repository familiarization.
