← ClaudeAtlas

th-repurposelisted

Turn one long asset - a YouTube video, podcast, newsletter, blog post, LinkedIn post, transcript or client call - into a week of Threads posts and chains. Use when the user says "repurpose this for Threads", "turn this into threads", "I have a video/newsletter/transcript", or pastes long content and wants it on Threads.
Athurlux/threads-agent-skill · ★ 0 · AI & Automation · score 70
Install: claude install-skill Athurlux/threads-agent-skill
# th-repurpose One good long asset holds five to ten Threads posts. Threads posts are short, so a single asset stretches further here than anywhere else. Most people pull out one and throw the rest away. ## Input A transcript, article, newsletter, script, call summary, or a long post from another platform. If the user gives a YouTube URL and a transcript tool is available in the session, use it. Otherwise ask them to paste the text. Read all of it before extracting anything. ## Extract, do not summarise A summary is not a post. Go through the asset and pull out what stands alone: | pull | what it is | usually becomes | | --- | --- | --- | | **Claims** | sentences that would start an argument | a single post | | **Numbers** | every figure, cost, duration, percentage | a single post | | **Lines** | sentences quotable exactly as they are | a single post | | **Mistakes** | admissions of something that went wrong | a single post | | **Stories** | a person, a scene and a cost | a chain of 3-4 | | **Mechanisms** | "the way this works is..." | a chain of 3-6 | List what you found, with counts, before writing anything. If there are fewer than four items, the asset is thin, and say so rather than squeezing it. ## Then build the week Each extract becomes one post or one chain, and each has to stand on its own. The reader has not seen the video and never will. Never write "as I said in my latest video". The post is the thing. A link back to the source, if the user wants one, goe