Skill Introduction

Overview

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.

Core value

Turns reusable Other know-how into an installable skill, helping users complete github, community work faster.

Target users

Developers, testers, and maintainers who handle Other tasks in Focus Code.
Teams that already trust workflows or content from affaan-m.
Users who want standardized prompts, steps, or conventions instead of repeating setup work.

Best practices

Read the skill content first to confirm required inputs, expected outputs, and dependencies.
Try it on a small task before relying on it for critical work.
Add project-specific constraints such as coding style, target platform, test expectations, and delivery format.
For external sources, verify the source link, version, and recent maintenance activity.

Best use cases

Tasks related to github, community that need a reusable execution flow.
Converting a community repo, team convention, or personal workflow into day-to-day assistance.
Starting from a proven skill instead of writing prompts or procedures from scratch.

Limits and boundaries

Results depend on the quality of the original skill content and may need human correction.
It does not replace code review, tests, security review, or professional judgment.
External tools, APIs, account permissions, and local dependencies still need separate setup.

Differentiation

Structured around Other, making it easier to discover and reuse than loose prompt snippets.
Marked as GitHub, which helps users judge trust and maintenance expectations.
Keeps the original source link available for repository, documentation, or discussion follow-up.
Tagged with github, community, so it can be filtered by concrete task intent.

Install and use

Install

Copy Install Command

focus install crosspost-badda4

View source

Detail Preview

SKILL.md

Primary filemarkdown4 KB

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.

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

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:

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-voice for reusable source-derived voice capture
content-engine for voice capture and source shaping
x-api for X publishing workflows

crosspost