crosspost
by affaan-mcrosspost is a skill for turning one source idea into native social posts for X, LinkedIn, Threads, and Bluesky. It preserves the original meaning and voice, avoids identical copy, and adapts by platform constraints. Use this crosspost guide when you need controlled crosspost usage for Social Media.
This skill scores 78/100, which means it is a solid listing candidate for directory users who want guided cross-posting across X, LinkedIn, Threads, and Bluesky. The repository gives enough workflow structure and usage triggers to support an install decision, though users should note that the skill is text-only and lacks companion scripts or reference files.
- Clear activation cues for cross-platform publishing, including explicit phrases like "crosspost" and "post this everywhere".
- Operationally useful workflow rules: adapt per platform, preserve voice, and avoid identical copy.
- Good progressive structure with a primary-version step, voice-fingerprint step, and platform-specific constraints.
- No install command, scripts, or supporting references, so adoption depends on the SKILL.md text alone.
- Some platform guidance is only partially visible in the excerpt, so users may need to inspect the full file for implementation detail.
Overview of crosspost skill
crosspost is a skill for turning one source idea into platform-specific social posts without copying the same text into X, LinkedIn, Threads, and Bluesky. It is best for people who need a fast but controlled crosspost workflow: founders, marketers, creators, and agents handling launch notes, product updates, essays, or announcements for social media.
The real job here is not “post everywhere.” It is to preserve the original meaning and voice while adapting to each platform’s length, tone, and engagement norms. The crosspost skill is useful when a generic prompt would produce repetitive, brand-damaging near-duplicates.
What makes crosspost different
The skill’s main constraint is simple: never publish identical copy across platforms. It also pushes the model to keep one message focused, avoid fake CTAs, and adapt to platform constraints rather than stereotypes. That makes the crosspost skill a better fit when consistency matters more than volume.
Best fit for this workflow
Use crosspost when you already have a strong source post, article, memo, or launch update and want variants that feel native on each network. It is less useful if you want a full social strategy, audience research, or copywriting from scratch.
When to hesitate
If the source is vague, the voice is undefined, or the campaign needs heavy rewriting beyond social adaptation, you will get better results by shaping the source first and then using crosspost for distribution. For very opinionated brand campaigns, the skill also requires careful review so the platform versions do not drift in message.
How to Use crosspost skill
Install crosspost cleanly
Use the repository’s skill install flow for your environment, then point the agent at skills/crosspost/SKILL.md as the controlling instruction. If your setup supports skill management commands, install crosspost into the working session before asking for output; otherwise, include the skill file in context manually.
Start with the right source input
The crosspost skill works best when you provide one primary source version, not three competing drafts. Strong inputs look like this:
- the original post or thread
- the article, launch note, or changelog it should promote
- the intended platforms
- any must-keep phrase, claim, link, or CTA
- the brand voice if it already exists
If you only say “crosspost this,” the model has to guess too much about tone, angle, and emphasis.
Read these files first
For the crosspost guide, start with SKILL.md and pay special attention to:
When to ActivateCore RulesWorkflow- platform-specific adaptation notes
Those sections tell you how the skill wants source material selected and how far platform versions should diverge.
Prompt pattern that works
A good crosspost prompt is specific about source, destination, and constraints:
Use the crosspost skill to adapt this launch note for X, LinkedIn, Threads, and Bluesky. Keep the same core message, preserve our voice, do not invent a CTA, and make each version native to the platform.
If you have voice data, add it directly. If the source voice is weak, run brand-voice first so crosspost can reuse that profile instead of improvising a new style.
crosspost skill FAQ
Is crosspost better than a normal prompt?
Usually yes, if you care about platform fit and consistency. A normal prompt can produce usable drafts, but the crosspost skill adds guardrails: it avoids identical copy, preserves voice, and forces platform-aware adaptation for social media.
Do I need to be a beginner to use it?
No, but beginners should supply a clear source and a short constraint list. The more ambiguous the input, the more likely the output will feel generic. The skill is easier to use when the user already knows what the original message is and what cannot change.
When should I not use crosspost?
Do not use crosspost when you need a full content plan, a thread strategy from scratch, or a complete rewrite of weak source material. It is also a poor fit if each platform needs a radically different message rather than one shared idea adapted across channels.
How does it handle Social Media differences?
crosspost adjusts the same underlying message for X, LinkedIn, Threads, and Bluesky instead of forcing the same wording everywhere. That matters because each platform has different length pressure, pacing, and audience expectations.
How to Improve crosspost skill
Give the skill better source material
The biggest quality jump comes from starting with a strong primary version. If the source is polished, crosspost can focus on adaptation instead of rescue work. If the source is rough, ask it to first clarify the message before generating platform variants.
Provide hard constraints early
Tell the skill what must stay fixed: product name, launch date, link text, legal phrasing, or tone boundaries. Also say what may change, such as hooks, line breaks, emoji use, or CTA strength. That reduces guesswork and helps the crosspost skill keep the message intact.
Watch for common failure modes
The usual problems are over-explaining, uniform tone across platforms, and adding engagement bait that was not in the source. If the first pass feels too similar, ask for stronger differentiation by platform while keeping the same factual core.
Iterate by platform, not by vague “better”
When refining output, comment in terms of the network: “make LinkedIn more professional,” “compress X further,” or “make Threads more conversational.” This is more useful than asking for a general rewrite because it tells crosspost exactly which constraint to optimize for in the next pass.
