cross-platform-repurposing

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

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.

此技能可将一个想法转化为多篇帖子——这是实现可持续内容产出的最大抓手。一篇博客可以变成一周的社交内容；一个精彩见解可以转化为五篇适配各平台原生风格的帖子。小团队借此能拥有大团队的内容产出能力。

让它奏效的核心原则，也是多数尝试失败的陷阱：

复用不是重复发布。把相同文案粘贴到所有平台是偷懒的做法：它完全不符合任何平台的原生风格，对于在多个平台关注你的用户来说，这看起来像垃圾信息，而且不少平台会悄悄压制明显跨平台复制的内容。真正的技巧是拆分核心→适配平台：提取核心观点，然后为每个目标平台重新打造原生内容——钩子、格式、篇幅和行动号召（CTA）各不相同，但核心信息和品牌调性保持一致。

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.

将单篇帖子分发至多个平台（一到多）。
将长内容（博客、视频、播客、通讯）拆分为多篇短帖子（长到短）。
将一种格式转化为其他格式（文字见解→图文轮播、Reel、推文串）。
在
```
batch-content-plan
```
中使用，将有限的原始素材拓展为完整的内容日历。

请勿使用的场景：当内容具有极强平台特异性时（比如圈内梗、平台原生趋势、回复内容）——强行移植到其他平台会显得格格不入。另外，当两个平台的受众高度重叠时，要改变内容的切入角度，而不只是转移帖子。要清楚哪些内容不适合跨平台传播。

Step 0 — Read the foundation first

步骤0 — 先读取基础资料

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.

加载

brand-profile.md

和

voice.md

。品牌调性在所有平台保持一致；语气风格则随平台调整（参考语气风格对照表——LinkedIn更正式，TikTok更随性）。所有操作都要遵循既定规范。

Step 1 — Atomize: find the core idea

步骤1 — 拆分核心：提炼核心观点

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

从源内容中提取可复用的核心单元——核心论点、见解、故事、数据、关键瞬间。对于单篇帖子，通常是一个核心单元；对于长内容（博客、20分钟视频），则是多个核心单元，每个单元都足够支撑一篇独立帖子。不要把长内容总结成一篇单薄的帖子——要提取其中最优质的5-10个核心单元。详见

references/repurposing-model.md

。

Step 2 — Pick targets and direction

步骤2 — 选择目标平台与转化方向

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.

确定目标平台和转化方向（一到多、长到短、格式转格式、视频↔文字——详见

references/source-types.md

）。转化方向决定具体操作机制。

Step 3 — Re-native per platform (don't translate, rebuild)

步骤3 — 为各平台打造原生内容（不是翻译，是重构）

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

针对每个目标平台，基于核心单元重构原生内容——组合合适的技能：

每个平台配专属钩子（
```
hook-writer
```
）——LinkedIn信息流的钩子和TikTok首帧的钩子截然不同。
适配平台的格式与篇幅。
撰写文案（
```
caption-writer
```
），如果是视频则编写脚本（
```
reels-script
```
），或者创作推文串（
```
thread-writer
```
）。
运用平台原生机制——话题标签、链接（个人简介链接、可点击链接、评论区链接）、行动号召（CTA）。

保持不变的：核心单元和品牌调性。需要改变的：钩子、格式、篇幅、结构、行动号召、互动机制、语气风格。详见

references/platform-transforms.md

。

Step 4 — Quality-check: does each stand alone and feel native?

步骤4 — 质量检查：每个版本是否独立且贴合平台？

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.

每个版本都必须通过两项测试：

独立成立——只看到这篇帖子的用户能获得完整价值（不能出现“正如我在LinkedIn上所说…”这类表述）。
贴合平台——看起来是为该平台量身打造，而非移植而来。如果能看出是复制粘贴的，就重新构建。

如果两个平台的受众高度重叠，要在内容切入角度上做区分，而不只是调整格式。

Step 5 — Hand off to scheduling

步骤5 — 交付给调度系统

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.

将完成的各平台版本交付给

scheduling-and-queue

进行调度/分发（系统会先进行确认和验证；WoopSocial会设置各平台专属字段）。注意错开发布时间——不要同一时间在所有平台发布相同的内容。

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.

你是否拆分了核心单元（提取核心观点），而非直接翻译表层内容？
每个版本是否真正适配平台原生风格——钩子、格式、篇幅、行动号召各不相同，而非简单复制粘贴？
每个版本是否能独立成立？
品牌调性是否保持一致，同时语气风格随平台调整？
对于长内容，你是否提取了多个核心单元，而非只是一篇总结？
你是否识别出哪些内容不应该被复用？

如果两个版本只是文案相同，仅话题标签不同，那你只是重复发布了——回到步骤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.

平台间受众高度重叠→调整内容的切入角度/格式，避免粉丝看到重复内容。
平台特异性内容（趋势、回复、圈内梗）→不要强行移植到其他平台；明确说明不可复用。
仅含单一观点的长内容→只有一个核心单元；不要为了凑帖子数量而制造冗余内容。
视频转文字→提取语音中的见解/语录作为文字核心单元；不要只是简单转录。
文字转视频→将核心单元交付给
```
reels-script
```
来打造视频内容；不要只是把文案读出来。
受监管/敏感内容→所有版本都要遵循合规规范。

Related skills

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.

```
references/repurposing-model.md
```
——拆分核心→适配平台；保持不变与需要调整的内容；转化方向。
```
references/platform-transforms.md
```
——一个想法如何转化为各平台原生帖子。
```
references/source-types.md
```
——按源内容类型/转化方向进行复用（长内容、多平台分发、跨媒介）。
```
references/examples.md
```
——一个想法→五个原生版本，以及长内容拆分示例。