Cross-Platform Repurposing
This skill turns one idea into many posts — the single biggest lever for producing content
sustainably. One blog post becomes a week of social; one strong insight becomes five
platform-native posts. It's how a small team posts like a big one.
The principle that makes it work — and the trap that ruins most attempts:
Repurposing is not reposting. Pasting the same caption onto every platform is the lazy
version: it fits none of them natively, it looks like spam to anyone who follows you in two
places, and several platforms quietly suppress obviously cross-posted content. The craft is
atomize → adapt: extract the core idea, then rebuild it natively for each target — a
different hook, format, length, and CTA, same truth and voice.
When to use this
- Fan one post out across platforms (one → many).
- Atomize a long piece (blog, video, podcast, newsletter) into many short posts (long → short).
- Convert one format into others (a written insight → a carousel, a Reel, a thread).
- Inside
batch-content-plan, to stretch limited raw material into a full calendar.
When NOT to use it: when content is genuinely platform-specific (an in-joke, a
platform-native trend, a reply) — forcing it elsewhere reads wrong. And when the audience
overlaps almost entirely on two platforms, vary the angle, don't just relocate the post. Know
when a piece shouldn't travel.
Step 0 — Read the foundation first
Load brand-profile.md and voice.md. Voice stays constant across platforms; register
shifts per platform (use the voice tone-map — LinkedIn more formal, TikTok looser). Carry
guardrails everywhere.
Step 1 — Atomize: find the core idea
Extract the reusable atom from the source — the point, the insight, the story, the stat, the
moment. For a single post that's usually one atom; for long-form (a blog, a 20-minute video) it's
several atoms, each strong enough to be its own post. Don't summarize a long piece into one
weak post — pull its best 5–10 atoms. See references/repurposing-model.md.
Step 2 — Pick targets and direction
Decide the platforms and the direction of the repurpose (one→many, long→short,
format→format, video↔text — see references/source-types.md). Direction determines the
mechanics.
Step 3 — Re-native per platform (don't translate, rebuild)
For each target, rebuild the atom natively — composing the right skills:
- A new hook per platform (
hook-writer) — what hooks on a LinkedIn feed differs from a
TikTok first frame.
- The right format and length for that platform.
- The copy (
caption-writer), the script if video (reels-script), or the thread
(thread-writer).
- Native mechanics — hashtags, links (bio vs clickable vs comments), CTA.
What stays the same: the atom and the voice. What changes: hook, format, length,
structure, CTA, mechanics, register. See references/platform-transforms.md.
Step 4 — Quality-check: does each stand alone and feel native?
Every version must pass two tests:
- Stands alone — someone who only sees this one post gets full value (no "as I said on
LinkedIn…").
- Feels native — it looks built for this platform, not relocated. If you can tell it was
copy-pasted, rebuild it.
If two platforms share most of the audience, change the angle between them, not just the
formatting.
Step 5 — Hand off to scheduling
Pass the finished, per-platform versions to scheduling-and-queue to schedule/fan out (it
confirms and validates first; WoopSocial applies per-platform fields). Space them out — don't
fire the same idea everywhere at the same minute.
Quality bar — self-check
- Did you atomize (extract the core idea) rather than translate the wrapper?
- Is each version genuinely native — different hook, format, length, CTA — not copy-paste?
- Does each stand on its own?
- Is the voice constant with the register shifted per platform?
- For long-form, did you pull multiple atoms, not one summary?
- Did you recognize anything that shouldn't be repurposed?
If two versions are the same text with different hashtags, you reposted — go back to Step 3.
Edge cases
- Heavy audience overlap across platforms → vary the angle/format between them so followers
don't see the same post twice.
- Platform-specific content (trends, replies, in-jokes) → don't force it elsewhere; say so.
- Long-form with one idea → it's one atom; don't manufacture filler to hit a post count.
- Video → text → pull the spoken insights/quotes as written atoms; don't just transcribe.
- Text → video → hand the atom to
reels-script to build it as a video, don't read the
caption aloud.
- Regulated/sensitive → carry compliance guardrails into every version.
Related skills
brand-profile, voice-builder — voice + register + guardrails.hook-writer — a fresh hook for each platform.caption-writer, reels-script, thread-writer — build each native version.content-recycling — repurposing across time (refresh evergreen later).captions-and-clipping, opus-clip — cutting clips from long video (podcasts, webinars) at depth.batch-content-plan — uses this to stretch material into a calendar.scheduling-and-queue — schedules/fans out the finished versions.
References
references/repurposing-model.md — atomize → adapt; what stays vs changes; the directions.references/platform-transforms.md — how one idea becomes each platform's native post.references/source-types.md — repurposing by source/direction (long-form, fan-out, cross-medium).references/examples.md — one idea → five native versions, and a long-form atomization.
1---2name: cross-platform-repurposing3description: Use to turn one piece of content into multiple platform-native posts — adapt, never copy-paste. Run when the user says "repurpose this," "turn this into posts for every platform," "cross-post," "make this work on TikTok/LinkedIn/X too," "one idea into a week of content," "turn this blog/video/podcast into social posts," or wants to fan content out. Reads brand-profile and voice first, extracts the core idea, then re-natives it for each platform (different hook, format, length, mechanics, CTA) using the content skills, and hands the fan-out to scheduling-and-queue. This is the multiplier that makes a content operation sustainable — but every version must stand on its own and feel native, never duplicated.4license: MIT5---6
7# Cross-Platform Repurposing
8
9This skill turns one idea into many posts — the single biggest lever for producing content
10sustainably. One blog post becomes a week of social; one strong insight becomes five
11platform-native posts. It's how a small team posts like a big one.
12
13The principle that makes it work — and the trap that ruins most attempts:
14
15> **Repurposing is not reposting.** Pasting the same caption onto every platform is the lazy
16> version: it fits none of them natively, it looks like spam to anyone who follows you in two
17> places, and several platforms quietly suppress obviously cross-posted content. The craft is
18> **atomize → adapt**: extract the core idea, then rebuild it natively for each target — a
19> different hook, format, length, and CTA, same truth and voice.
20
21## When to use this
22
23- Fan one post out across platforms (one → many).
24- Atomize a long piece (blog, video, podcast, newsletter) into many short posts (long → short).
25- Convert one format into others (a written insight → a carousel, a Reel, a thread).
26- Inside `batch-content-plan`, to stretch limited raw material into a full calendar.
27
28**When NOT to use it:** when content is genuinely platform-specific (an in-joke, a
29platform-native trend, a reply) — forcing it elsewhere reads wrong. And when the audience
30overlaps almost entirely on two platforms, vary the *angle*, don't just relocate the post. Know
31when a piece shouldn't travel.
32
33## Step 0 — Read the foundation first
34
35Load `brand-profile.md` and `voice.md`. Voice stays constant across platforms; **register
36shifts** per platform (use the voice tone-map — LinkedIn more formal, TikTok looser). Carry
37guardrails everywhere.
38
39## Step 1 — Atomize: find the core idea
40
41Extract the reusable **atom** from the source — the point, the insight, the story, the stat, the
42moment. For a single post that's usually one atom; for long-form (a blog, a 20-minute video) it's
43**several** atoms, each strong enough to be its own post. Don't summarize a long piece into one
44weak post — pull its best 5–10 atoms. See `references/repurposing-model.md`.
45
46## Step 2 — Pick targets and direction
47
48Decide the **platforms** and the **direction** of the repurpose (one→many, long→short,
49format→format, video↔text — see `references/source-types.md`). Direction determines the
50mechanics.
51
52## Step 3 — Re-native per platform (don't translate, rebuild)
53
54For each target, rebuild the atom natively — composing the right skills:
55
56- **A new hook per platform** (`hook-writer`) — what hooks on a LinkedIn feed differs from a
57 TikTok first frame.
58- **The right format and length** for that platform.
59- **The copy** (`caption-writer`), the **script** if video (`reels-script`), or the **thread**
60 (`thread-writer`).
61- **Native mechanics** — hashtags, links (bio vs clickable vs comments), CTA.
62
63What stays the same: the **atom** and the **voice**. What changes: hook, format, length,
64structure, CTA, mechanics, register. See `references/platform-transforms.md`.
65
66## Step 4 — Quality-check: does each stand alone and feel native?
67
68Every version must pass two tests:
69
701. **Stands alone** — someone who only sees this one post gets full value (no "as I said on
71 LinkedIn…").
722. **Feels native** — it looks built *for* this platform, not relocated. If you can tell it was
73 copy-pasted, rebuild it.
74
75If two platforms share most of the audience, change the *angle* between them, not just the
76formatting.
77
78## Step 5 — Hand off to scheduling
79
80Pass the finished, per-platform versions to `scheduling-and-queue` to schedule/fan out (it
81confirms and validates first; WoopSocial applies per-platform fields). Space them out — don't
82fire the same idea everywhere at the same minute.
83
84## Quality bar — self-check
85
86- Did you **atomize** (extract the core idea) rather than translate the wrapper?
87- Is each version **genuinely native** — different hook, format, length, CTA — not copy-paste?
88- Does each **stand on its own**?
89- Is the **voice constant** with the **register shifted** per platform?
90- For long-form, did you pull **multiple atoms**, not one summary?
91- Did you recognize anything that **shouldn't** be repurposed?
92
93If two versions are the same text with different hashtags, you reposted — go back to Step 3.
94
95## Edge cases
96
97- **Heavy audience overlap across platforms** → vary the angle/format between them so followers
98 don't see the same post twice.
99- **Platform-specific content** (trends, replies, in-jokes) → don't force it elsewhere; say so.
100- **Long-form with one idea** → it's one atom; don't manufacture filler to hit a post count.
101- **Video → text** → pull the spoken insights/quotes as written atoms; don't just transcribe.
102- **Text → video** → hand the atom to `reels-script` to build it as a video, don't read the
103 caption aloud.
104- **Regulated/sensitive** → carry compliance guardrails into every version.
105
106## Related skills
107
108- `brand-profile`, `voice-builder` — voice + register + guardrails.
109- `hook-writer` — a fresh hook for each platform.
110- `caption-writer`, `reels-script`, `thread-writer` — build each native version.
111- `content-recycling` — repurposing across **time** (refresh evergreen later).
112- `captions-and-clipping`, `opus-clip` — cutting clips from long video (podcasts, webinars) at depth.
113- `batch-content-plan` — uses this to stretch material into a calendar.
114- `scheduling-and-queue` — schedules/fans out the finished versions.
115
116## References
117
118- `references/repurposing-model.md` — atomize → adapt; what stays vs changes; the directions.
119- `references/platform-transforms.md` — how one idea becomes each platform's native post.
120- `references/source-types.md` — repurposing by source/direction (long-form, fan-out, cross-medium).
121- `references/examples.md` — one idea → five native versions, and a long-form atomization.
social-media-skills