Generate local subtitles for video editing workflows with Auto Subs
Use Auto Subs when an operator or media agent needs local-first subtitle generation, editing, and handoff into DaVinci Resolve, Premiere Pro, After Effects, or a command-line video pipeline.
npx skills add agentskillexchange/skills --skill generate-local-subtitles-for-video-editing-workflows-with-auto-subs
Use Auto Subs when a media workflow needs to transcribe source audio, edit speakers and subtitle timing, and return caption assets to a video project without sending media to a cloud service. It can run as a standalone local subtitle generator, connect directly to DaVinci Resolve, communicate with Adobe Premiere Pro and After Effects through its bundled extension, or be invoked through its CLI for repeatable pipeline work.
What this skill actually does
Invoke this instead of using a video editor manually when subtitles are part of a repeated production workflow: podcast clips, course videos, social edits, localization prep, or batch caption generation where an agent can prepare files and preserve local data handling. The boundary is subtitle generation and editor handoff; it is not a generic video editing suite, speech-to-text model listing, or broad media automation platform.
Inputs and prerequisites: Auto Subs desktop app or CLI, local media files, and optionally DaVinci Resolve, Adobe Premiere Pro, or Adobe After Effects for editor integration..
Setup notes:
Install Auto Subs from the platform installer listed in the project README, or on macOS run brew install --cask auto-subs. For editor workflows, open DaVinci Resolve and launch Workspace -> Scripts -> AutoSubs, or open Premiere Pro / After Effects and use the bundled CEP extension. For automation, follow the repository’s CLI guide to transcribe media and export subtitle assets from the command line.
Source and verification boundary: use https://tom-moroney.com/auto-subs/ as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.
Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.