About visant-premiere-editor
A production-oriented skill for carrying cut plans into Adobe Premiere Pro as frame-accurate rough cuts, aimed at agents working with a human editor. It uses FCP7 XML rather than cut-by-cut MCP edits and documents checks for importing, adjusting, and delivering sequences.
Key features
- 01Convert JSON cut plans to FCP7 XML
- 02Check sequence frames and metadata
- 03Apply motion settings and markers
- 04Create Figma Slides cards
- 05Document import and delivery steps
Use cases
- 01Import a planned rough cut into Premiere Pro
- 02Check sequence output against a cut plan
- 03Add approved face-shot punch-ins and markers
MCP support
Uses premiere-pro-mcp through its CEP backend to inspect and modify Premiere Pro projects, sequences, clips, effects, and renders. It also describes Figma MCP calls for generating and capturing slide cards.
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ pedrojaques99/ visant-skills-public --skill visant-premiere-editorAfter installing, type/visant-premiere-editorin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
references/cases.mdpitfalls.mdscripts/figma_cards.pypremiere_xml.pyscripts/icons/anthropic.svgclaude.svgcloudflare.svgcursor.svgfigma.svggithub.svggoogledrive.svggooglegemini.svglinear.svgnotion.svgopenai.svgvercel.svgwarning.svgDetails
From the project READMEVisant Premiere Editor
Requirements
| Needed for | What | Check |
|---|---|---|
| everything | Windows or macOS with Adobe Premiere Pro (measured on 2026 / 26.x) | open Premiere |
| everything | premiere-pro-mcp with the CEP backend and the MCP Bridge panel open (Window > Extensions > MCP Bridge); measured on 1.17 | MCP tool verify_premiere_connection |
| everything | ffmpeg + ffprobe on PATH | ffprobe -version |
premiere_xml.py | Python 3 + opentimelineio + otio-fcp-adapter (pip install opentimelineio otio-fcp-adapter) | python -c "import opentimelineio as o; o.adapters.from_name('fcp_xml')" |
figma_cards.py | Python 3 (stdlib only) + Figma MCP (use_figma, get_screenshot) with skills figma-use, figma-use-slides | python --version |
Works with Premiere in English or Portuguese (PT-BR). The XML holds no effect names; the MCP calls
take the UI names, mapped in PREMIERE_NAMES in scripts/premiere_xml.py (EN and PT-BR labels read
from Premiere 2026's own Dictionaries/en_US and pt_BR). Another UI language: read the same keys
from its folder and add a column. Unsure which names this Premiere uses: save a get_effect_properties
readback and run python scripts/premiere_xml.py --names <file>.
Shipped here: scripts/premiere_xml.py (plan → FCP7 XML, motion table, checker),
scripts/figma_cards.py (cards JS for Figma Slides) and scripts/icons/ (Simple Icons, CC0).
Old Portuguese plan/batch keys, --saida/--conferir and Edição N (não apresentar) rows still
work (python scripts/premiere_xml.py --self-test proves old and new plans give the same XML).
Not shipped, project-side: the scripts named in the tighten, learn, b-roll and delivery
sections (aperta_final.py, aprende.py, fala.py, agente.py, rampa.py, onde.py,
trecho.py, fonte_iphone.py, entrega.py, legenda_whisper.py, sensor_export.py). They live
next to the project's lesson engine because they need its plan and source wavs. If the project
does not have them, do those steps by hand with ffmpeg and the MCP, following the same rules.
Role
The agent assembles the rough cut; the person editing refines it in Premiere. No music, color or b-roll in the rough cut unless asked.
Input: a cut plan in JSON (format at the top of scripts/premiere_xml.py). Another stage makes
the plan: speech-based breakdown and cuts in visant-video-editor, or the project's own scripts.
This skill does not decide cuts, it only carries the plan into Premiere without losing a frame.
Rule zero: never assemble cut by cut through the MCP.
create_subclip+create_sequence_from_clipsmisses by 1 frame per end (Premiere rounds seconds down) and a PNG subclip becomes 12 hours. The path is XML.
Flow
- The user may be working in Premiere right now.
set_active_sequenceswitches their screen, and a clip's node ID changes when the active sequence changes. Before each edit, re-read the ID withget_clip_at_position, and warn before a round of changes. - Connection, read-only.
verify_premiere_connection(backendcep) andget_project_info. If a call times out at 120 s, a dialog is open in Premiere: ask the user to close it and fire nothing else until they do. - Check the source with
ffprobe: resolution, fps (r_frame_rateandavg_frame_rate), audio present, rotation. iPhone MOV is VFR and Premiere interprets it at 29.9992. - Generate the XML:
python scripts/premiere_xml.py <plan.json> --out <dir>. - Import into the open project:
import_mediawith the.xml(suppress_ui: true). Do not useimport_fcp_xml, which creates ANOTHER project. One lesson per call. - Relink: XML media comes in offline even with the right path.
search_project_itemswithoffline_only, thenrelink_mediaof each item to the same path. Up to 4 in parallel works. - Punch-in (face shots only):
python scripts/premiere_xml.py --motion <plan.json>gives the table. Apply withset_effect_propertyon Motion > Scale (Movimento > Escala), in %, and normalized Position (Posição)[x/w, y/h].set_clip_properties_batchfails on a PT-BR UI. Animated push-in (only with the user's approval, showing first and last frame sheets first):add_keyframeonly accepts numbers, so Position does not animate. Put the Anchor Point (Ponto de ancoragem) on the face[cx/w, cy/h]and Position on the target[0.5, 0.38], and animate only Scale. Keyframe time is SOURCE time: useinPointfromget_clip_propertiesandinPoint + duration − 1 frame. - Marker colors: the XML carries no color. Use
update_marker(time_seconds, color=1)(red) on shot markers; speech stays default (0, green). - Read back and check:
get_full_sequence_info. When the result goes to a file (large output), runpython scripts/premiere_xml.py --check <plan.json> <file>. When it comes inline, check cut count, total frames, markers, format and A1. - Look at frames:
capture_frameat 2 or 3 points (one punch-in of each scale and the most suspicious cut) against the reference render, if any. A Position stuck at the clamp limit means a badly detected face. - Save (
save_project) and tidy: sequences and media in one bin per delivery. CEP does not delete project items: test leftovers go to a bin_descartar (teste do agente)and the sequence name gets[descartar], for the user to delete.
Tightening an already edited sequence (pauses, drags, fumbles)
When the user already edited the sequence by hand, do not regenerate from the engine: their edit is lost. The path is an XML round trip into a new sequence alongside:
create_project_backupof the.prproj.- For each lesson:
set_active_sequence(warn first, it switches the user's screen) andexport_as_fcp_xmlto_apertada/aula-N.xml. - Run the project's tighten script (
aperta_final.py _apertada/aula-N.xml). It outputsaula-N-apertada.xml+.cortes.tsv, each cut with time, reason and word. import_mediaof the tightened XML withtarget_bin(the user's bin), media into<bin>/_mídia, then step 5 (relink) and 8 (check). The original stays intact for comparison; re-import gets--sufixo v2and never overwrites a tightened version the user already edited.
Tightening rules: silence is measured from the audio (< -45 dB), never from the gap between whisper words, because whisper stretches a word over the pause (one word spanned 4.7 s). A pause
0.15 s keeps 0.10 s. A drag is a word of up to 3 letters with continuous sound > 0.40 s, measured inside whisper's edges, because in running speech the sound does not stop between words. From a drag only the vowel's core is removed, keeping 0.15 s of head and 0.08 s of tail. Badge and label move only with the cut; b-roll is cut along. The script aborts when a
.movpiece's duration does not match the plan: sign the engine's plan changed after the render and the word→frame map is wrong.
Learning from the user's edit
When the user fixes a generated sequence by hand (e.g. redid the ending), do not guess what they
meant. Export their version and compare with yours: python aprende.py <mine.xml> <theirs.xml>.
The comparison is per raw stretch and shows what they RESTORED, what they CUT FURTHER and which
words are in each stretch. To repeat their ending on a new version:
aprende.py <new.xml> <theirs.xml> --fecho MM:SS.s <out.xml> "<name>". Their clips go in at the
end with volume and cut, and masterclipid is remapped, because their id points to other media
and the import hangs. A change that repeats becomes a number in the skill or a line in the
script (fecho.tsv, roteiro.tsv), not another hand fix.
For their edit to survive every new version: aprende.py <mine> <theirs> --grava writes
edicao_dono.tsv (cut/keep per raw stretch) and the tighten script repeats it on its own. A
boring stretch (dictating a prompt) becomes a ramp: a line in rampas.tsv (rampa.py: speeds up
in steps up to 3x, voice always audible, no zoom (the user zooms by hand), and an ACELERADO badge).
Content cuts (rambling, sentence said twice, stumble) belong to the agent and stay separate:
fala.py <module> <lesson> prints speech per sentence with source time;
agente.py <module> <lesson> <source> "start|end" ... --grava finds the stretch by text and
writes edicao_agente.tsv, which the tighten script reads together with the user's. A cut that
changes a promise (course mentioned, price, deadline) goes in, but goes to a question.
Cards: notices and logos, made in Figma
The card is born in the lesson deck (Figma Slides), never drawn in Premiere:
python scripts/figma_cards.py <batch.json> <batch.js>(format at the top of the script; icons inscripts/icons/, Simple Icons CC0 in the official color; a brand not there goes in as text, never an invented logo).- Run the JS with
use_figma. Each lesson gets a rowEdit N (do not present)(an existingEdição N (não apresentar)row is reused); if the row fills up, it opensEdit N b. get_screenshotwithcontentsOnlyof each card → PNG in_build/aulaN/sobre/.- In Premiere:
import_media,overwrite_clipon the HIGHEST free track,set_clip_duration,set_effect_property(normalized Position, Scale), house fade (references/pitfalls.md). Find the second of the line with the project'sonde.py <module> <lesson> <xml|json> "phrase".
A card that repeats what the slide already shows does not go in.
Covering speech with b-roll and timelapse
A long face stretch with no screen needs b-roll. Rules:
- Video-only copy (
ffmpeg -an) of each b-roll: camera audio never goes into A1. - Cut the exact piece in ffmpeg (
cortes/<lesson>_<tl>_<source>.mov) and place it whole:set_item_in_outdoes not apply the in point in this version. - Track above the face and below the cards; never over a card or an engine label.
- Look at every frame first: Claude's sidebar, account picker, e-mail, client name. Blur
(
boxbluron the region) or swap the b-roll. When in doubt, swap. - iPhone source: convert HDR→SDR and fix rotation BEFORE cutting the piece.
Swapping a rendered piece already in the sequence
A redone piece (speech cut, color) gets a NEW NAME (-2.mov): re-importing the same path is
ignored. import_media → remove_from_timeline of the video AND the audio (they come out
separately) → overwrite_clip at 0 → get_sequence_structure to check the duration. A Media
Encoder job already queued keeps the old version: queue a new job with another name and ask the
user to delete the old one.
Delivery
- Sequence name is the file name:
Aula N · Título, nov2/apertada/nova. The tighten script outputs· nova; the user approves and the suffix goes. save_project,check_offline_media= 0, and per lesson:set_active_sequence→add_to_render_queue(preset01 - Match Source - High bitrate, output<N · Título>.mp4, no?in the name) andstart_batch_encode(the user does not need to press ▶). If the queue never starts, useexport_sequenceinstead (see pitfalls). The MP4 carries the whole sequence: trim the black at the end withffmpeg -t ... -c copy. Watch the output folder (the project'ssensor_export.py).- Loudness: 2-pass loudnorm to -14 LUFS / -1.5 dBTP with the video copied, then
.srt/.vttfrom whisper (the project'sentrega.py+legenda_whisper.py). Re-run only on what is missing.
Report
One table per sequence: cuts, frames, duration vs plan, markers, format, tracks. Say what changed relative to the plan (frame pulled, marker pushed, position fixed by hand) and send the fix to whoever generates the plan.
Measured pitfalls, with cause and fix: references/pitfalls.md. Read before the session's first
import. Where the rules came from: references/cases.md.