Editing

1. Continue before you start. If this conversation already works on a video (a

   video-agent/edits/<slug>/

   folder, a take just edited, a week of scripts just written), the request is the next step of that project with the skill already in use: apply the change, rerun the step, keep its files, never start it over.
2. Otherwise read the request and pick the skill:
   • No

     video-agent/

     folder yet, first time, tools, voice, permissions, accounts, keys:

     studio-setup

     . An edit asked before any setup: run

     studio-setup

     first (or at least its tools step).
   • Their Instagram stats, "what works on my account", an audit of an account or of their competitors:

     insta-audit

     .
   • Scripts, ideas for the week, hooks, rewrite, humanize a text, "sounds like AI", what goes viral in their niche, swipe file:

     studio-script

     (

     viral

     for the niche research).
   • A take or a local file, "my last take", a video URL to edit, an existing slug, short, reel, a full YouTube video:

     short-editing

     . "In the style of <name>" =

     short-editing ... style <name>

     .
   • Their B-roll ("add these clips", "my B-roll", "put my B-roll on this short", find a shot, drop a clip):

     broll

     (

     setup

     ,

     add

     ,

     use

     ,

     search

     ,

     reject

     ).
   • Copy another creator's editing style ("steal", "edit like @x", a reel given as the model for a look rather than as the take to edit):

     steal

     .
   • One long video (a podcast, a live, a long YouTube video) into several shorts:

     clips

     .
   • A version of a take in another language:

     short-translate

     .
   • Thumbnails, covers, stills, any image:

     codex-images

     .
   • Publish or schedule a finished video ("post it", "publier", "mets-le en ligne"):

     publish

     .
   • Still ambiguous: ask one question only.
3. Load the target: invoke it with the Skill tool, else read

   <skills folder>/<skill>/SKILL.md

   (the skills installed next to this one) and follow it exactly as if the user had typed

   /<skill> <args>

   . Pass their words through as that skill's arguments.