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 prompting and no live agent session: load it, review what it does, check the permissions, run it.

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.

Both are examples of the saved-workflow-plus-Workflow-AI pattern: the script handles selection, transcript export, batching, validation, and re-import, while a configured Workflow AI provider does only the language work. They are tuned for CLI providers such as Codex or Claude Code by default and also work with local LM Studio models — for smaller local models, lower the batch size in the setup dialog.

Finishing​

  • Reconstruct Edit From Reference: searches selected original Project-panel media for every shot in a rendered reference, reconstructs reliable matches as editable video clips, and leaves uncertain decisions marked or gapped for review. 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 V1 Clips To V2 Reference Framing: matches clips on track V1 against a full-frame reference on V2, recovers Position and Scale, and applies the values back to the V1 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.

Markers​

  • 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

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 checks those requirements before the run (preflight):

  • The Workflow AI transcript tools need a configured and tested Workflow AI provider — Codex CLI, Claude Code CLI, or LM Studio. Guided Setup covers this.
  • Workflows that use external tools need the matching Runtime Pack — for example Python for the transcript tools, plus FFmpeg and Python/OpenCV for reconstruction, slip matching, and framing recovery. The panel points you to the Runtime Packs tab when something is missing. See Runtime Packs.

If a requirement is missing, the workflow reports it clearly instead of failing 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.