
Crosspost
- 5.2k installs
- 238k repo stars
- Updated August 5, 2026
- affaan-m/everything-claude-code
crosspost is an agent skill for platform-native multi-channel social distribution across X, LinkedIn, Threads, and Bluesky.
About
The crosspost skill distributes one underlying idea across X, LinkedIn, Threads, and Bluesky while preserving the author's voice and platform constraints. Core rules forbid publishing identical copy, inventing CTAs or closing questions the source did not earn, and padding LinkedIn posts with fake founder-reflection tone. Workflow starts from the strongest source version, optionally runs brand-voice for a reusable VOICE PROFILE and content-engine for voice shaping, then adapts per platform: compressed claims on X, necessary context on LinkedIn without forced professionalism, direct readable Threads copy, and concise Bluesky posts without hashtag gaming. Default posting order publishes the strongest native version first, then secondary platforms, staggering timing only when requested. Banned patterns include Excited to share, Here's what I learned, What do you think, and link in bio unless literally true. Output returns primary version, adapted variants, change notes, and unresolved publishing constraints.
- Never publish identical copy across platforms; adapt for constraints not stereotypes.
- Start from strongest source and reuse brand-voice VOICE PROFILE when available.
- X stays compressed; LinkedIn adds context without fake professional tone or forced questions.
- Threads and Bluesky get distinct voice-preserving versions, not shortened LinkedIn paste.
- Banned filler includes Excited to share, What do you think, and unearned link in bio CTAs.
Crosspost by the numbers
- 5,185 all-time installs (skills.sh)
- +221 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #135 of 1,879 Marketing & SEO skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
crosspost capabilities & compatibility
- Capabilities
- platform constraint adaptation · voice fingerprint reuse via brand voice · banned pattern quality gate · posting order guidance · change notes per platform variant
- Works with
- Use cases
- marketing · copywriting · seo
What crosspost says it does
Do not publish identical copy across platforms.
npx skills add https://github.com/affaan-m/everything-claude-code --skill crosspostAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 5.2k |
|---|---|
| repo stars | ★ 238k |
| Security audit | 3 / 3 scanners passed |
| Last updated | August 5, 2026 |
| Repository | affaan-m/everything-claude-code ↗ |
How do I publish the same idea across social platforms without duplicate copy or off-brand padding?
Adapt one source post into platform-native versions for X, LinkedIn, Threads, and Bluesky without duplicating copy verbatim.
Who is it for?
Teams distributing launches, essays, or updates across multiple social channels with one source draft.
Skip if: Skip when only X posting is needed; use x-api or content-engine instead.
When should I use this skill?
User says crosspost, post this everywhere, or wants platform-specific social adaptations.
What you get
Platform-native post variants with voice preserved and banned filler removed.
- X post draft
- LinkedIn post draft
- Threads post draft
By the numbers
- Covers four platforms: X LinkedIn Threads Bluesky
- Default posting order: strongest native version first
Files
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
- 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-voicefor reusable source-derived voice capturecontent-enginefor voice capture and source shapingx-apifor X publishing workflows
interface:
display_name: "Crosspost"
short_description: "Multi-platform social distribution"
brand_color: "#EC4899"
default_prompt: "Use $crosspost to adapt content for multiple social platforms."
policy:
allow_implicit_invocation: true
Related skills
Forks & variants (1)
Crosspost has 1 known copy in the catalog totaling 1.4k installs. They canonicalize to this original listing.
- affaan-m - 1.4k installs
How it compares
Pick crosspost when one announcement must become four distinct social drafts rather than a single post pasted everywhere.
FAQ
Who is crosspost for?
Developers and marketers adapting one source post into native versions for X, LinkedIn, Threads, and Bluesky.
When should I use crosspost?
When a launch, essay, or update needs distinct platform versions without verbatim duplication.
Is crosspost safe to install?
Review the Security Audits panel; it shapes copy only and does not post without separate API skills.