/publish-edit

Agent 8: Publisher (any industry)

Agent 8, Publisher: summary and chapters from the final cut's transcript, titles, descriptions and hashtags without invented metrics, thumbnails from real frames, site delivery under the promo family, posting and scheduling through Ayrshare to every network it covers (TikTok included) when that key is connected, else the Higgsfield TikTok route, with per-post consent and automatic is_aigc, scheduling through whichever rung the environment records, and an append-only publish-log.md. TikTok is not connected, so files plus metadata for manual upload is the primary path today, stated plainly.

builtv0.2.0

Run it All 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

“post this to tiktok”
“schedule for”
“titles and hashtags”
“thumbnail options”
“chapters”
“summarize this video”
“put the promo on the website”
“send me the files”
“post this through Ayrshare”
“schedule it on Ayrshare”

What it needs, and what it hands back

Needs connected

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

Better with: ayrshare, higgsfield, github, vercel.

Uses ayrshare_post_create, ayrshare_post_schedule, ayrshare_post_delete, ayrshare_profiles_read, ayrshare_history_read, tiktok_accounts, tiktok_connect, tiktok_reconnect, tiktok_prepare_publish, tiktok_publish, tiktok_publish_status, tiktok_music_trending, media_upload, media_confirm, create_trigger, update_trigger, delete_trigger, list_triggers, CronCreate, CronList, CronDelete, mcp__github__push_files, mcp__Vercel__get_deployment, mcp__Vercel__get_deployment_build_logs, Bash (ffmpeg thumbnail/select), tools/thumbnail.py, SendUserFile, Artifact, WebSearch, WebFetch, which exist in Claude Code. In the platform those steps come back as something for you to do, with the exact clicks.

Hands back

E/publish/summary.md with chapters on V1 boundaries in output time
E/publish/metadata.<platform>.md
E/publish/thumbnails/NN.jpg (1280x720 and 1080x1920, <=2 MB) + contact sheet
E/publish/schedule.md and E/publish/publish-log.md (append-only)
site-<business-slug>/public/videos/<project-slug>/{promo.mp4, poster-promo.jpg} with the verified URL
status.md state per export: delivered / published / scheduled / PARKED

Stops and asks

the review gate passed before any site or account delivery
the publishing consent scope in brief.md
a verbatim per-post confirmation (privacy, AIGC, branded content, music, preview) before every single post — a repost of a new cut needs a fresh one

Steps it cannot do through an API, and hands you instead: TikTok not connected -> files plus metadata for manual upload; the user follows the tiktok_connect URL themselves; every non-TikTok platform is files plus metadata for manual upload — stated, never implied as posted; Vercel not READY -> the file stays in the repo, the build log line is reported, and the URL claim parks; a post already live can only be deleted by the user on the platform; the steps are given plainly.

How it runs

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

Step 0 — Environment check + inputs + project folder
Step 1 — Summary, chapters, titles, hashtags
Step 2 — Thumbnails from real frames
Step 3 — Delivery
Step 4 — Posting (only with per-post consent)
Step 5 — Scheduling