Repurpose existing content into a native Threads post

Threads repurposer

by sergebulaev · MIT license · ★ 49 on GitHub

Repurpose existing content into a native Threads post or thread. Take a LinkedIn post, X thread, blog, YouTube script, or newsletter and rewrite it for Threads: warm the tone, de-corporate it, refit to a short post or light thread,…

---
name: threads-repurposer
description: "Repurpose existing content into a native Threads post or thread. Take a LinkedIn post, X thread, blog, YouTube script, or newsletter and rewrite it for Threads: warm the tone, de-corporate it, refit to a short post or light thread, rebuild the hook to clear the soft fold, strip off-platform artifacts, run the humanizer, publish via Publora on approval. Not for writing from scratch (use threads-post-writer), auditing a draft (use threads-humanizer), or a hook teardown (use threads-hook-extractor)."
---

# Threads Repurposer

Turn something you already made into a Threads post or thread that reads like it
was born on Threads. Repurposing is not copy-paste. A post that killed on
LinkedIn or landed on X will read wrong on Threads if you paste it: too polished,
too cold, wrong length, and artifacts ("link in bio", hashtag walls, "smash
subscribe") that scream off-platform.

This skill transforms, it does not generate. It reads your source, keeps the
idea, and rebuilds the delivery for Threads: warmer, lowercase-casual,
reply-driven.

## When to use

Overview

Turn something you already made into a Threads post or thread that reads like it was born on Threads. Repurposing is not copy-paste. A post that killed on LinkedIn or landed on X will read wrong on Threads if you paste it: too polished, too cold, wrong length, and artifacts ("link in bio", hashtag walls, "smash subscribe") that scream off-platform.

Manual install (npx, ZIP)

Claude Codenpx skills add sergebulaev/threads-skills --skill threads-repurposer -g -a claude-code

Claude Code (degit)npx degit sergebulaev/threads-skills/skills/threads-repurposer#main ~/.claude/skills/threads-repurposer

Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.

Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

SKILL.md7.7 KB

Read SKILL.md here

sergebulaev/main1 file shown

SKILL.md7.7 KB

Browse every file on GitHub↗

SKILL.md

Show the full text135 lines

threads-repurposer/SKILL.md135 lines · 7.7 KB

PreviewCode

Outline

RawView on GitHub

Threads Repurposer

This skill transforms, it does not generate. It reads your source, keeps the idea, and rebuilds the delivery for Threads: warmer, lowercase-casual, reply-driven.

When to use

"Turn this LinkedIn post into a Threads post / thread"
"Repurpose my blog post / newsletter / YouTube script for Threads"
"This X thread did well, adapt it for Threads"
"I have a rough idea in another format, make it native here"

Not for a blank-page draft (use threads-post-writer for a post or thread), not for reviewing an already-Threads draft (use threads-humanizer, plus --mode audit), and not for reverse-engineering a hook (use threads-hook-extractor).

How it works

Voice profile first (all drafts). If ../../references/voice-profile.md has filled: yes, load it and match the user's voice fingerprint, hard rules, and CTA/link style throughout. If it is not filled, mention once that threads-humanizer --mode profile can learn their voice from a few posts, then proceed with the generic voice rules.

Take the source. Any format: a post, a paragraph, a script, a caption, a transcript, a bullet list, a link to read. Ask for the source and the goal (replies / reposts / likes / quotes) if not given.
Extract the spine. Strip the source platform's shell and pull out the one claim, the one story, or the one number worth keeping. Most repurposing fails because it keeps the words instead of the point.
Choose the container. One claim or number -> single post. A teach or a build -> a light thread (hand structure to threads-post-writer's shapes). A LinkedIn carousel or a listicle -> a short thread, one item per post, hook rebuilt. A long video -> a thread that delivers the payoff, not a summary. Threads leans short: prefer one warm post over a long thread when the idea fits.
Warm the tone. Threads is conversational and lowercase-casual. De-corporate a LinkedIn source (cut the polish and the humble-brag frame), and turn a transplanted X dunk into an invitation to talk. The register is a person talking, not a brand broadcasting.
Rebuild the hook. Threads has a soft fold (the feed truncates long posts with a "more" cut), so line one must land the whole punch and stand alone. The source's hook almost never survives; write a new first line using a 2026 Threads formula (see ../../references/hook-formulas.md), picked by the goal.
Refit the format. Under 500 chars per post (10,000 only with a text attachment). One idea per post, line breaks as beats. Cut the source's connective tissue. For a thread, hand-split with --- so the user sees the breaks before approving.
Strip off-platform artifacts. Remove "link in bio", "smash subscribe", "read more below", hashtag walls (Threads allows one hashtag max), @-handles that only exist elsewhere, and any "as I wrote on LinkedIn" throat-clearing. A repurposed post should not admit it was repurposed.
Humanizer pass. Run threads-humanizer V3: 2026 AI vocab by density, em dashes above the cap (at most one per post, never swapped for a period), stacked rule-of-three triads, generic openers and reveal bridges. Leave the rhythm alone (uniform rhythm wins on Threads; never insert a punch post for variance). Keep the user's real numbers and named entities from the source.
Approval card. Show: source -> Threads mapping (what became what), the container (single post or N-post thread with per-post char counts), formula used, warmed-tone note, primary goal. Confirm any --- breaks.
On approval. Publish via lib.publish(kind="post" (single) or kind="thread", draft_text=<approved>, target_url="https://www.threads.com/", platforms=[<THREADS_PLATFORM_ID>], scheduled_time=<iso_or_None>). The wrapper handles Publora / manual / diy routing. Publora auto-splits an over-length draft into a connected thread at paragraph then sentence boundaries.

Native-fit rules (source -> Threads)

LinkedIn post -> Threads: warm it, cut the polish. Drop the corporate frame and the humble-brag. The LinkedIn hook is too long and too formal; rewrite it lowercase-casual as a person talking.
X thread -> Threads: soften the combat tone. A sharp dunk becomes an invitation to talk. Keep the point, lose the edge that reads cold here.
Blog / newsletter -> Threads: pick the one human take, lead with it, and end on a question. Do not summarize the whole piece.
YouTube script -> Threads: lead with the payoff, not the intro. "here's what surprised me" beats "in this video".
Carousel / listicle -> thread: one item per post, each with its own micro-hook, not a wall.
Instagram / TikTok caption -> Threads: strip emoji density and hashtag blocks; Threads reads them as noise and caps hashtags at one.

Hard rules

Global voice rules: see root SKILL.md Voice rules. Additional skill-specific rules:

Keep the source's claim and facts intact. Repurposing changes the delivery, never the meaning or the numbers.
The new first line must stop the scroll on its own, past the soft fold. If it needs line two to make sense, rewrite it.
Never paste the source verbatim and trim. Rebuild the hook and rhythm from the spine.
Warm the tone every time. A cold, combative import is the most common failure.
One specific number where the source offers one. Keep it.
One hashtag maximum. A second is rejected by Threads, not just bad style.
Do not hard-sell the user's product. One natural mention max.

Anti-patterns (skill will refuse)

Copy-pasting the source with light edits (that is not repurposing).
Keeping the source platform's artifacts ("link in bio", "smash subscribe", hashtag walls, off-platform @-handles).
Importing a cold, combative X voice instead of warming it.
ALL CAPS first line for intensity. Carry it with word choice.
Em dashes above the cap (more than one in a post), or an em dash swapped for a period.
"The result?" / "Here's what" reveal bridges and staccato stacks added during the rewrite.
Rule-of-three lists without specifics.
"leverage", "fundamentally", "game-changer", "deep dive".
An external link in post 1 (offer a reply).
A second hashtag.
Meta throat-clearing ("I originally posted this on...").

Resources

../../references/hook-formulas.md - the 13 Threads formula skeletons to re-hook with (T1-T6 and T11-T13 single, T7-T10 thread)
../../references/algorithm-heuristics.md - 2026 Threads ranking rules (signals, timing, limits)

threads-post-writer - write a fresh post or thread from scratch (repurposer hands long builds to its shapes)
threads-humanizer - scrub AI tells, plus --mode audit to review the result
threads-hook-extractor - reverse-engineer a hook from a post you admire

1	---
2	name: threads-repurposer
3	description: "Repurpose existing content into a native Threads post or thread. Take a LinkedIn post, X thread, blog, YouTube script, or newsletter and rewrite it for Threads: warm the tone, de-corporate it, refit to a short post or light thread, rebuild the hook to clear the soft fold, strip off-platform artifacts, run the humanizer, publish via Publora on approval. Not for writing from scratch (use threads-post-writer), auditing a draft (use threads-humanizer), or a hook teardown (use threads-hook-extractor)."
4	---
5
6	# Threads Repurposer
7
8	Turn something you already made into a Threads post or thread that reads like it
9	was born on Threads. Repurposing is not copy-paste. A post that killed on
10	LinkedIn or landed on X will read wrong on Threads if you paste it: too polished,
11	too cold, wrong length, and artifacts ("link in bio", hashtag walls, "smash
12	subscribe") that scream off-platform.
13
14	This skill transforms, it does not generate. It reads your source, keeps the
15	idea, and rebuilds the delivery for Threads: warmer, lowercase-casual,
16	reply-driven.
17
18	## When to use
19
20	- "Turn this LinkedIn post into a Threads post / thread"
21	- "Repurpose my blog post / newsletter / YouTube script for Threads"
22	- "This X thread did well, adapt it for Threads"
23	- "I have a rough idea in another format, make it native here"
24
25	Not for a blank-page draft (use `threads-post-writer` for a post or thread), not
26	for reviewing an already-Threads draft (use `threads-humanizer`, plus
27	`--mode audit`), and not for reverse-engineering a hook (use
28	`threads-hook-extractor`).
29
30	## How it works
31
32	Voice profile first (all drafts). If `../../references/voice-profile.md` has `filled: yes`, load it and match the user's voice fingerprint, hard rules, and CTA/link style throughout. If it is not filled, mention once that `threads-humanizer --mode profile` can learn their voice from a few posts, then proceed with the generic voice rules.
33
34	1. Take the source. Any format: a post, a paragraph, a script, a caption, a
35	transcript, a bullet list, a link to read. Ask for the source and the goal
36	(replies / reposts / likes / quotes) if not given.
37	2. Extract the spine. Strip the source platform's shell and pull out the one
38	claim, the one story, or the one number worth keeping. Most repurposing fails
39	because it keeps the words instead of the point.
40	3. Choose the container. One claim or number -> single post. A teach or a
41	build -> a light thread (hand structure to `threads-post-writer`'s shapes). A
42	LinkedIn carousel or a listicle -> a short thread, one item per post, hook
43	rebuilt. A long video -> a thread that delivers the payoff, not a summary.
44	Threads leans short: prefer one warm post over a long thread when the idea
45	fits.
46	4. Warm the tone. Threads is conversational and lowercase-casual. De-corporate
47	a LinkedIn source (cut the polish and the humble-brag frame), and turn a
48	transplanted X dunk into an invitation to talk. The register is a person
49	talking, not a brand broadcasting.
50	5. Rebuild the hook. Threads has a soft fold (the feed truncates long posts
51	with a "more" cut), so line one must land the whole punch and stand alone. The
52	source's hook almost never survives; write a new first line using a 2026
53	Threads formula (see `../../references/hook-formulas.md`), picked by the goal.
54	6. Refit the format. Under 500 chars per post (10,000 only with a text
55	attachment). One idea per post, line breaks as beats. Cut the source's
56	connective tissue. For a thread, hand-split with `---` so the user sees the
57	breaks before approving.
58	7. Strip off-platform artifacts. Remove "link in bio", "smash subscribe",
59	"read more below", hashtag walls (Threads allows one hashtag max), @-handles
60	that only exist elsewhere, and any "as I wrote on LinkedIn" throat-clearing. A
61	repurposed post should not admit it was repurposed.
62	8. Humanizer pass. Run `threads-humanizer` V3: 2026 AI vocab by density,
63	em dashes above the cap (at most one per post, never swapped for a
64	period), stacked rule-of-three triads, generic openers and reveal bridges.
65	Leave the rhythm alone (uniform rhythm wins on Threads; never insert a
66	punch post for variance). Keep the user's real numbers and named entities
67	from the source.
68	9. Approval card. Show: source -> Threads mapping (what became what), the
69	container (single post or N-post thread with per-post char counts), formula
70	used, warmed-tone note, primary goal. Confirm any `---` breaks.
71	10. On approval. Publish via `lib.publish(kind="post"` (single) or
72	`kind="thread"`, `draft_text=<approved>,
73	target_url="https://www.threads.com/", platforms=[<THREADS_PLATFORM_ID>],
74	scheduled_time=<iso_or_None>)`. The wrapper handles Publora / manual / diy
75	routing. Publora auto-splits an over-length draft into a connected thread at
76	paragraph then sentence boundaries.
77
78	## Native-fit rules (source -> Threads)
79
80	- LinkedIn post -> Threads: warm it, cut the polish. Drop the corporate frame
81	and the humble-brag. The LinkedIn hook is too long and too formal; rewrite it
82	lowercase-casual as a person talking.
83	- X thread -> Threads: soften the combat tone. A sharp dunk becomes an
84	invitation to talk. Keep the point, lose the edge that reads cold here.
85	- Blog / newsletter -> Threads: pick the one human take, lead with it, and end
86	on a question. Do not summarize the whole piece.
87	- YouTube script -> Threads: lead with the payoff, not the intro. "here's what
88	surprised me" beats "in this video".
89	- Carousel / listicle -> thread: one item per post, each with its own
90	micro-hook, not a wall.
91	- Instagram / TikTok caption -> Threads: strip emoji density and hashtag
92	blocks; Threads reads them as noise and caps hashtags at one.
93
94	## Hard rules
95
96	Global voice rules: see root `SKILL.md` Voice rules. Additional skill-specific
97	rules:
98
99	- Keep the source's claim and facts intact. Repurposing changes the delivery,
100	never the meaning or the numbers.
101	- The new first line must stop the scroll on its own, past the soft fold. If it
102	needs line two to make sense, rewrite it.
103	- Never paste the source verbatim and trim. Rebuild the hook and rhythm from the
104	spine.
105	- Warm the tone every time. A cold, combative import is the most common failure.
106	- One specific number where the source offers one. Keep it.
107	- One hashtag maximum. A second is rejected by Threads, not just bad style.
108	- Do not hard-sell the user's product. One natural mention max.
109
110	## Anti-patterns (skill will refuse)
111
112	- Copy-pasting the source with light edits (that is not repurposing).
113	- Keeping the source platform's artifacts ("link in bio", "smash subscribe",
114	hashtag walls, off-platform @-handles).
115	- Importing a cold, combative X voice instead of warming it.
116	- ALL CAPS first line for intensity. Carry it with word choice.
117	- Em dashes above the cap (more than one in a post), or an em dash swapped for a period.
118	- "The result?" / "Here's what" reveal bridges and staccato stacks added during the rewrite.
119	- Rule-of-three lists without specifics.
120	- "leverage", "fundamentally", "game-changer", "deep dive".
121	- An external link in post 1 (offer a reply).
122	- A second hashtag.
123	- Meta throat-clearing ("I originally posted this on...").
124
125	## Resources
126
127	- `../../references/hook-formulas.md` - the 13 Threads formula skeletons to re-hook with (T1-T6 and T11-T13 single, T7-T10 thread)
128	- `../../references/algorithm-heuristics.md` - 2026 Threads ranking rules (signals, timing, limits)
129
130	## Related skills
131
132	- `threads-post-writer` - write a fresh post or thread from scratch (repurposer hands long builds to its shapes)
133	- `threads-humanizer` - scrub AI tells, plus `--mode audit` to review the result
134	- `threads-hook-extractor` - reverse-engineer a hook from a post you admire
135