Crosspost
Turn one launch note, essay, or thread into platform-native posts for X, LinkedIn, Threads, and Bluesky without duplicate spam.
Overview
Crosspost is an agent skill most often used in Launch (also Grow distribution) that adapts one content artifact into platform-specific versions for X, LinkedIn, Threads, and Bluesky without duplicating identical copy.
Install
npx skills add https://github.com/affaan-m/everything-claude-code --skill crosspostWhat is this skill?
- Adapts one source idea across X, LinkedIn, Threads, and Bluesky
- Five core rules including no identical copy and no invented CTAs
- Workflow: primary version → voice fingerprint → per-platform reshape
- Integrates content-engine for shaping and brand-voice for fingerprint reuse
- One post stays about one thing across adaptations
- 4 platforms: X, LinkedIn, Threads, Bluesky
- 5 core crosspost rules in workflow
Adoption & trust: 4.1k installs on skills.sh; 210k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have a launch or essay ready but posting the same text everywhere tanks engagement and reads as inauthentic.
Who is it for?
Founders shipping product updates, essays, or threads who maintain presence on several social networks.
Skip if: Teams that need auto-scheduling, paid ad creative, or a single-network-only strategy with no adaptation.
When should I use this skill?
User wants to distribute the same underlying idea across multiple platforms; launch, update, release, or essay needs platform-specific versions; user says crosspost, post this everywhere, or adapt for X and LinkedIn.
What do I get? / Deliverables
You get channel-native post drafts that keep one core idea and your voice—after optional content-engine and brand-voice prep.
- Per-platform post drafts
- Voice-aligned adaptation notes
- Single-idea consistency check across channels
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Distribution is the canonical shelf because crossposting is invoked when something is ready to reach audiences on multiple social channels. Launch distribution is where adapted multi-platform copy ships; the skill’s core job is channel-specific publishing prep, not long-term analytics.
Where it fits
Ship a product launch note as distinct X, LinkedIn, and Threads drafts from one changelog.
Repurpose a long essay into short network-native posts without inventing a new CTA.
Adapt an existing X thread into a LinkedIn narrative that respects length and tone norms.
How it compares
Platform adaptation workflow—not a social scheduler MCP and not a generic SEO article rewriter.
Common Questions / FAQ
Who is crosspost for?
Solo and indie builders who publish launches and updates themselves and want credible multi-platform voice without a marketing agency.
When should I use crosspost?
At Launch when distributing a release; at Grow when repurposing content; whenever the user asks to crosspost or adapt copy for X and LinkedIn.
Is crosspost safe to install?
It is editorial guidance only; review the Security Audits panel on this page before installing skills from third-party repos.
Workflow Chain
Requires first: content engine, brand voice
SKILL.md
READMESKILL.md - Crosspost
# Crosspost Distribute content across platforms without turning it into the same fake post in four costumes. ## When to Activate - the user wants to publish the same underlying idea across multiple platforms - a launch, update, release, or essay needs platform-specific versions - the user says "crosspost", "post this everywhere", or "adapt this for X and LinkedIn" ## Core Rules 1. Do not publish identical copy across platforms. 2. Preserve the author's voice across platforms. 3. Adapt for constraints, not stereotypes. 4. One post should still be about one thing. 5. Do not invent a CTA, question, or moral if the source did not earn one. ## Workflow ### Step 1: Start with the Primary Version Pick the strongest source version first: - the original X post - the original article - the launch note - the thread - the memo or changelog Use `content-engine` first if the source still needs voice shaping. ### Step 2: Capture the Voice Fingerprint Run `brand-voice` first if the source voice is not already captured in the current session. Reuse the resulting `VOICE PROFILE` directly. Do not build a second ad hoc voice checklist here unless the user explicitly wants a fresh override for this campaign. ### Step 3: Adapt by Platform Constraint ### X - keep it compressed - lead with the sharpest claim or artifact - use a thread only when a single post would collapse the argument - avoid hashtags and generic filler ### LinkedIn - add only the context needed for people outside the niche - do not turn it into a fake founder-reflection post - do not add a closing question just because it is LinkedIn - do not force a polished "professional tone" if the author is naturally sharper ### Threads - keep it readable and direct - do not write fake hyper-casual creator copy - do not paste the LinkedIn version and shorten it ### Bluesky - keep it concise - preserve the author's cadence - do not rely on hashtags or feed-gaming language ## Posting Order Default: 1. post the strongest native version first 2. adapt for the secondary platforms 3. stagger timing only if the user wants sequencing help Do not add cross-platform references unless useful. Most of the time, the post should stand on its own. ## Banned Patterns Delete and rewrite any of these: - "Excited to share" - "Here's what I learned" - "What do you think?" - "link in bio" unless that is literally true - generic "professional takeaway" paragraphs that were not in the source ## Output Format Return: - the primary platform version - adapted variants for each requested platform - a short note on what changed and why - any publishing constraint the user still needs to resolve ## Quality Gate Before delivering: - each version reads like the same author under different constraints - no platform version feels padded or sanitized - no copy is duplicated verbatim across platforms - any extra context added for LinkedIn or newsletter use is actually necessary ## Related Skills - `brand-voice` for reusable source-derived voice capture - `content-engine` for voice capture and source shaping - `x-api` for X publishing workflows