Back to Details

crosspost

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Crosspost

跨平台分发内容

Distribute content across multiple social platforms with platform-native adaptation.
针对多社交平台分发内容，并做平台原生适配。

When to Use

适用场景

  • User wants to post content to multiple platforms
  • Publishing announcements, launches, or updates across social media
  • Repurposing a post from one platform to others
  • User says "crosspost", "post everywhere", "share on all platforms", or "distribute this"
  • 用户需要将内容发布到多个平台
  • 在社交媒体上发布公告、产品上线或更新信息
  • 将某一平台的内容改编后发布到其他平台
  • 用户提到“跨平台发布”、“全平台发布”、“所有平台分享”或“分发此内容”等需求

How It Works

工作原理

Core Rules

核心规则

  1. Never post identical content cross-platform. Each platform gets a native adaptation.
  2. Primary platform first. Post to the main platform, then adapt for others.
  3. Respect platform conventions. Length limits, formatting, link handling all differ.
  4. One idea per post. If the source content has multiple ideas, split across posts.
  5. Attribution matters. If crossposting someone else's content, credit the source.
  1. 绝不在跨平台发布相同内容。每个平台的内容都要做原生适配。
  2. 优先主平台。先发布到主平台，再为其他平台做适配。
  3. 遵循平台规范。各平台的字数限制、格式要求、链接处理方式均不同。
  4. 单条内容一个核心观点。如果源内容包含多个观点，拆分到不同帖子中发布。
  5. 注明来源。如果分发的是他人内容，需注明原作者。

Platform Specifications

平台规格

PlatformMax LengthLink HandlingHashtagsMedia
X280 chars (4000 for Premium)Counted in lengthMinimal (1-2 max)Images, video, GIFs
LinkedIn3000 charsNot counted in length3-5 relevantImages, video, docs, carousels
Threads500 charsSeparate link attachmentNone typicalImages, video
Bluesky300 charsVia facets (rich text)None (use feeds)Images
平台最大字数链接处理方式话题标签媒体支持
X280字符（高级版为4000字符）计入字数少量使用（最多1-2个）图片、视频、动图
LinkedIn3000字符不计入字数3-5个相关标签图片、视频、文档、轮播图
Threads500字符作为独立链接附件通常不使用图片、视频
Bluesky300字符通过富文本片段（facets）添加不使用（使用订阅源）图片

Workflow

工作流程

Step 1: Create Source Content

步骤1：创建源内容

Start with the core idea. Use 
content-engine
skill for high-quality drafts:
  • Identify the single core message
  • Determine the primary platform (where the audience is biggest)
  • Draft the primary platform version first
从核心观点入手，使用
content-engine
技能生成高质量草稿：
  • 明确单一核心信息
  • 确定主平台（受众最多的平台）
  • 先起草主平台版本的内容

Step 2: Identify Target Platforms

步骤2：确定目标平台

Ask the user or determine from context:
  • Which platforms to target
  • Priority order (primary gets the best version)
  • Any platform-specific requirements (e.g., LinkedIn needs professional tone)
询问用户或根据上下文判断：
  • 要发布到哪些平台
  • 优先级顺序（主平台使用最优版本）
  • 任何平台特定要求（例如LinkedIn需要专业语气）

Step 3: Adapt Per Platform

步骤3：平台适配

For each target platform, transform the content:
X adaptation:
  • Open with a hook, not a summary
  • Cut to the core insight fast
  • Keep links out of main body when possible
  • Use thread format for longer content
LinkedIn adaptation:
  • Strong first line (visible before "see more")
  • Short paragraphs with line breaks
  • Frame around lessons, results, or professional takeaways
  • More explicit context than X (LinkedIn audience needs framing)
Threads adaptation:
  • Conversational, casual tone
  • Shorter than LinkedIn, less compressed than X
  • Visual-first if possible
Bluesky adaptation:
  • Direct and concise (300 char limit)
  • Community-oriented tone
  • Use feeds/lists for topic targeting instead of hashtags
针对每个目标平台，调整内容：
X平台适配：
  • 以钩子开头，而非总结
  • 快速切入核心观点
  • 尽可能将链接放在正文之外
  • 较长内容使用线程式发布
LinkedIn平台适配：
  • 开头第一句要有吸引力（在“查看更多”前可见）
  • 段落简短并添加换行
  • 围绕经验总结、成果或专业见解展开
  • 比X平台提供更明确的背景信息（LinkedIn受众需要背景铺垫）
Threads平台适配：
  • 语气口语化、随意
  • 比LinkedIn短，比X平台宽松
  • 尽可能优先视觉内容
Bluesky平台适配：
  • 直接简洁（300字符限制）
  • 社区导向语气
  • 使用订阅源/列表进行话题定位，而非话题标签

Step 4: Post Primary Platform

步骤4：发布主平台内容

Post to the primary platform first:
  • Use 
    x-api
    skill for X
  • Use platform-specific APIs or tools for others
  • Capture the post URL for cross-referencing
先发布主平台内容：
  • 使用
    x-api
    技能发布到X平台
  • 使用各平台专属API或工具发布到其他平台
  • 记录帖子URL用于跨平台引用

Step 5: Post to Secondary Platforms

步骤5：发布到次级平台

Post adapted versions to remaining platforms:
  • Stagger timing (not all at once — 30-60 min gaps)
  • Include cross-platform references where appropriate ("longer thread on X" etc.)
将适配后的版本发布到剩余平台：
  • 错开发布时间（不要同时发布，间隔30-60分钟）
  • 适当添加跨平台引用（例如“在X平台查看完整线程”等）

Examples

示例

Source: Product Launch

示例：产品上线

X version:
We just shipped [feature].

[One specific thing it does that's impressive]

[Link]
LinkedIn version:
Excited to share: we just launched [feature] at [Company].

Here's why it matters:

[2-3 short paragraphs with context]

[Takeaway for the audience]

[Link]
Threads version:
just shipped something cool — [feature]

[casual explanation of what it does]

link in bio
X平台版本：
We just shipped [feature].

[One specific thing it does that's impressive]

[Link]
LinkedIn平台版本：
Excited to share: we just launched [feature] at [Company].

Here's why it matters:

[2-3 short paragraphs with context]

[Takeaway for the audience]

[Link]
Threads平台版本：
just shipped something cool — [feature]

[casual explanation of what it does]

link in bio

Source: Technical Insight

示例：技术见解

X version:
TIL: [specific technical insight]

[Why it matters in one sentence]
LinkedIn version:
A pattern I've been using that's made a real difference:

[Technical insight with professional framing]

[How it applies to teams/orgs]

#relevantHashtag
X平台版本：
TIL: [specific technical insight]

[Why it matters in one sentence]
LinkedIn平台版本：
A pattern I've been using that's made a real difference:

[Technical insight with professional framing]

[How it applies to teams/orgs]

#relevantHashtag

API Integration

API集成

Batch Crossposting Service (Example Pattern)

批量跨平台分发服务（示例模式）

If using a crossposting service (e.g., Postbridge, Buffer, or a custom API), the pattern looks like:
python
import os
import requests

resp = requests.post(
    "https://your-crosspost-service.example/api/posts",
    headers={"Authorization": f"Bearer {os.environ['POSTBRIDGE_API_KEY']}"},
    json={
        "platforms": ["twitter", "linkedin", "threads"],
        "content": {
            "twitter": {"text": x_version},
            "linkedin": {"text": linkedin_version},
            "threads": {"text": threads_version}
        }
    },
    timeout=30
)
resp.raise_for_status()
如果使用跨平台分发服务（例如Postbridge、Buffer或自定义API），模式如下：
python
import os
import requests

resp = requests.post(
    "https://your-crosspost-service.example/api/posts",
    headers={"Authorization": f"Bearer {os.environ['POSTBRIDGE_API_KEY']}"},
    json={
        "platforms": ["twitter", "linkedin", "threads"],
        "content": {
            "twitter": {"text": x_version},
            "linkedin": {"text": linkedin_version},
            "threads": {"text": threads_version}
        }
    },
    timeout=30
)
resp.raise_for_status()

Manual Posting

手动发布

Without Postbridge, post to each platform using its native API:
  • X: Use 
    x-api
    skill patterns
  • LinkedIn: LinkedIn API v2 with OAuth 2.0
  • Threads: Threads API (Meta)
  • Bluesky: AT Protocol API
如果不使用Postbridge，可通过各平台原生API发布：
  • X平台：使用
    x-api
    技能模式
  • LinkedIn：使用带OAuth 2.0的LinkedIn API v2
  • Threads：Meta旗下Threads API
  • Bluesky：AT Protocol API

Quality Gate

质量检查

Before posting:
  • Each platform version reads naturally for that platform
  • No identical content across platforms
  • Length limits respected
  • Links work and are placed appropriately
  • Tone matches platform conventions
  • Media is sized correctly for each platform
发布前检查：
  • 各平台版本符合该平台的自然阅读习惯
  • 跨平台无重复内容
  • 遵守字数限制
  • 链接有效且放置合理
  • 语气符合平台规范
  • 媒体尺寸适配各平台

Related Skills

相关技能

  • content-engine
    — Generate platform-native content
  • x-api
    — X/Twitter API integration
  • content-engine
    — 生成平台原生内容
  • x-api
    — X/Twitter API集成