Debug Zoom
- 1.4k installs
- 23.1k repo stars
- Updated July 28, 2026
- anthropics/knowledge-work-plugins
debug-zoom is an agent skill for 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.
About
The debug-zoom skill is designed for 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. /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. Invoke when the user auth, API, webhook, SDK, or MCP behavior is failing and you need a ranked hypothesis list plus verification steps.
- Most likely failure layer.
- Ranked hypotheses.
- Targeted fix steps.
- Verification checklist.
- Relevant skill links.
Debug Zoom by the numbers
- 1,409 all-time installs (skills.sh)
- +82 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Ranked #823 of 16,659 AI & Agent Building skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
debug-zoom capabilities & compatibility
- Capabilities
- most likely failure layer · ranked hypotheses · targeted fix steps · verification checklist
What debug-zoom says it does
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
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
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill debug-zoomAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.4k |
|---|---|
| repo stars | ★ 23.1k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 28, 2026 |
| Repository | anthropics/knowledge-work-plugins ↗ |
How do I 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?
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.
Who is it for?
Developers using debug zoom workflows documented in SKILL.md.
Skip if: Skip when the task falls outside debug-zoom scope or needs a different stack.
When should I use this skill?
User auth, API, webhook, SDK, or MCP behavior is failing and you need a ranked hypothesis list plus verification steps.
What you get
Completed debug-zoom workflow with documented commands, files, and expected deliverables.
- Ranked failure hypothesis list
- Isolated failing layer
- Targeted verification steps
By the numbers
- Covers 5 Zoom failure layers: auth, API, webhook, SDK, and media/session
Files
/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 $ARGUMENTSWorkflow
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
- setup-zoom-oauth
- design-mcp-workflow
Related skills
Setup Matt Pocock SkillsScaffold the per-repo configuration that Matt Pocock’s engineering agent skills rely on so they understand the issue tracker, triage labels, and domain documentation la462k185k
Lark Skill MakerQuickly turn any Lark/Feishu OpenAPI call or multi-step workflow into a reusable agent skill with its own SKILL.md.379k15.8k
CavemanSlash token usage by roughly 75% while keeping every technical detail intact when working with Claude Code, Cursor or similar agents.378k92.5k
Lark AppsConnect Claude, Cursor or custom agents directly to Lark (Feishu) for messaging, document automation, approval workflows and enterprise data access.375k
Running Claude Code Via Litellm CopilotRun Claude Code at a fraction of the cost by routing requests through LiteLLM to the GitHub Copilot Chat API.270k72
Codex PetGenerate a complete Codex Pet spritesheet and metadata from one reference image without needing an OpenAI key or Codex Pro.246k8How it compares
Pick debug-zoom over integration planning skills when code exists and you need ranked failure hypotheses rather than a new architecture blueprint.
FAQ
What does debug-zoom do?
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.
When should I use debug-zoom?
User auth, API, webhook, SDK, or MCP behavior is failing and you need a ranked hypothesis list plus verification steps.
Is debug-zoom safe to install?
Review the Security Audits panel on this page before installing in production.