Skip to main content

The Script Library

The Library tab of the Automation Agent panel is where saved workflows live — both your own scripts and a set of ready-made example workflows that ship with the product.

The Library has two roots:

  • Examples: tested workflows maintained by us. They are the fastest way to get real results, and they double as reference implementations you can open in the block editor and learn from.
  • User Library: your own saved scripts and everything you adapt from the examples.

Running a Library workflow needs no prompt authoring and no live Assistant or MCP-agent session. Select it, review what it does and what it requires, then run it. Some tools need no AI configuration at all; others use local Runtime Packs or call a configured Workflow AI provider for the part that needs language or editorial judgment.

Find What You Can Use​

The default All tools view keeps every supported Library document discoverable. The filter menu beside the search field offers narrower views:

  • Ready now: every currently known requirement is satisfied on this machine.
  • No AI required: the workflow does not call Workflow AI while it runs.
  • Uses Workflow AI: the workflow contains a Workflow AI step.

No AI required and Ready now are intentionally separate. An AI-free image-analysis or media-processing tool may still need Python or FFmpeg. Those local tools do not require an AI account or subscription: install the matching Runtime Pack once, or import it offline, and the workflow can run locally afterward.

Filtering keeps the Library's folder hierarchy intact. Branches containing matches open automatically; branches without matches remain present and can still be expanded for folder actions such as creating or saving tools. Tools with missing requirements remain selectable under All tools so you can read their descriptions and understand what setup would unlock them. A document that could not be inspected remains visible there instead of being incorrectly included in a filtered result.

What Ships In The Examples​

Transcript Handling​

  • Proofread Selected Transcripts With Workflow AI: proofreads the transcripts of selected clips, shows validated correction suggestions for review, and optionally imports accepted changes back into Premiere. Used in the proofreading recipe.
  • Translate Selected Transcripts With Workflow AI: translates selected clip transcripts into a target language you choose and imports the result. Used in the translation recipe.
  • Export Selected Clip Transcripts To SRT: creates portable SRT files from complete source transcripts.
  • Generate SRT From Active Sequence Source Transcripts: maps source-transcript words into the active edit and reports unsupported clips or overlapping speech instead of guessing.
  • Analyze SRT Readability And Timing: checks subtitle structure, layout, and reading speed and can optionally add review markers to the matching active sequence.
  • Reflow SRT Captions: completely rebuilds caption and line boundaries with global look-ahead and automatically uses precise saved word timing when available.
  • Translate SRT Files To Multiple Languages With Workflow AI: translates selected SRT files into several languages while keeping timing decisions local.
  • Condense SRT For Readability With Workflow AI: shortens only captions that remain too fast after a text-preserving timing adjustment and keeps every rewrite reviewable. The complete set is documented in the SRT Caption Toolbox.

The Workflow-AI-powered tools are examples of the saved-workflow-plus-Workflow-AI pattern: the script handles selection or file discovery, transcript/SRT processing, batching, validation, and local merge or re-import, while a configured Workflow AI provider does only the language work. Each setup dialog gives concrete starting values for Codex CLI or Claude Code and smaller local LM Studio models, and labels project-specific context or instruction fields as optional.

Editing​

  • Assemble Sequence From Script (Offline): matches an exact or near-exact target script against one or more selected source transcripts and creates a new sequence in target-text order. Likely alternatives are stacked, while changed, partial, or missing wording remains visible through markers and gaps. It uses the Python Runtime Pack but no Workflow AI provider. See the transcript-based assembly recipe.
  • Build Repeated-Takes Comparison Sequence: finds repeated script-like deliveries across selected transcribed recordings and organizes each passage as a stacked take group. An optional reference script improves matching; the analysis stays local. See the repeated-takes recipe.
  • Create Semantic Rough-Select Comparison: uses a powerful configured Workflow AI provider to organize freely spoken material, build a possible story order, and stack substantially rephrased alternatives. Use Codex CLI or Claude Code for this complete-context editorial task; current local LM Studio agents are generally not strong enough. See the semantic workflow section in the repeated-takes recipe.

Choose the first tool when a target script defines the edit, the second when the goal is exhaustive take comparison, and the third when meaning and story context matter more than matching the same words.

Finishing​

  • Reconstruct Edit From Reference: searches selected original Project-panel media for every shot in a rendered reference, reconstructs the best matches as editable video clips, and can place disabled ranked alternatives for uncertain shots on existing tracks above the conform. It can use Premiere Scene Edit Detection when the reference is one flat clip. See the complete reference-conform recipe.
  • Detect Scene Edits In Selected Clips: runs Premiere's native Scene Edit Detection on selected timeline clips and applies cuts, creates source markers, or creates Project-panel subclips. See the Scene Edit Detection recipe.
  • Slip Clips To Match Reference: fine-conforms selected clips or all clips on V1 by slipping their source frames to the best visual match in the overlapping V2 reference. Supports bounded and entire-source searches, and adds color-coded markers for review. See the timing-refinement recipe.
  • Match Clips To Reference Framing: matches selected or all clips on a chosen target track against a full-frame reference on another video track, recovers Position and Scale, and applies the values back to the target clips. Uses the FFmpeg and Python Runtime Packs for frame extraction and image analysis. See the framing recipe.

These tools form a staged reference-conform workflow without forcing every project through every stage: detect boundaries when necessary, reconstruct missing shots, refine source timing, then recover framing only when the approved composition differs.

Publishing & Social​

  • Create YouTube Chapters From Active Sequence: analyzes the usable spoken content in the active edit, creates verified chapter point markers, and can copy matching YouTube-style chapter text. It requires the Python Runtime Pack and a powerful configured Workflow AI provider such as Codex CLI or Claude Code. See the YouTube chapters recipe.
  • Find Highlights And Teasers In Active Sequence: proposes scored duration markers for transcript-based teasers, highlights, pull quotes, and social cutdowns. It has the same Python and powerful-provider requirements. See the highlights and teasers recipe.

Both tools analyze transcripts only. Use their live-agent recipe variants when title cards, B-roll, screen content, silent reveals, or other visual evidence must influence the result. Most current local LM Studio models are unlikely to handle these complete-context editorial tasks reliably.

Marker Utilities​

  • Export Sequence Markers To SRT and Import SRT As Sequence Markers
  • Export Sequence Markers To YouTube Chapter Text and Import YouTube Chapter Text As Sequence Markers
Library navigation in this beta

The four marker import/export helpers previously listed under Markers now live under Marker Utilities. The new transcript-analysis tools live under Publishing & Social because their purpose is editorial content analysis; markers are only how Premiere displays their results.

Rendering​

  • Render Frames At Sequence Markers
  • Render Marker Ranges With Export Preset

What Some Workflows Need First​

Library workflows declare what they require, and Automation Agent shows their current readiness while you browse. It checks again before a run starts:

  • The Workflow AI transcript tools need a configured and tested Workflow AI provider — Codex CLI, Claude Code CLI, or LM Studio. The complete-context Publishing & Social tools need a particularly capable provider; Codex CLI or Claude Code are recommended, while most current local LM Studio models are unlikely to be sufficient. Open AI Setup takes you to the existing AI Setup tab; Guided Setup covers the recommended configuration.
  • Workflows that use external tools need the matching Runtime Pack — for example Python for transcript processing, plus FFmpeg and Python/OpenCV for reconstruction, slip matching, and framing recovery. Open Runtime Packs takes you to the existing Runtime Packs tab. See Runtime Packs.

These actions reuse the normal setup tabs; they do not create separate configuration paths. If a requirement is missing, the workflow does not begin and then fail halfway through.

Review Before You Run​

Library workflows follow the same rules as everything else in Automation Agent:

  • You can open any workflow in the block editor and read exactly what it does before running it.
  • Execution respects the Execution Permissions tab. Give a workflow only the read and write access it needs — for example, transcript tools only need write access to the clips whose transcripts you want to change. See Permissions and Safety.
  • Workflows that modify the project confirm or report their changes, and items they cannot process are skipped and reported.

Make Them Your Own​

The examples are also starting points. Duplicate a workflow into your User Library, open it in the block editor, and adapt it: change the report format, add a project-specific naming rule, or adjust the Workflow AI instructions.

When you build something new — alone, with your Assistant, or both — save it here too. See Create And Save Your Own Scripts, and use Keyboard Shortcuts and Remote Triggers to launch saved workflows from a shortcut or Stream Deck button.