debug-zoom Skill
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. Published by anthropics in knowledge-work-plugins.
Decision snapshot
Is this a fit?
Documentation, Design and media, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
OAuth authentication, Credentials required
Copy skill directory
22 days ago · Apache-2.0 license
Access note: OAuth.
What is debug-zoom Skill?
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. Published by anthropics in knowledge-work-plugins. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Documentation
- Design and media
- Documentation use cases
- Design and media use cases
Declared skill metadata
- Source file: partner-built/zoom-plugin/skills/debug-zoom/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
- OAuth
Requirements and access
Security and permissions
Review permissions before connecting any MCP server to an agent. Pay special attention to whether it can read local files, write data, call external services, or perform destructive actions.
When to use debug-zoom Skill
- Use it for documentation.
- Use it for design and media.
Built with
Editorial notes
Source
- Creator: anthropics
- Repository: anthropics/knowledge-work-plugins
- Skill file: partner-built/zoom-plugin/skills/debug-zoom/SKILL.md
What 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 a ranked hypothesis list plus verification steps.
Skill instructions
/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 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 - setup-zoom-oauth - design-mcp-workflow
Verified compatibility and discovery
Frequently asked questions
What is debug-zoom?
debug-zoom is a open-source AI agent skill with Copy skill directory. Debug a broken Zoom integration by isolating the failure point and routing into the right Zoom references.
Who is debug-zoom best for?
debug-zoom is best for reusing agent instructions, scripts, and references, documentation workflows, design and media workflows.
How do I install debug-zoom?
Install or run debug-zoom using Copy skill directory. Check debug-zoom for the latest setup command.
Is debug-zoom actively maintained?
debug-zoom may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
