li-repurpose

# 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: | pull | what it is | | --- | --- | | **Claims** | every sentence that would start an argument | | **Numbers** | every figure, cost, duration, percentage | | **Stories** | every moment with a person, a scene and a cost | | **Mechanisms** | every "the way this works is..." explanation | | **Mistakes** | every admission of something that went wrong | | **Lines** | every sentence that is already quotable as-is | 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. ...