agentleFS
Sign inStart free
FmarzochiFmarzochi/EGC/.agents/skills/crosspost/SKILL.md

crosspost

Skill61 starsChanged 46 days agoApache-2.0View on GitHub

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.

We split this skill into the rules it gives an agent

19 rules. 0 are common, 17 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 27 edited versions we read keep these.

  • 17

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not publish identical copy across platforms.

    line 18
  2. Distinctive:

    Do not invent a CTA, question, or moral if the source did not earn one.

    line 22
  3. Very specific:

    Use content-engine first if the source still needs voice shaping.

    line 35
  4. Very specific:

    Run brand-voice first if the source voice is not already captured in the current session.

    line 39
  5. Distinctive:

    Do not build a second ad hoc voice checklist here unless the user explicitly wants a fresh override for this campaign.

    line 42
  6. Distinctive:

    use a thread only when a single post would collapse the argument

    line 50
  7. Distinctive:

    avoid hashtags and generic filler

    line 51
  8. Distinctive:

    add only the context needed for people outside the niche

    line 55
  9. Distinctive:

    do not turn it into a fake founder-reflection post

    line 56
  10. Distinctive:

    do not add a closing question just because it is LinkedIn

    line 57
  11. Distinctive:

    do not force a polished "professional tone" if the author is naturally sharper

    line 58
  12. Distinctive:

    keep it readable and direct

    line 62
  13. Distinctive:

    do not write fake hyper-casual creator copy

    line 63
  14. Distinctive:

    do not paste the LinkedIn version and shorten it

    line 64
  15. Distinctive:

    do not rely on hashtags or feed-gaming language

    line 70
  16. Distinctive:

    Do not add cross-platform references unless useful.

    line 79
  17. Distinctive:

    Delete and rewrite any of these:

    line 83
  18. Distinctive:

    no platform version feels padded or sanitized

    line 102
  19. Distinctive:

    no copy is duplicated verbatim across platforms

    line 103

“Common” is measured: kept by at least 6 in 10 of the 27 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Download now (ZIP)

Trending

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Aug 30: 0 new projectsWeek of Sep 6: 0 new projectsWeek of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projects
Aug 2026Sep 2026Oct 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free