setup-zoom-oauth — Claude skill: what it does, how to install
A skill that walks through Zoom OAuth setup: app type, grant flow, scopes, token exchange and refresh. Useful when auth blocks the integration.
npx skills add openai/plugins --skill setup-zoom-oauth -a codexWhat setup-zoom-oauth does
The skill kicks in when auth is the blocker, or when the choice of auth method will shape the whole integration. It runs a five-step workflow: pin down the app model and who is authorizing whom, pick the right grant flow, identify the minimum scopes for the user flow, define token storage and refresh behaviour, and only then open the reference docs.
Those references are three sibling skills: oauth, general and rest-api. The skill itself does not issue tokens or call the API. It sets the order of decisions and points you at the right place for details. A separate section lists common mistakes: picking a grant before the actor and tenant model is clear, asking for broad scopes up front, forgetting the token lifecycle.
One mistake there is worth reading twice. After a successful refresh you must not reuse the old refresh token — store the newly returned one instead. And when auth fails, the skill says to check app configuration before blaming the API.
What it helps with
- pick a grant flow that matches the app and tenant model
- narrow scopes down to the exact user flow
- define token storage and refresh behaviour
- debug a failing auth flow before touching API calls
- store the new refresh token instead of reusing the old one
Example prompts for the agent
- help me set up Zoom OAuth in my app
- which grant flow fits a user authorizing inside someone else's account
- Zoom auth is failing — where do I start checking
How to install setup-zoom-oauth
1Skills CLI (Vercel)
npx skills add openai/plugins --skill setup-zoom-oauth -a codex2Manually: put the files in place
.agents/skills/setup-zoom-oauth/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add openai/plugins --skill setup-zoom-oauth -a claude-code2Manually: put the files in place
~/.claude/skills/setup-zoom-oauth/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/setup-zoom-oauth/
Manually: put the files in place
.cursor/skills/setup-zoom-oauth/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install openai/plugins setup-zoom-oauth2Manually: put the files in place
.github/skills/setup-zoom-oauth/SKILL.mdPlatform CLI
gemini skills install https://github.com/openai/plugins --path plugins/zoom/skills/setup-zoom-oauthManually: put the files in place
.devin/skills/setup-zoom-oauth/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: Codex skills: how to install, where they live, how to call them
Questions about setup-zoom-oauth
How do I install setup-zoom-oauth in Claude?
Run npx skills add openai/plugins --skill setup-zoom-oauth -a codex. The skill file then lives at .agents/skills/setup-zoom-oauth/SKILL.md.
What does setup-zoom-oauth do?
It guides you through Zoom auth setup: app type selection, grant flow, scope planning, token exchange and refresh. It also covers common debugging mistakes.
What breaks most often during setup?
The refresh token. Reusing the old one after a successful refresh is wrong — store the new value. Another frequent cause is choosing a grant before the actor and tenant model is settled.
Source text
SKILL.md · MIT
--- 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
© Zoom · MIT · openai/plugins
