Generated banner for Zoom General
Generated logo for Zoom General

Zoom General

AnthropicOfficialCreated by ZoomDistributed by Anthropic

  • Skill
  • Meta (authoring, orchestration, planning, memory)
  • Agent tooling
  • MIT
  • Medium risk

From the author

Cross-product Zoom reference skill. Use after the workflow is clear when you need shared platform guidance, app-model comparisons, authentication context, scopes, marketplace considerations, or API-vs-MCP routing.
— the description by Zoom

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The zoom-general skill serves as the primary entry point and classification layer for developers working with the Zoom platform. It provides a structured framework to identify the correct Zoom product, SDK, or API path based on user intent. It includes logic for routing complex queries, chaining multiple skills (such as combining REST APIs with OAuth and webhooks), and resolving ambiguities between deterministic automation and AI-driven agentic workflows.

What it does

  • Classifies developer queries to identify the appropriate Zoom product or SDK.
  • Provides a routing matrix to distinguish between REST API, MCP, and SDK use cases.
  • Offers guidance on choosing the correct Zoom app type (General, S2S, or Webhook-only).
  • Facilitates skill chaining for multi-step integrations like OAuth and webhook setups.
  • Provides decision frameworks for API vs. MCP and SDK vs. REST implementation paths.
  • Acts as a central index for all specialized Zoom developer skills.

When to use it

  • When you are unsure which Zoom SDK or API is required for your project.
  • When you need to determine if your task requires REST APIs, MCP tools, or a hybrid approach.
  • When planning a complex integration that involves authentication, webhooks, and API orchestration.
  • When you need to compare different Zoom app types to match your architectural requirements.
  • When you need to resolve ambiguity between similar Zoom products like Meeting SDK and Video SDK.

Advantages

  • Reduces development friction by directing users to the most relevant documentation and skills.
  • Ensures architectural consistency by enforcing standard routing patterns.
  • Simplifies complex decision-making through clear matrices and guardrails.
  • Promotes best practices for authentication and event-driven design.
  • Provides a unified entry point for navigating the entire Zoom developer ecosystem.

Usage examples

“I want to build a custom video UI for a Zoom meeting on the web, what should I use?”
The skill identifies the requirement for a custom UI around a real meeting and routes the user to the zoom-meeting-sdk-web-component-view skill.
“Should I use the REST API or MCP for my AI agent?”
The skill provides the API vs. MCP routing matrix, explaining that REST is for deterministic automation while MCP is for dynamic AI tool orchestration.
“How do I set up a server-side integration that handles meetings and webhooks?”
The skill suggests the Rivet SDK for scaffolding or chains the zoom-rest-api, zoom-oauth, and zoom-webhooks skills.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/anthropics/zoom-general/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip zoom-general.zip -d .agents/skills

Documentation by Zoom

Zoom General (Cross-Product Skills)

Background reference for cross-product Zoom questions. Prefer the workflow skills first, then use this file for shared platform guidance and routing detail.

How zoom-general Routes a Complex Developer Query

Use zoom-general as the classifier and chaining layer:

  1. detect product signals in the query

  2. pick one primary skill

  3. attach secondary skills for auth, events, or deployment edges

  4. ask one short clarifier only when two routes match with similar confidence

Minimal implementation:

type SkillId =
  | 'zoom-general'
  | 'zoom-rest-api'
  | 'zoom-webhooks'
  | 'zoom-oauth'
  | 'zoom-meeting-sdk-web-component-view'
  | 'zoom-video-sdk'
  | 'zoom-mcp';

const hasAny = (q: string, words: string[]) => words.some((w) => q.includes(w));

function detectSignals(rawQuery: string) {
  const q = rawQuery.toLowerCase();
  return {
    meetingCustomUi: hasAny(q, ['zoom meeting', 'custom ui', 'component view', 'embed meeting']),
    customVideo: hasAny(q, ['video sdk', 'custom video session', 'peer-video-state-change']),
    restApi: hasAny(q, ['rest api', '/v2/', 'create meeting', 'list users', 's2s oauth']),
    webhooks: hasAny(q, ['webhook', 'x-zm-signature', 'event subscription', 'crc']),
    oauth: hasAny(q, ['oauth', 'pkce', 'token refresh', 'account_credentials']),
    mcp: hasAny(q, ['zoom mcp', 'agentic retrieval', 'tools/list', 'semantic meeting search']),
  };
}

function pickPrimarySkill(s: ReturnType<typeof detectSignals>): SkillId {
  if (s.meetingCustomUi) return 'zoom-meeting-sdk-web-component-view';
  if (s.mcp) return 'zoom-mcp';
  if (s.restApi) return 'zoom-rest-api';
  if (s.customVideo) return 'zoom-video-sdk';
  return 'zoom-general';
}

function buildChain(primary: SkillId, s: ReturnType<typeof detectSignals>): SkillId[] {
  const chain = [primary];
  if (s.oauth && !chain.includes('zoom-oauth')) chain.push('zoom-oauth');
  if (s.webhooks && !chain.includes('zoom-webhooks')) chain.push('zoom-webhooks');
  return chain;
}

Example:

  • Create a meeting, configure webhooks, and handle OAuth token refresh -> zoom-rest-api -> zoom-oauth -> zoom-webhooks

  • Build a custom video UI for a Zoom meeting on web -> zoom-meeting-sdk-web-component-view

For the full TypeScript implementation and handoff contract, use references/routing-implementation.md.

Choose Your Path

I want to...Use this skill
Build a custom web UI around a real Zoom meetingzoom-meeting-sdk-web-component-view
Build deterministic automation/configuration/reporting with explicit request controlzoom-rest-api
Receive event notifications (HTTP push)zoom-webhooks
Receive event notifications (WebSocket, low-latency)zoom-websockets
Embed Zoom meetings in my appzoom-meeting-sdk
Build custom video experiences (Web, React Native, Flutter, Android, iOS, macOS, Unity, Linux)zoom-video-sdk
Build an app that runs inside Zoom clientzoom-apps-sdk
Transcribe uploaded or stored media with AI Services Scribescribe
Access live audio/video/transcripts from meetingszoom-rtms
Enable collaborative browsing for supportzoom-cobrowse-sdk
Build Contact Center apps and channel integrationscontact-center
Build Virtual Agent web/mobile chatbot experiencesvirtual-agent
Build Zoom Phone integrations (Smart Embed, Phone API, webhooks, URI flows)phone
Build Team Chat apps and integrationszoom-team-chat
Build server-side integrations with Rivet (auth + webhooks + APIs)rivet-sdk
Run browser/device/network preflight diagnostics before joinprobe-sdk
Add pre-built UI components for Video SDKzoom-ui-toolkit
Implement OAuth authentication (all grant types)zoom-oauth
Build AI-driven tool workflows (AI Companion/agents) over Zoom datazoom-mcp
Build AI-driven Whiteboard workflows over Zoom Whiteboard MCPzoom-mcp/whiteboard
Build enterprise AI systems with stable API core + AI tool layerzoom-rest-api + zoom-mcp

Planning Checkpoint: Rivet SDK (Optional)

When a user starts planning a server-side integration that combines auth + webhooks + API calls, ask this first:

  • Rivet SDK is a Node.js framework that bundles Zoom auth handling, webhook receivers, and typed API wrappers.

  • Do you want to use Rivet SDK for faster scaffolding, or do you prefer a direct OAuth + REST implementation without Rivet?

Routing after answer:

  • If user chooses Rivet: chain rivet-sdk + oauth + rest-api.

  • If user declines Rivet: chain oauth + rest-api (+ webhooks or product skill as needed).

SDK vs REST Routing Matrix (Hard Stop)
User intentCorrect pathDo not route to
Embed Zoom meeting in app UIzoom-meeting-sdkREST-only join_url flow
Build custom web UI for a real Zoom meetingzoom-meeting-sdk-web-component-viewzoom-video-sdk
Build custom video UI/session appzoom-video-sdkMeeting SDK or REST meeting links
Get browser join links / manage meeting resourceszoom-rest-apiMeeting SDK join implementation

Routing guardrails:

  • If user asks for SDK embed/join behavior, stay in SDK path.

  • If the prompt says meeting plus custom UI/video/layout/embed, prefer zoom-meeting-sdk-web-component-view.

  • Only use zoom-video-sdk when the user is building a custom session product rather than a Zoom meeting.

  • Only use REST path for resource management, reporting, or link distribution unless user explicitly requests a mixed architecture.

  • For executable classification/chaining logic and error handling, see references/routing-implementation.md.

API vs MCP Routing Matrix (Hard Stop)
User intentCorrect pathWhy
Deterministic backend automation, account/user configuration, reporting, scheduled jobszoom-rest-apiExplicit request/response control and repeatable behavior
AI agent chooses tools dynamically, cross-platform AI tool interoperabilityzoom-mcpMCP is optimized for dynamic tool discovery and agentic workflows
Enterprise AI architecture (stable core + adaptive AI layer)zoom-rest-api + zoom-mcpAPIs run core system actions; MCP exposes curated AI tools/context

Routing guardrails:

  • Do not replace deterministic backend APIs with MCP-only routing.

  • Do not force raw REST-first routing when the task is AI-agent tool orchestration.

  • Prefer hybrid routing when the user needs both stable automation and AI-driven interactions.

  • MCP remote server works over Streamable HTTP/SSE; use this path when the target client/agent supports MCP transports (for example Claude or VS Code).

  • Do not design per-tenant custom MCP endpoint provisioning; Zoom MCP endpoints are shared at instance/cluster level.

  • Source: https://developers.zoom.us/docs/mcp/library/resources/apis-vs-mcp/

Ambiguity Resolution (Ask Before Routing)

When a prompt matches both API and MCP paths with similar confidence, ask one short clarifier before execution:

  • Do you want deterministic REST API automation, AI-agent MCP tooling, or a hybrid of both?

Then route as:

  • REST answer → zoom-rest-api

  • MCP answer → zoom-mcp

  • Hybrid answer → zoom-rest-api + zoom-mcp

MCP Availability and Topology Notes
  • Zoom-hosted MCP access is evolving; docs indicate a model where Zoom exposes product-scoped MCP servers (for example Meetings, Team Chat, Whiteboard).

  • Use zoom-mcp as the parent MCP entry point.

  • Route Whiteboard-specific MCP requests to zoom-mcp/whiteboard.

  • When a request is product-specific and MCP coverage exists, route to that MCP product surface first; otherwise use REST/SDK skills for deterministic implementation.

Webhooks vs WebSockets

Both receive event notifications, but differ in approach:

Aspectwebhookszoom-websockets
ConnectionHTTP POST to your endpointPersistent WebSocket
LatencyHigherLower
SecurityRequires public endpointNo exposed endpoint
SetupSimplerMore complex
Best forMost use casesReal-time, security-sensitive

Common Use Cases

Use CaseDescriptionSkills Needed
Meeting + Webhooks + OAuth RefreshCreate a meeting, process real-time updates, and refresh OAuth tokens safely in one designzoom-rest-api + zoom-oauth + zoom-webhooks
Scribe Transcription PipelineTranscribe uploaded files or S3 archives with AI Services Scribe using fast mode or batch jobsscribe + optional zoom-rest-api + optional zoom-webhooks
APIs vs MCP RoutingDecide whether to route to deterministic Zoom APIs, AI-driven MCP, or a hybrid designzoom-rest-api and/or zoom-mcp
Custom Meeting UI (Web)Build a custom video UI for a real Zoom meeting in a web app using Meeting SDK Component Viewzoom-meeting-sdk-web-component-view + zoom-oauth
Meeting AutomationSchedule, update, delete meetings programmaticallyzoom-rest-api
Meeting BotsBuild bots that join meetings for AI/transcription/recordingmeeting-sdk/linux + zoom-rest-api + optional zoom-webhooks
High-Volume Meeting PlatformDesign distributed meeting creation and event processing with retries, queues, and reconciliationzoom-rest-api + zoom-webhooks + zoom-oauth
Recording & TranscriptionDownload recordings, get transcriptszoom-webhooks + zoom-rest-api
Recording Download PipelineAuto-download recordings to your own storage (S3, GCS, etc.)zoom-webhooks + zoom-rest-api
Real-Time Media StreamsAccess live audio, video, transcripts via WebSocketzoom-rtms + zoom-webhooks
In-Meeting AppsBuild apps that run inside Zoom meetingszoom-apps-sdk + zoom-oauth
React Native Meeting EmbedEmbed meetings into iOS/Android React Native appszoom-meeting-sdk-react-native + zoom-oauth
Native Meeting SDK Multi-Platform DeliveryAlign Android, iOS, macOS, and Unreal Meeting SDK implementations under one auth/version strategyzoom-meeting-sdk + platform skills
Native Video SDK Multi-Platform DeliveryAlign Android, iOS, macOS, and Unity Video SDK implementations under one auth/version strategyzoom-video-sdk + platform skills
Electron Meeting EmbedEmbed meetings into desktop Electron appszoom-meeting-sdk-electron + zoom-oauth
Flutter Video SessionsBuild custom mobile video sessions in Flutterzoom-video-sdk-flutter + zoom-oauth
React Native Video SessionsBuild custom mobile video sessions in React Nativezoom-video-sdk-react-native + zoom-oauth
Immersive ExperiencesCustom video layouts with Layers APIzoom-apps-sdk
Collaborative AppsReal-time shared state in meetingszoom-apps-sdk
Contact Center App Lifecycle and Context SwitchingBuild Contact Center apps that handle engagement events and multi-engagement statecontact-center + zoom-apps-sdk
Virtual Agent Campaign Web and Mobile WrapperDeliver one campaign-driven bot flow across web and native mobile wrappersvirtual-agent + contact-center
Virtual Agent Knowledge Base Sync PipelineSync external knowledge content into Zoom Virtual Agent using web sync or custom API connectorsvirtual-agent + zoom-rest-api + zoom-oauth
Zoom Phone Smart Embed CRM IntegrationBuild CRM dialer and call logging flows using Smart Embed plus Phone APIsphone + zoom-oauth + zoom-webhooks
Rivet Event-Driven API OrchestratorBuild a Node.js backend that combines webhooks and API actions through Rivet module clientsrivet-sdk + zoom-oauth + zoom-rest-api
Probe SDK Preflight Readiness GateAdd browser/device/network diagnostics and readiness policy before Meeting SDK or Video SDK joinsprobe-sdk + zoom-meeting-sdk or zoom-video-sdk

Complete Use-Case Index

Prerequisites

  1. Zoom account (Pro, Business, or Enterprise)

  2. App created in Zoom App Marketplace

  3. OAuth credentials (Client ID and Secret)

References

Quick Start

  1. Go to marketplace.zoom.us

  2. Click Develop → Build App

  3. Select app type (see references/app-types.md)

  4. Configure OAuth and scopes

  5. Copy credentials to your application

Detailed References

SDK Maintenance

Resources

Environment Variables

Operations

  • RUNBOOK.md - 5-minute preflight and debugging checklist.

Files

references/authorization-patterns.md

Authorization Patterns

Permission validation middleware and role-based access control for Zoom API integrations.

Note: These are implementation patterns for YOUR application when building Zoom integrations. These are not Zoom's internal authorization mechanisms - they are examples of how to structure authorization logic in your own backend.

Overview

When chaining multiple Zoom API calls, each step may require different scopes and permissions. This document provides patterns for validating authorization at each step before proceeding.

Authorization Flow

┌─────────────────────────────────────────────────────────────────────────┐
│                     AUTHORIZATION VALIDATION FLOW                        │
└─────────────────────────────────────────────────────────────────────────┘

┌─────────────────────────────────────────────────────────────────────────┐
│ 1. Check Token Validity                                                 │
│    └── Is token expired? → Refresh or re-authenticate                  │
│    └── Is token revoked? → Re-authenticate                             │
└─────────────────────────────────────────────────────────────────────────┘
                                    │
                                    ▼
┌─────────────────────────────────────────────────────────────────────────┐
│ 2. Validate Required Scopes                                             │
│    └── Does token have scopes for this operation?                       │
│    └── If missing → Return 403 with required scopes                     │
└─────────────────────────────────────────────────────────────────────────┘
                                    │
                                    ▼
┌─────────────────────────────────────────────────────────────────────────┐
│ 3. Check Resource Permissions                                           │
│    └── Does user have access to this resource?                          │
│    └── Is user admin/owner/member?                                      │
└─────────────────────────────────────────────────────────────────────────┘
                                    │
                                    ▼
┌─────────────────────────────────────────────────────────────────────────┐
│ 4. Execute Operation                                                    │
│    └── Call Zoom API                                                    │
│    └── Handle API-level authorization errors                            │
└─────────────────────────────────────────────────────────────────────────┘

Scope Validation Middleware

Express.js Middleware
const axios = require('axios');

/**
 * Middleware to validate OAuth token has required scopes
 * @param {string[]} requiredScopes - Scopes required for this route
 */
function requireScopes(requiredScopes) {
  return async (req, res, next) => {
    const token = req.headers.authorization?.replace('Bearer ', '');
    
    if (!token) {
      return res.status(401).json({
        error: 'unauthorized',
        message: 'No access token provided'
      });
    }
    
    try {
      // Get token info to check scopes
      const tokenInfo = await getTokenInfo(token);
      
      // Check if token has all required scopes
      const tokenScopes = tokenInfo.scope.split(' ');
      const missingScopes = requiredScopes.filter(
        scope => !tokenScopes.includes(scope)
      );
      
      if (missingScopes.length > 0) {
        return res.status(403).json({
          error: 'insufficient_scope',
          message: 'Token missing required scopes',
          required_scopes: requiredScopes,
          missing_scopes: missingScopes,
          your_scopes: tokenScopes
        });
      }
      
      // Attach token info to request for downstream use
      req.zoomToken = tokenInfo;
      req.zoomScopes = tokenScopes;
      next();
      
    } catch (error) {
      if (error.response?.status === 401) {
        return res.status(401).json({
          error: 'invalid_token',
          message: 'Token is invalid or expired'
        });
      }
      next(error);
    }
  };
}

/**
 * Get token information including scopes
 * 
 * IMPORTANT: Scopes are returned during OAuth token exchange, not from API calls.
 * You should store the scopes when you receive the access token.
 */
async function getTokenInfo(accessToken) {
  // For Server-to-Server OAuth: Decode JWT to get scopes
  const parts = accessToken.split('.');
  if (parts.length === 3) {
    const payload = JSON.parse(Buffer.from(parts[1], 'base64').toString());
    return {
      scope: payload.scope || '',
      exp: payload.exp,
      aud: payload.aud
    };
  }
  
  // For User OAuth tokens: Scopes are NOT available from API responses.
  // You must store scopes when you receive them during token exchange.
  // 
  // During OAuth token exchange, the response includes:
  // {
  //   "access_token": "...",
  //   "token_type": "bearer",
  //   "scope": "user:read meeting:write ...",  <-- Store this!
  //   "expires_in": 3600
  // }
  //
  // Store the scope in your database alongside the token.
  
  throw new Error(
    'User OAuth token scopes must be stored during token exchange. ' +
    'Cannot retrieve scopes from an opaque access token.'
  );
}

/**
 * Example: Store scopes during OAuth token exchange
 */
async function handleOAuthCallback(code) {
  const response = await axios.post('https://zoom.us/oauth/token', null, {
    params: {
      grant_type: 'authorization_code',
      code: code,
      redirect_uri: REDIRECT_URI
    },
    auth: {
      username: CLIENT_ID,
      password: CLIENT_SECRET
    }
  });
  
  const { access_token, refresh_token, scope, expires_in } = response.data;
  
  // IMPORTANT: Store the scope along with the token
  await saveTokenToDatabase({
    accessToken: access_token,
    refreshToken: refresh_token,
    scope: scope,  // <-- Store this for later permission checks
    expiresAt: Date.now() + (expires_in * 1000)
  });
  
  return { access_token, scope };
}

// Usage
const express = require('express');
const app = express();

// Route requiring meeting:read scope
app.get('/api/meetings/:id',
  requireScopes(['meeting:read']),
  async (req, res) => {
    // Token already validated, proceed with API call
    const meeting = await getMeeting(req.params.id, req.headers.authorization);
    res.json(meeting);
  }
);

// Route requiring multiple scopes
app.post('/api/users/:id/meetings',
  requireScopes(['user:read', 'meeting:write']),
  async (req, res) => {
    const meeting = await createMeeting(req.params.id, req.body, req.headers.authorization);
    res.json(meeting);
  }
);
Scope Requirements by Operation
OperationUser ScopeAdmin Scope (S2S)
Get own user infouser:readuser:read:admin
List all usersN/Auser:read:admin
Create userN/Auser:write:admin
Get own meetingsmeeting:readmeeting:read:admin
Get any user's meetingsN/Ameeting:read:admin
Create meeting for selfmeeting:writemeeting:write:admin
Create meeting for othersN/Ameeting:write:admin
List own recordingsrecording:readrecording:read:admin
List any user's recordingsN/Arecording:read:admin
Delete own recordingrecording:writerecording:write:admin
Delete any recordingN/Arecording:write:admin
Access own phonephone:readphone:read:admin
Access any user's phoneN/Aphone:read:admin
Manage phone settingsphone:writephone:write:admin

Note: "N/A" means this operation requires admin-level scopes and cannot be done with user-level OAuth.

Role-Based Access Control

Define Roles
/**
 * Role definitions with allowed scopes
 */
const ROLES = {
  admin: {
    scopes: [
      'user:read:admin', 'user:write:admin',
      'meeting:read:admin', 'meeting:write:admin',
      'recording:read:admin', 'recording:write:admin',
      'account:read:admin', 'account:write:admin'
    ],
    description: 'Full administrative access'
  },
  
  manager: {
    scopes: [
      'user:read:admin',
      'meeting:read:admin', 'meeting:write:admin',
      'recording:read:admin'
    ],
    description: 'Manage meetings and view users'
  },
  
  user: {
    scopes: [
      'user:read',
      'meeting:read', 'meeting:write',
      'recording:read'
    ],
    description: 'Manage own meetings and recordings'
  },
  
  viewer: {
    scopes: [
      'meeting:read',
      'recording:read'
    ],
    description: 'View-only access'
  }
};

/**
 * Check if user role has required scope
 */
function roleHasScope(role, requiredScope) {
  const roleConfig = ROLES[role];
  if (!roleConfig) return false;
  
  return roleConfig.scopes.some(scope => {
    // Exact match
    if (scope === requiredScope) return true;
    
    // Admin scope covers non-admin version
    // e.g., meeting:read:admin covers meeting:read
    if (scope.endsWith(':admin')) {
      const baseScope = scope.replace(':admin', '');
      if (baseScope === requiredScope) return true;
    }
    
    return false;
  });
}

/**
 * Middleware to require a specific role
 */
function requireRole(allowedRoles) {
  return (req, res, next) => {
    const userRole = req.user?.role; // From your auth system
    
    if (!userRole || !allowedRoles.includes(userRole)) {
      return res.status(403).json({
        error: 'forbidden',
        message: 'Insufficient role permissions',
        required_roles: allowedRoles,
        your_role: userRole || 'none'
      });
    }
    
    next();
  };
}

// Usage
app.delete('/api/users/:id',
  requireRole(['admin']),
  requireScopes(['user:write:admin']),
  async (req, res) => {
    // Only admins can delete users
    await deleteUser(req.params.id);
    res.json({ success: true });
  }
);

Permission Checking Between Chained Operations

Chain Validation Pattern
/**
 * Validate permissions for a multi-step operation
 * before executing any steps
 */
async function validateChainPermissions(operations, tokenScopes) {
  const allRequiredScopes = new Set();
  
  for (const op of operations) {
    for (const scope of op.requiredScopes) {
      allRequiredScopes.add(scope);
    }
  }
  
  const missingScopes = [...allRequiredScopes].filter(
    scope => !tokenScopes.includes(scope)
  );
  
  if (missingScopes.length > 0) {
    return {
      valid: false,
      missingScopes,
      message: `Cannot complete operation chain. Missing scopes: ${missingScopes.join(', ')}`
    };
  }
  
  return { valid: true };
}

/**
 * Execute a chain of operations with permission validation
 */
async function executeAuthorizedChain(operations, accessToken) {
  // Get token scopes
  const tokenInfo = await getTokenInfo(accessToken);
  const tokenScopes = tokenInfo.scope.split(' ');
  
  // Validate all permissions upfront
  const validation = await validateChainPermissions(operations, tokenScopes);
  if (!validation.valid) {
    throw new Error(validation.message);
  }
  
  // Execute operations in sequence
  const results = [];
  for (const op of operations) {
    console.log(`Executing: ${op.name}`);
    
    try {
      const result = await op.execute(accessToken, results);
      results.push({ name: op.name, success: true, data: result });
    } catch (error) {
      // Check if it's an authorization error
      if (error.response?.status === 403) {
        throw new Error(`Authorization failed at step "${op.name}": ${error.response.data.message}`);
      }
      throw error;
    }
  }
  
  return results;
}

// Example: User + Meeting creation chain
const userMeetingChain = [
  {
    name: 'createUser',
    requiredScopes: ['user:write:admin'],
    execute: async (token, previousResults) => {
      return await createUser({
        email: '[email protected]',
        firstName: 'New',
        lastName: 'User'
      }, token);
    }
  },
  {
    name: 'createMeeting',
    requiredScopes: ['meeting:write:admin'],
    execute: async (token, previousResults) => {
      const user = previousResults.find(r => r.name === 'createUser').data;
      return await createMeeting(user.id, {
        topic: 'Onboarding Meeting'
      }, token);
    }
  }
];

// Usage
try {
  const results = await executeAuthorizedChain(userMeetingChain, accessToken);
  console.log('Chain completed:', results);
} catch (error) {
  console.error('Chain failed:', error.message);
}

Graceful Degradation

Handle Partial Permissions
/**
 * Execute with graceful degradation when permissions are partial
 */
async function executeWithDegradation(operations, accessToken) {
  const tokenInfo = await getTokenInfo(accessToken);
  const tokenScopes = tokenInfo.scope.split(' ');
  
  const results = [];
  
  for (const op of operations) {
    // Check if we have permission for this operation
    const hasPermission = op.requiredScopes.every(
      scope => tokenScopes.includes(scope)
    );
    
    if (!hasPermission) {
      if (op.required) {
        // Required operation - fail the chain
        throw new Error(`Missing required scopes for ${op.name}: ${op.requiredScopes.join(', ')}`);
      } else {
        // Optional operation - skip with warning
        console.warn(`Skipping ${op.name}: insufficient permissions`);
        results.push({
          name: op.name,
          skipped: true,
          reason: 'insufficient_permissions',
          required_scopes: op.requiredScopes
        });
        continue;
      }
    }
    
    // Execute operation
    const result = await op.execute(accessToken, results);
    results.push({ name: op.name, success: true, data: result });
  }
  
  return results;
}

// Example with optional operations
const meetingWithOptionalRecording = [
  {
    name: 'getMeeting',
    required: true,
    requiredScopes: ['meeting:read'],
    execute: async (token) => getMeetingDetails(meetingId, token)
  },
  {
    name: 'getRecordings',
    required: false, // Optional - won't fail chain
    requiredScopes: ['recording:read'],
    execute: async (token, prev) => {
      const meeting = prev.find(r => r.name === 'getMeeting').data;
      return getRecordings(meeting.uuid, token);
    }
  }
];

Authorization Decision Flowchart

┌──────────────────────────────────────────────────────────────────────────┐
│                      AUTHORIZATION DECISION FLOW                          │
└──────────────────────────────────────────────────────────────────────────┘

                        ┌─────────────────┐
                        │  Receive Request │
                        └────────┬────────┘
                                 │
                                 ▼
                    ┌────────────────────────┐
                    │  Is token present?     │
                    └───────────┬────────────┘
                                │
                    ┌───────────┴───────────┐
                    │ NO                    │ YES
                    ▼                       ▼
            ┌───────────────┐     ┌────────────────────┐
            │ Return 401    │     │ Is token valid?    │
            │ Unauthorized  │     └─────────┬──────────┘
            └───────────────┘               │
                                ┌───────────┴───────────┐
                                │ NO                    │ YES
                                ▼                       ▼
                        ┌───────────────┐     ┌────────────────────┐
                        │ Return 401    │     │ Has required       │
                        │ Invalid Token │     │ scopes?            │
                        └───────────────┘     └─────────┬──────────┘
                                                        │
                                            ┌───────────┴───────────┐
                                            │ NO                    │ YES
                                            ▼                       ▼
                                    ┌───────────────┐     ┌────────────────────┐
                                    │ Return 403    │     │ Has resource       │
                                    │ Insufficient  │     │ access?            │
                                    │ Scope         │     └─────────┬──────────┘
                                    └───────────────┘               │
                                                        ┌───────────┴───────────┐
                                                        │ NO                    │ YES
                                                        ▼                       ▼
                                                ┌───────────────┐     ┌────────────────┐
                                                │ Return 403    │     │ Execute        │
                                                │ Forbidden     │     │ Operation      │
                                                └───────────────┘     └────────────────┘

Common Authorization Errors

StatusErrorCauseSolution
401invalid_tokenToken expired or revokedRefresh token or re-authenticate
401unauthorizedNo token providedInclude Authorization header
403insufficient_scopeToken missing required scopeRequest additional scopes
403forbiddenUser lacks resource accessCheck user permissions
403access_deniedAdmin-only operationUse admin account

Best Practices

  1. Validate upfront - Check all permissions before starting a chain

  2. Fail fast - Return clear error messages with required scopes

  3. Graceful degradation - Skip optional steps rather than fail entirely

  4. Audit logging - Log all authorization decisions

  5. Principle of least privilege - Request only needed scopes

  6. Token caching - Cache token info to avoid repeated validation calls

Real-World Examples

See these use-cases for authorization patterns in action:

Resources

Requirements and compatibility

Written for: Claude Code, Claude apps

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Claude Code frontmatter, Needs an MCP server

Security

What our scanner noticed· Medium risk

  • Possible data-exfiltration endpoints
  • Instructions that use the network

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Zoom
Publisher
Anthropic (Official)
Distributed by
Anthropic
Source
anthropics/knowledge-work-plugins · partner-built/zoom-plugin/skills/general · commit e050c2e
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from partner-built/zoom-plugin/LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Zoom or Anthropic.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download zoom-general.zip