AutoGineer
Generated banner for Scribe
Generated logo for Scribe

Scribe

OpenAIOfficialCreated by ZoomDistributed by OpenAI

  • Skill
  • Tool integration
  • Automation and integrations
  • MIT
  • No issues found
Download ZIP

From the author

Use when using Scribe.
— the description by Zoom

AutoGineer summary

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

This skill provides a structured workflow for integrating Zoom Scribe AI services into your applications. It covers the end-to-end process of setting up transcription pipelines, from credential management and media ingestion to handling batch jobs and webhook callbacks. It distinguishes between synchronous fast-mode transcription and asynchronous batch processing, ensuring developers can select the appropriate mode for their specific latency and volume requirements.

What it does

  • Guides the setup of authentication using JWT for Zoom AI services.
  • Defines the workflow for both synchronous fast-mode and asynchronous batch transcription.
  • Outlines requirements for media ingestion, chunking, and persistence.
  • Provides instructions for implementing webhook callbacks for batch job notifications.
  • Offers troubleshooting steps for common issues like credential drift or processing errors.

When to use it

  • When you need to transcribe pre-recorded media files stored in cloud storage.
  • When building automated transcription pipelines that require batch processing.
  • When you need to integrate Zoom's AI transcription capabilities into an existing application.
  • When you need to verify the status or manage the lifecycle of batch transcription jobs.

Advantages

  • Provides a clear, step-by-step procedure for complex transcription integrations.
  • Helps distinguish between different processing modes to optimize for latency.
  • Includes essential guidance on security practices like webhook signature verification.
  • Centralizes configuration requirements for S3-based batch processing.

Usage examples

“How do I set up a batch transcription job for files in S3?”
The agent will guide you through defining the input S3 URI, configuring the batch job parameters, and setting up a webhook to receive completion notifications.
“What are the requirements for using the synchronous Scribe endpoint?”
The agent will explain the POST /aiservices/scribe/transcribe endpoint, required file and config fields, and how to handle the immediate response.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/openai/scribe/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip scribe.zip -d .agents/skills

Documentation by Zoom

Zoom AI Services Scribe

Use this skill for Zoom Scribe transcription pipelines over uploaded or stored media. If the user needs live meeting media, compare against RTMS or Meeting SDK bot workflows first.

Workflow

  1. Confirm the media source, size, language, expected latency, and whether fast mode or batch mode fits.

  2. Set up Build-platform credentials and JWT handling separately from application transcription logic.

  3. Design ingestion, chunking, retries, webhook callbacks, and persistence before connecting downstream AI workflows.

  4. Implement a minimal transcription request and response parser, then add batching and operational monitoring.

  5. Debug by checking credential audience, processing mode, media format, file size, backend timeout, and webhook delivery.

References

Files

references/full-guide.md

Zoom AI Services Scribe

Background reference for Zoom AI Services Scribe across:

  • synchronous single-file transcription (POST /aiservices/scribe/transcribe)

  • asynchronous batch jobs (/aiservices/scribe/jobs*)

  • browser microphone pseudo-streaming via repeated short file uploads

  • webhook-driven batch status updates

  • Build-platform JWT generation and credential handling

Official docs:

Routing Guardrail

  • If the user needs uploaded or stored media transcribed into text, route here first.

  • If the user needs live meeting media without file-based upload/batch jobs, route to ../rtms/SKILL.md.

  • If the user needs Zoom REST API inventory for AI Services paths, chain ../rest-api/SKILL.md.

  • If the user needs webhook signature patterns or generic HMAC receiver hardening, optionally chain ../webhooks/SKILL.md.

Quick Links

  1. concepts/auth-and-processing-modes.md

  2. scenarios/high-level-scenarios.md

  3. examples/fast-mode-node.md

  4. examples/batch-webhook-pipeline.md

  5. references/api-reference.md

  6. references/environment-variables.md

  7. references/samples-validation.md

  8. references/versioning-and-drift.md

  9. troubleshooting/common-drift-and-breaks.md

  10. RUNBOOK.md

Core Workflow

  1. Get Build-platform credentials and generate an HS256 JWT.

  2. Choose fast mode for one short file or batch mode for stored archives / large sets.

  3. Submit the transcription request.

  4. For batch jobs, poll job/file status or receive webhook notifications.

  5. Persist and post-process transcript JSON.

Hosted Fast-Mode Guardrail

  • The formal fast-mode API limits are 100 MB and 2 hours, but hosted browser flows can still time out before the upstream response returns.

  • Current deployed-sample observations:

    • ~17.2 MB MP4 completed in about 26s

    • ~38.6 MB MP4 completed in about 26-37s

    • ~59.2 MB MP4 completed in about 32-34s on the backend

    • some ~59.2 MB browser requests still surfaced as frontend 504 while backend logs later showed 200

  • Treat frontend 504 plus backend 200 as a browser/edge timeout race, not an automatic transcription failure.

  • For hosted UIs, prefer an async request/polling wrapper for fast mode instead of holding the browser open for the full upstream response.

  • For larger or less predictable media, prefer batch mode even when the file is still within the formal fast-mode size limit.

Browser Microphone Pattern

  • scribe does not expose a documented real-time streaming API surface.

  • If you want a browser microphone experience, use pseudo-streaming:

    1. capture microphone audio in short chunks

    2. upload each chunk through the async fast-mode wrapper

    3. poll for completion

    4. append chunk transcripts in sequence

  • Recommended starting cadence:

    • chunk size: 5 seconds

    • acceptable range: 5-10 seconds

    • in-flight chunk requests: 2-3

  • This is a practical UI pattern for incremental transcript updates, not a substitute for rtms.

  • Treat this as a fallback demo pattern, not the preferred production architecture.

  • It adds repeated upload overhead, chunk-boundary drift, browser codec/container variability, and transcript stitching complexity.

  • If the user asks for actual live stream ingestion, low-latency continuous media, or server-push media transport, route to ../rtms/SKILL.md instead.

Endpoint Surface

ModeMethodPathUse
FastPOST/aiservices/scribe/transcribeSynchronous transcription for one file
BatchPOST/aiservices/scribe/jobsSubmit asynchronous batch job
BatchGET/aiservices/scribe/jobsList jobs
BatchGET/aiservices/scribe/jobs/{jobId}Inspect job summary/state
BatchDELETE/aiservices/scribe/jobs/{jobId}Cancel queued/processing job
BatchGET/aiservices/scribe/jobs/{jobId}/filesInspect per-file results

High-Level Scenarios

  • On-demand clip transcription after a user uploads one recording.

  • Batch transcription of stored S3 call archives.

  • Webhook-driven ETL pipeline that writes transcripts to your database/search index.

  • Re-transcription of Zoom-managed recordings after exporting them to your own storage.

  • Offline compliance or QA workflows that need timestamps, channel separation, and speaker hints.

Chaining

  • Stored Zoom recordings -> ../rest-api/SKILL.md + scribe

  • Webhook verification hardening -> ../webhooks/SKILL.md

  • Real-time live transcript/media -> ../rtms/SKILL.md

  • Cross-product routing -> ../general/SKILL.md

Operations

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

Requirements and compatibility

Written for: OpenAI Codex

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: Needs Node.js

Security

No issues found by our static scan· No issues found

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
OpenAI (Official)
Distributed by
OpenAI
Source
openai/plugins · plugins/zoom/skills/scribe · commit d420d13
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from plugins/zoom/LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

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

Download ZIP

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