setup-zoom-oauth
$
npx mdskill add openai/plugins/setup-zoom-oauthSets up OAuth for Zoom integrations by guiding through authentication decisions
- Helps configure OAuth when authentication is a critical integration blocker
- Relies on Zoom's OAuth API and related REST endpoints for token exchange
- Evaluates app model, grant type, and scope requirements based on user roles
- Routes users to detailed documentation after clarifying authentication context
SKILL.md
.github/skills/setup-zoom-oauthView on GitHub ↗
--- name: setup-zoom-oauth description: Use when setting up OAuth. --- # /setup-zoom-oauth Use this skill when auth is the blocker or when auth choices will shape the entire integration. ## Scope - App type selection - OAuth grant selection - Scope planning - Token exchange and refresh - Auth debugging and environment assumptions ## Workflow 1. Determine the app model and who is authorizing whom. 2. Choose the correct grant flow. 3. Identify minimum scopes for the user flow. 4. Define token storage and refresh behavior. 5. Route into the deepest relevant reference docs only after the above is clear. ## Primary References - [oauth](../oauth/SKILL.md) - [general](../general/SKILL.md) - [rest-api](../rest-api/SKILL.md) ## Common Mistakes - Picking a grant before clarifying the actor and tenant model - Asking for broad scopes before confirming the exact workflow - Forgetting refresh-token behavior and token lifecycle handling - Reusing an old refresh token after a successful refresh instead of storing the newly returned one - Treating auth failures as API failures without checking app configuration first
More from openai/plugins
- accessibility-and-inclusive-visualizationMake data visualizations accessible and inclusive. Use when the user needs chart or diagram accessibility guidance, text alternatives for complex visuals, color and contrast review, keyboard support, reduced-motion behavior for animation or parallax, or an accessibility QA workflow for exported figures, UML-like diagrams, and dashboards.
- agent-browserBrowser automation CLI for AI agents. Use when the user needs to interact with websites, verify dev server output, test web apps, navigate pages, fill forms, click buttons, take screenshots, extract data, or automate any browser task. Also triggers when a dev server starts so you can verify it visually.
- agent-browser-verifyAutomated browser verification for dev servers. Triggers when a dev server starts to run a visual gut-check with agent-browser — verifies the page loads, checks for console errors, validates key UI elements, and reports pass/fail before continuing.
- agents-sdkBuild AI agents on Cloudflare Workers using the Agents SDK. Load when creating stateful agents, durable workflows, real-time WebSocket apps, scheduled tasks, MCP servers, or chat applications. Covers Agent class, state management, callable RPC, Workflows integration, and React hooks. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
- ai-elementsAI Elements component library guidance — pre-built React components for AI interfaces built on shadcn/ui. Use when building chat UIs, message displays, tool call rendering, streaming responses, reasoning panels, or any AI-native interface with the AI SDK.
- ai-gatewayVercel AI Gateway expert guidance. Use when configuring model routing, provider failover, cost tracking, or managing multiple AI providers through a unified API.
- ai-generation-persistenceAI generation persistence patterns — unique IDs, addressable URLs, database storage, and cost tracking for every LLM generation
- ai-sdkVercel AI SDK expert guidance. Use when building AI-powered features — chat interfaces, text generation, structured output, tool calling, agents, MCP integration, streaming, embeddings, reranking, image generation, or working with any LLM provider.
- aiq-deploy|
- aiq-research|