Debug Zoom
Skill ActiveDebug 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.
Debug failing Zoom integrations by isolating issues and providing targeted solutions and verification steps.
Features
- Isolates failure layers (auth, API, webhook, SDK, media, MCP)
- Generates ranked hypotheses for failures
- Provides targeted fix steps
- Includes verification checklists
- Links to relevant Zoom references and related skills
Use Cases
- When Zoom authentication is failing
- When Zoom API requests return errors
- When Zoom webhooks are not firing
- When the Zoom SDK initialization fails
Non-Goals
- General Zoom troubleshooting unrelated to integration failures
- Providing comprehensive Zoom documentation
- Fixing issues outside of authentication, API, webhook, SDK, or MCP behavior
Trust
- warning:Issues AttentionThere are 29 open issues and 4 closed issues in the last 90 days, indicating a low closure rate and potential maintainer responsiveness issues.
Practical Utility
- info:Usage examplesWhile the skill outlines usage, it lacks concrete, end-to-end examples with observable outcomes.
- info:Edge casesThe skill outlines failure modes but does not explicitly document recovery steps for each.
Installation
First, add the marketplace
/plugin marketplace add anthropics/knowledge-work-plugins/plugin install zoom-plugin@knowledge-work-pluginsQuality Score
Trust Signals
Similar Extensions
Node Connect
100Diagnose OpenClaw Android, iOS, or macOS node pairing, QR/setup code, route, auth, and connection failures.
Openclaw Debugging
100Debug OpenClaw model, provider, tool-surface, code-mode, streaming, and live/Crabbox behavior by choosing the right logs, probes, and proof path before changing code.
Systematic Debugging
100Systematic debugging methodology emphasizing root cause analysis over quick fixes
Troubleshooting
100Uses Chrome DevTools MCP and documentation to troubleshoot connection and target issues. Trigger this skill when list_pages, new_page, or navigate_page fail, or when the server initialization fails.
Root Cause Tracing
99Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior
Query Agent Events
99Bug-investigation tool for the Netdata agent-events ingestion namespace -- triage crashes, panics, fatals across the fleet by downloading events of interest and clustering locally. Covers the three transports (Cloud API and direct agent API are primary; ssh is operator-only), the verified AE_* field map and enum meanings, the dedup model (23h client-side per agent and event signature), the after-the-fact event timing (POST only on agent restart), and the Netdata systemd-journal plugin multi-value filter syntax (FIELD in A, B, C) AND ... Use when investigating crashes / panics / fatals; when grepping for events touching a specific function or file or version; when looking for regressions across versions; when an agent is reported crashing in a way you want to triage. Ships scripts get-events.sh and analyze-events.sh that fetch events with index-friendly filters and compute group-by stats. Defaults to last 24 hours and to the latest stable plus latest 2-3 nightlies.