# Crosspost

> 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.

- Skill: `davie521/crosspost` (Agent Skill)
- Install (CLI): `npx skillmds@latest add davie521/crosspost`
- Raw SKILL.md: https://api.skillmd.com/api/skills/davie521/crosspost/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Davie521 (https://skillmd.com/u/davie521)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/davie521/crosspost

---


# 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

1. **Never draft identical content cross-platform.** Each platform gets a native adaptation.
2. **Primary platform first.** Draft the main platform's version first, 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.
6. **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:

1. **Anchor asset** — start from the article, video, demo, memo, or launch doc
2. **Extract 3-7 atomic ideas** — each stands alone as one post
3. **Write platform-native variants** — apply the Step 3 adaptations per idea
4. **Trim repetition across outputs** — no duplicated copy across platforms unless requested
5. **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:
- [ ] Each platform version reads naturally for that platform
- [ ] No identical content across platforms
- [ ] Length limits respected
- [ ] Hooks are strong and specific — no generic hype language
- [ ] Links work and are placed appropriately
- [ ] Tone matches platform conventions
- [ ] CTA matches the content and audience
- [ ] Media is sized correctly for each platform