Crosspost
Adapt one piece of source content into platform-native drafts for multiple platforms. This skill produces the drafts and a suggested posting order — actual publishing is done by the user.
When to Activate
- User wants content drafted for multiple platforms
- Announcements, launches, or updates going out across social media
- Repurposing a post from one platform to others
- Repurposing articles, podcasts, demos, or docs into social content
- Scripting short-form video or YouTube versions of existing content
- User says "crosspost", "post everywhere", "share on all platforms", or "distribute this"
Core Rules
- Never draft identical content cross-platform. Each platform gets a native adaptation.
- Primary platform first. Draft the main platform's version first, then adapt for others.
- Respect platform conventions. Length limits, formatting, link handling all differ.
- One idea per post. If the source content has multiple ideas, split across posts.
- Attribution matters. If crossposting someone else's content, credit the source.
- Hooks matter more than summaries. Use specifics over slogans; keep the ask small and clear.
Platform Specifications
Text platforms:
| Platform |
Max Length |
Link Handling |
Hashtags |
Media |
| X |
280 chars (4000 for Premium) |
Counted in length |
Minimal (1-2 max) |
Images, video, GIFs |
| LinkedIn |
3000 chars |
Not counted in length |
3-5 relevant |
Images, video, docs, carousels |
| Threads |
500 chars |
Separate link attachment |
None typical |
Images, video |
| Bluesky |
300 chars |
Via facets (rich text) |
None (use feeds) |
Images |
Video and long-form targets (TikTok/short video, YouTube, newsletter) have no hard character limits — their adaptation notes are in Step 3.
Workflow
Step 1: Create Source Content
Start with the core idea:
- Identify the single core message
- Determine the primary platform (where the audience is biggest)
- Draft the primary platform version first
Before drafting, clarify if not obvious from context:
- Source asset: what are we adapting from (article, video, demo, memo, launch doc)
- Audience: builders, investors, customers, operators, or general audience
- Goal: awareness, conversion, recruiting, authority, launch support, or engagement
Step 2: Identify Target Platforms
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)
Step 3: Adapt Per Platform
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
TikTok / short video adaptation:
- First 3 seconds must interrupt attention
- Script around visuals, not just narration
- One demo, one claim, one CTA
YouTube adaptation:
- Show the result early
- Structure by chapter
- Refresh the visual every 20-30 seconds
Newsletter adaptation:
- Deliver one clear lens, not a bundle of unrelated items
- Make section titles skimmable
- Keep the opening paragraph doing real work
Step 4: Deliver Drafts and Posting Order
Hand the user the full set of platform versions, plus a suggested rollout:
- Primary platform first, then secondary platforms
- Stagger timing (not all at once — 30-60 min gaps)
- Include cross-platform references where appropriate ("longer thread on X" etc.)
- Note any missing inputs needed before publishing (links, media, handles)
This skill does not post. Publishing to each platform is the user's step.
Repurposing Cascade
When adapting a larger source asset (article, podcast, demo, launch doc) into a multi-platform campaign, follow this cascade:
- Anchor asset — start from the article, video, demo, memo, or launch doc
- Extract 3-7 atomic ideas — each stands alone as one post
- Write platform-native variants — apply the Step 3 adaptations per idea
- Trim repetition across outputs — no duplicated copy across platforms unless requested
- Align CTAs with platform intent — the ask on LinkedIn differs from the ask on X or in a newsletter
When asked for a full campaign, return: the core angle, platform-specific drafts, optional posting order, optional CTA variants, and any missing inputs needed before publishing.
Content Adaptation 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
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
Quality Gate
Before delivering drafts:
1---2name: crosspost3description: Multi-platform content adaptation across X, LinkedIn, Threads, Bluesky, TikTok, YouTube, and newsletters. Drafts a platform-native version for each target platform — it does not post or publish anything. Never produces identical copy cross-platform. Use when the user wants to distribute or repurpose content across platforms.4---56# Crosspost78Adapt one piece of source content into platform-native drafts for multiple platforms. This skill produces the drafts and a suggested posting order — actual publishing is done by the user.910## When to Activate1112- User wants content drafted for multiple platforms13- Announcements, launches, or updates going out across social media14- Repurposing a post from one platform to others15- Repurposing articles, podcasts, demos, or docs into social content16- Scripting short-form video or YouTube versions of existing content17- User says "crosspost", "post everywhere", "share on all platforms", or "distribute this"1819## Core Rules20211. **Never draft identical content cross-platform.** Each platform gets a native adaptation.222. **Primary platform first.** Draft the main platform's version first, then adapt for others.233. **Respect platform conventions.** Length limits, formatting, link handling all differ.244. **One idea per post.** If the source content has multiple ideas, split across posts.255. **Attribution matters.** If crossposting someone else's content, credit the source.266. **Hooks matter more than summaries.** Use specifics over slogans; keep the ask small and clear.2728## Platform Specifications2930Text platforms:3132| Platform | Max Length | Link Handling | Hashtags | Media |33|----------|-----------|---------------|----------|-------|34| X | 280 chars (4000 for Premium) | Counted in length | Minimal (1-2 max) | Images, video, GIFs |35| LinkedIn | 3000 chars | Not counted in length | 3-5 relevant | Images, video, docs, carousels |36| Threads | 500 chars | Separate link attachment | None typical | Images, video |37| Bluesky | 300 chars | Via facets (rich text) | None (use feeds) | Images |3839Video and long-form targets (TikTok/short video, YouTube, newsletter) have no hard character limits — their adaptation notes are in Step 3.4041## Workflow4243### Step 1: Create Source Content4445Start with the core idea:46- Identify the single core message47- Determine the primary platform (where the audience is biggest)48- Draft the primary platform version first4950Before drafting, clarify if not obvious from context:51- Source asset: what are we adapting from (article, video, demo, memo, launch doc)52- Audience: builders, investors, customers, operators, or general audience53- Goal: awareness, conversion, recruiting, authority, launch support, or engagement5455### Step 2: Identify Target Platforms5657Ask the user or determine from context:58- Which platforms to target59- Priority order (primary gets the best version)60- Any platform-specific requirements (e.g., LinkedIn needs professional tone)6162### Step 3: Adapt Per Platform6364For each target platform, transform the content:6566**X adaptation:**67- Open with a hook, not a summary68- Cut to the core insight fast69- Keep links out of main body when possible70- Use thread format for longer content7172**LinkedIn adaptation:**73- Strong first line (visible before "see more")74- Short paragraphs with line breaks75- Frame around lessons, results, or professional takeaways76- More explicit context than X (LinkedIn audience needs framing)7778**Threads adaptation:**79- Conversational, casual tone80- Shorter than LinkedIn, less compressed than X81- Visual-first if possible8283**Bluesky adaptation:**84- Direct and concise (300 char limit)85- Community-oriented tone86- Use feeds/lists for topic targeting instead of hashtags8788**TikTok / short video adaptation:**89- First 3 seconds must interrupt attention90- Script around visuals, not just narration91- One demo, one claim, one CTA9293**YouTube adaptation:**94- Show the result early95- Structure by chapter96- Refresh the visual every 20-30 seconds9798**Newsletter adaptation:**99- Deliver one clear lens, not a bundle of unrelated items100- Make section titles skimmable101- Keep the opening paragraph doing real work102103### Step 4: Deliver Drafts and Posting Order104105Hand the user the full set of platform versions, plus a suggested rollout:106- Primary platform first, then secondary platforms107- Stagger timing (not all at once — 30-60 min gaps)108- Include cross-platform references where appropriate ("longer thread on X" etc.)109- Note any missing inputs needed before publishing (links, media, handles)110111This skill does not post. Publishing to each platform is the user's step.112113## Repurposing Cascade114115When adapting a larger source asset (article, podcast, demo, launch doc) into a multi-platform campaign, follow this cascade:1161171. **Anchor asset** — start from the article, video, demo, memo, or launch doc1182. **Extract 3-7 atomic ideas** — each stands alone as one post1193. **Write platform-native variants** — apply the Step 3 adaptations per idea1204. **Trim repetition across outputs** — no duplicated copy across platforms unless requested1215. **Align CTAs with platform intent** — the ask on LinkedIn differs from the ask on X or in a newsletter122123When asked for a full campaign, return: the core angle, platform-specific drafts, optional posting order, optional CTA variants, and any missing inputs needed before publishing.124125## Content Adaptation Examples126127### Source: Product Launch128129**X version:**130```131We just shipped [feature].132133[One specific thing it does that's impressive]134135[Link]136```137138**LinkedIn version:**139```140Excited to share: we just launched [feature] at [Company].141142Here's why it matters:143144[2-3 short paragraphs with context]145146[Takeaway for the audience]147148[Link]149```150151**Threads version:**152```153just shipped something cool — [feature]154155[casual explanation of what it does]156157link in bio158```159160### Source: Technical Insight161162**X version:**163```164TIL: [specific technical insight]165166[Why it matters in one sentence]167```168169**LinkedIn version:**170```171A pattern I've been using that's made a real difference:172173[Technical insight with professional framing]174175[How it applies to teams/orgs]176177#relevantHashtag178```179180## Quality Gate181182Before delivering drafts:183- [ ] Each platform version reads naturally for that platform184- [ ] No identical content across platforms185- [ ] Length limits respected186- [ ] Hooks are strong and specific — no generic hype language187- [ ] Links work and are placed appropriately188- [ ] Tone matches platform conventions189- [ ] CTA matches the content and audience190- [ ] Media is sized correctly for each platform