Debug Zoom Integration
Skill Verified ActiveDebug broken Zoom implementations quickly. Use when auth, webhooks, SDK joins, MCP transport, or real-time media workflows are failing and you need to isolate the layer before proposing a fix.
Debug broken Zoom implementations quickly by identifying the root cause of failures across various layers of integration.
Features
- Guides diagnostic triage for Zoom integration failures
- Identifies likely failing layers (Auth, SDK, Media, Transport)
- Specifies evidence needed for effective debugging
- Provides ranked hypotheses and a short fix plan
Use Cases
- When Zoom authentication or app configuration is failing
- When SDK joins or platform mismatches occur
- When real-time media workflows or MCP transport are problematic
- To isolate the layer responsible for a Zoom integration failure before proposing a fix
Non-Goals
- Implementing fixes directly
- Debugging issues unrelated to Zoom integrations
- Providing a comprehensive guide to all possible Zoom features
Trust
- info:Issues AttentionOpened 29 issues in the last 90 days, with 4 closed, suggesting maintainer responsiveness may be slower than ideal for the volume of open issues.
Installation
First, add the marketplace
/plugin marketplace add anthropics/knowledge-work-plugins/plugin install zoom-plugin@knowledge-work-pluginsQuality Score
VerifiedTrust 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.