Setup Zoom Oauth
Wire Zoom into your app with the right OAuth grant, scopes, and refresh-token handling before you call the REST API.
Overview
setup-zoom-oauth is an agent skill for the Build phase that implements Zoom authentication correctly—app type, OAuth grant, scopes, token refresh, and auth debugging—before REST integration work.
Install
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill setup-zoom-oauthWhat is this skill?
- 5-step workflow: actor model → grant → minimum scopes → token storage/refresh → deep reference docs
- Covers app type selection, OAuth grant selection, scope planning, and token exchange
- Explicit refresh-token rule: store the new refresh token after each successful refresh
- Routes to oauth, general, and rest-api reference skills only after auth design is clear
- Common-mistakes list for grant-before-tenant and scope creep
- 5-step auth workflow before deep API references
Adoption & trust: 849 installs on skills.sh; 19.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You want Zoom in your product but picking a grant or scopes at random will break tenants, refresh tokens, or production auth in ways that look like API bugs.
Who is it for?
Solo builders adding Zoom OAuth to a new or existing backend who have not finalized grant type, scopes, or refresh handling.
Skip if: Teams that already have a working Zoom integration with documented token storage and only need a single REST endpoint example.
When should I use this skill?
Setting up Zoom app credentials, choosing an OAuth grant, requesting scopes, handling token refresh, or debugging auth failures.
What do I get? / Deliverables
You leave with a clear actor model, grant, minimum scopes, and refresh storage rules so Zoom REST calls can be implemented without rework.
- Documented grant choice and scope list
- Token storage and refresh behavior spec
- Checklist separating auth config errors from API errors
Recommended Skills
Journey fit
Canonical shelf is Build → integrations because auth choices lock in how every Zoom API call will work during implementation. OAuth app type, grants, and scope planning are third-party integration setup, not generic backend CRUD.
How it compares
Use instead of copying a generic OAuth snippet without Zoom-specific grant and refresh-token lifecycle rules.
Common Questions / FAQ
Who is setup-zoom-oauth for?
Indie and solo developers wiring Zoom into APIs or agent workflows who need correct OAuth grants, scopes, and refresh behavior before coding endpoints.
When should I use setup-zoom-oauth?
During Build integrations when setting app credentials, choosing a grant, planning scopes, implementing token exchange and refresh, or debugging auth failures that are not REST bugs.
Is setup-zoom-oauth safe to install?
It is procedural documentation for auth design; review the Security Audits panel on this Prism page and treat client secrets and tokens according to your own secret-management policy.
SKILL.md
READMESKILL.md - Setup Zoom 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