crosspost
affaan-m/everything-claude-code
Adapt and distribute content across X, LinkedIn, Threads, and Bluesky without repeating identical posts.
What is crosspost?
Crosspost helps you publish the same core idea across multiple social platforms while respecting each platform's constraints and audience expectations. Use it when you need to launch, announce, or share content that should reach people on different networks but in platform-appropriate ways.
- Adapts content for X, LinkedIn, Threads, and Bluesky with platform-specific constraints
- Preserves author voice across all versions while respecting platform differences
- Eliminates generic filler patterns like 'Excited to share' and forced CTAs
- Captures and reuses voice fingerprints for consistency across variants
- Suggests posting order and timing for multi-platform distribution
How to install crosspost
npx skills add https://github.com/affaan-m/everything-claude-code --skill crosspost- Access to X, LinkedIn, Threads, and/or Bluesky accounts
- Source content (article, post, memo, or thread to adapt)
- Optional: brand-voice skill output if you want consistent voice capture
How to use crosspost
- 1.Provide the primary source content (strongest native version first)
- 2.Run brand-voice skill if you need to capture voice fingerprint for consistency
- 3.Specify which platforms you want to post to
- 4.Review the adapted versions for each platform
- 5.Check the quality gate: each version should read like the same author under different constraints
- 6.Publish in the suggested order or adjust timing as needed
Use cases
- Publishing a product launch across all four platforms with tailored messaging
- Sharing a long-form essay as compressed X posts, LinkedIn context, and Threads versions
- Distributing a changelog or update with platform-specific angles
- Crossposting a memo or announcement while maintaining authentic voice on each network
- Adapting a thread into standalone posts optimized for each platform's format
- Founders and product teams launching updates or releases
- Content creators and writers distributing essays and ideas
- Marketing teams managing multi-platform campaigns
- Anyone sharing the same message across X, LinkedIn, Threads, and Bluesky
crosspost FAQ
No. Crosspost adapts content for each platform's constraints and audience. Identical copy across platforms violates the core rule and wastes the reach of each network.
Start with that as your primary version. Crosspost will adapt it for the others while preserving what made it work on the first platform.
Only if the source earned it. The skill blocks invented CTAs, questions, and moral conclusions that weren't in the original content.
Run brand-voice first to capture a voice profile, then reuse it across all platform variants. This ensures the same author comes through on X, LinkedIn, Threads, and Bluesky.
Only if useful. Most posts should stand alone on their platform without referencing where else they appear.
Full instructions (SKILL.md)
Source of truth, from affaan-m/everything-claude-code.
name: crosspost description: Multi-platform content distribution across X, LinkedIn, Threads, and Bluesky. Adapts content per platform using content-engine patterns. Never posts identical content cross-platform. Use when the user wants to distribute content across social platforms. metadata: origin: ECC
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
- Do not publish identical copy across platforms.
- Preserve the author's voice across platforms.
- Adapt for constraints, not stereotypes.
- One post should still be about one thing.
- 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:
- post the strongest native version first
- adapt for the secondary platforms
- 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
Related skills
More from affaan-m/everything-claude-code and the wider catalog.
security-review
Security checklist and patterns for authentication, input validation, secrets, and sensitive features.
golang-patterns
Idiomatic Go patterns, best practices, and conventions for building robust, efficient, and maintainable applications.
coding-standards
Baseline coding conventions for naming, readability, immutability, and quality across projects.
frontend-patterns
React and Next.js patterns for components, state management, performance, and modern frontend practices.
backend-patterns
REST/GraphQL API design, database optimization, and server-side patterns for Node.js, Express, and Next.js.
golang-testing
Go testing patterns: table-driven tests, subtests, benchmarks, fuzzing, and TDD methodology.