SHAI

S8 Content

/new-edit

The Edit Orchestrator (any industry, any deliverable mix)

The Edit Orchestrator: one video edit project for one client, hands-off — free local ingest first, one combined question recorded verbatim as the standing approval, then /ingest-footage, /build-cut, /generate-assets, /finish-edit and /publish-edit executed inline in pipeline order, with the review gate before any site or account delivery. v2: the one question names the saved style profiles and the strength; bulk apply is the -batch project with one profile across every source; the review packet and the final summary carry the style-match score, a distance, not a grade.

builtv0.2.0

Run itAll agents

Its status above is the registry's own, with the date of the run that produced it.

What it is for

Contract A

This agent owns no numbered ledger item of its own.

Example requests

  • edit this
  • cut shorts out of this
  • make a reel from this
  • batch-caption these videos
  • magic edit this
  • apply my style to this video
  • bulk apply my style
  • undo that edit
  • save this as a template
  • edited video
  • upload, edit, caption and schedule this

What it needs, and what it hands back

Needs connected

Nothing. It runs on what SHAI already knows about you.

Better with: higgsfield, openart, github, vercel, ayrshare.

Uses Bash, Read/Write/Edit, mcp__Higgsfield__balance, mcp__Higgsfield__transactions, openart_account_get, openart_project_list, openart_project_create, create_trigger (scheduled batches), Artifact, SendUserFile, which exist in Claude Code. In the platform those steps come back as something for you to do, with the exact clicks.

Hands back

  • clients/<slug>/edits/<project-slug>/brief.md with the standing approval verbatim
  • clients/<slug>/assets/brand/brand-kit.md
  • commands.log, review/review-v<N>.md, templates/
  • status.md (## Run context, ## Checklist, ## Credits, ## Needs-me list, ## Media rights) and the final summary

Stops and asks

  • the one question's answer (upload consent, credit ceiling per provider, publishing consent scope) before any upload or credit
  • the review gate before any site or account delivery
  • a re-quote when a revision touches more than half the rows or needs new credits

Steps it cannot do through an API, and hands you instead: no third-party-upload consent -> Stage B skipped, every provider-dependent slot parked manual-fallback, the local-only pipeline proceeds; TikTok not connected -> files plus metadata for manual upload, stated plainly; no scheduler rung available -> publish/schedule.md as the posting calendar.

How it runs

These are the headings of its own written instructions — 409 lines you can read and change.

  1. Step 0 — Environment check + inputs + project folder
  2. Step 1–6 — The pipeline, per output