Debug Zoom Skill for Claude
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.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/anthropics/knowledge-work-plugins --skill debug-zoomThe instruction itself
5 sections, as written by the author/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 $ARGUMENTS
Workflow
- Identify the failing layer: auth, API request, webhook, SDK init, media/session behavior, or MCP transport.
- Ask for the minimum missing evidence: exact error, platform, request/response, event payload, or code path.
- Produce 2-4 plausible causes ranked by likelihood.
- Route to the most relevant deep references in
skills/. - 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
Other skills for the same job
different authors, same section of the catalogue
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Vendor-agnostic lab automation framework. Use when controlling multiple equipment types (Hamilton, Tecan, Opentrons, plate readers, pumps) or needing unified programming across different vendors. Best for complex workflows, multi-vendor setups, simulation. For Opentrons-only protocols with official API, opentrons-integration may be simpler.
How to use it
Take anthropics/debug-zoom from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.