li-repurpose

One good long asset contains four to six posts. Most people extract one and throw the rest away.

Input

A transcript, an article, a newsletter, a script, a call summary. If the user gives a YouTube URL and there is a transcript tool available in the session, use it; otherwise ask them to paste the text. Read the whole thing before extracting anything.

Extract, do not summarise

A summary of a video is not a post. Nobody wants the summary. Go through the asset and pull out the things that stand alone:

List what you found, with counts, before writing anything. If the asset yields fewer than four items, it is thin, and four posts squeezed out of it will be thin too. Say that.

Then build the week

Each extract becomes one post, and each post has to stand completely on its own - the reader has not seen the video and never will. Never write "as I mentioned in my latest video". The post is the thing.

Assign a hook formula from li-post/hooks.json to each, and vary them: five posts from one source with the same hook shape reads as a content mill.

Order them across the week so the strongest claim goes first, the story goes midweek, and the mechanism post goes last, when people who liked the earlier ones are watching for it.

Output

SOURCE: "Why we killed discovery calls" (18 min, 3,400 words)

FOUND  4 claims, 6 numbers, 2 stories, 3 mechanisms, 1 mistake, 5 quotable lines

WEEK
TUE  #1  Contrarian    Discovery calls are a tax you pay for a bad website
WED  #17 Time Anchor   We got 6 hours a week back by deleting one calendar link
THU  #9  Cold Open     "Can we just hop on a quick call?"
FRI  #21 Direct Value  The 4-question form that replaced the call. Steal it.

Say "write Tuesday" and I will draft it.

Then draft on request, one at a time, each through /li-post and /li-human. Do not dump four finished posts at once - they will all sound the same, and the user will edit none of them.

Scheduling the week through PostZen

When the posts are written and approved and the PostZen MCP tools are in this session, offer to schedule the week through /li-publish. Two ways to place them:

• Explicit times. Each post gets its own scheduledFor with the user's timezone offset, straight off the week above.
• The queue. Each post goes in with queuedFromProfile, and PostZen gives it the profile's next free slot. This needs a queue with slots, which /li-plan sets up. Never fetch a slot with getNextQueueSlot and pass it back as scheduledFor.

One confirmation covers the whole list, and it lists everything: each post's day and time with timezone, format, account name, visibility, first line, any media file, and anything left to do by hand (a first-comment link, say). In queue mode the time is not fixed until the call returns, so list the slots previewQueue({ profileId }) shows, say that each post takes the next free one at send time, and report the scheduledFor that comes back. Show it, get the yes, then /li-publish sends them one call at a time and checks each platforms[].status before moving on.

If anything in the list changes after the yes, the yes is spent. Show the list again.