agentleFS
elainesmithburkel-codeelainesmithburkel-code/everything-claude-code/.agents/skills/crosspost/SKILL.md

crosspost

Skill1 starsChanged 8 months agoMITView 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.

  • Reads credentials

35 other projects use a version of this, 6 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use agent-sort, everything-claude-code and 5 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • niloykumarbarmanSkill

    agent-sort

    Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.

    Also in 8 projects that use this

  • InfopibeSkill

    everything-claude-code

    Also in 8 projects that use this

  • ysyecustSkill

    brand-discovery

    Use when a brand needs to discover or articulate its identity through structured multi-session interviews. Covers purpose, positioning, audience, personality, voice, narrative, and founder-brand tension across 8 modules using laddering, 5 Whys, and projective techniques. Produces a resumable session with disk-persisted state and a master brandbook (90_SYNTHESIS.md).

    Also in 4 projects that use this

  • ysyecustSkill

    competitive-report-structure

    Use after benchmark-methodology has produced scored competitor profile cards. Assembles findings into a decision-grade report: landscape map, competitor profiles, benchmarking matrix, white-space analysis, strategic recommendations, and team alignment trigger questions. Final step in the three-skill competitive pipeline.

    Also in 4 projects that use this

  • niloykumarbarmanSkill

    product-capability

    Translate PRD intent, roadmap asks, or product discussions into an implementation-ready capability plan that exposes constraints, invariants, interfaces, and unresolved decisions before multi-service work starts. Use when the user needs an ECC-native PRD-to-SRS lane instead of vague planning prose.

    Also in 8 projects that use this

  • +1 more from ysyecust
  • +1 more from niloykumarbarman

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 8 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 28 edited versions we read keep these.

  • 8

    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:

    One idea per post: If the source content has multiple ideas, split across posts.

    line 23
  2. Distinctive:

    Attribution matters: If crossposting someone else's content, credit the source.

    line 24
  3. Very specific:

    Start with the core idea. Use content-engine skill for high-quality drafts:

    line 39
  4. Distinctive:

    Ask the user or determine from context:

    line 46
  5. Distinctive:

    Keep links out of main body when possible

    line 58
  6. Distinctive:

    Use thread format for longer content

    line 59
  7. Distinctive:

    Use feeds/lists for topic targeting instead of hashtags

    line 75
  8. Very specific:

    Use x-api skill for X

    line 80
  9. Distinctive:

    Use platform-specific APIs or tools for others

    line 81
  10. Distinctive:

    If using a crossposting service (e.g., Postbridge, Buffer, or a custom API), the pattern looks like:

    line 148

“Common” is measured: kept by at least 6 in 10 of the 28 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 multiple social platforms with platform-native adaptation.

When to Activate

  • User wants to post content to multiple platforms
  • Publishing announcements, launches, or updates across social media
  • Repurposing a post from one platform to others
  • User says "crosspost", "post everywhere", "share on all platforms", or "distribute this"

Core Rules

  1. Never post identical content cross-platform. Each platform gets a native adaptation.
  2. Primary platform first. Post to the main platform, then adapt for others.
  3. Respect platform conventions. Length limits, formatting, link handling all differ.
  4. One idea per post. If the source content has multiple ideas, split across posts.
  5. Attribution matters. If crossposting someone else's content, credit the source.

Platform Specifications

PlatformMax LengthLink HandlingHashtagsMedia
X280 chars (4000 for Premium)Counted in lengthMinimal (1-2 max)Images, video, GIFs
LinkedIn3000 charsNot counted in length3-5 relevantImages, video, docs, carousels
Threads500 charsSeparate link attachmentNone typicalImages, video
Bluesky300 charsVia facets (rich text)None (use feeds)Images

Workflow

Step 1: Create Source Content

Start with the core idea. Use content-engine skill for high-quality drafts:

  • Identify the single core message
  • Determine the primary platform (where the audience is biggest)
  • Draft the primary platform version first

Step 2: Identify Target Platforms

Ask the user or determine from context:

  • Which platforms to target
  • Priority order (primary gets the best version)
  • Any platform-specific requirements (e.g., LinkedIn needs professional tone)

Step 3: Adapt Per Platform

For each target platform, transform the content:

X adaptation:

  • Open with a hook, not a summary
  • Cut to the core insight fast
  • Keep links out of main body when possible
  • Use thread format for longer content

LinkedIn adaptation:

  • Strong first line (visible before "see more")
  • Short paragraphs with line breaks
  • Frame around lessons, results, or professional takeaways
  • More explicit context than X (LinkedIn audience needs framing)

Threads adaptation:

  • Conversational, casual tone
  • Shorter than LinkedIn, less compressed than X
  • Visual-first if possible

Bluesky adaptation:

  • Direct and concise (300 char limit)
  • Community-oriented tone
  • Use feeds/lists for topic targeting instead of hashtags

Step 4: Post Primary Platform

Post to the primary platform first:

  • Use x-api skill for X
  • Use platform-specific APIs or tools for others
  • Capture the post URL for cross-referencing

Step 5: Post to Secondary Platforms

Post adapted versions to remaining platforms:

  • Stagger timing (not all at once — 30-60 min gaps)
  • Include cross-platform references where appropriate ("longer thread on X" etc.)

Content Adaptation Examples

Source: Product Launch

X version:

We just shipped [feature].

[One specific thing it does that's impressive]

[Link]

LinkedIn version:

Excited to share: we just launched [feature] at [Company].

Here's why it matters:

[2-3 short paragraphs with context]

[Takeaway for the audience]

[Link]

Threads version:

just shipped something cool — [feature]

[casual explanation of what it does]

link in bio

Source: Technical Insight

X version:

TIL: [specific technical insight]

[Why it matters in one sentence]

LinkedIn version:

A pattern I've been using that's made a real difference:

[Technical insight with professional framing]

[How it applies to teams/orgs]

#relevantHashtag

API Integration

Batch Crossposting Service (Example Pattern)

If using a crossposting service (e.g., Postbridge, Buffer, or a custom API), the pattern looks like:

import os
import requests

resp = requests.post(
    "https://api.postbridge.io/v1/posts",
    headers={"Authorization": f"Bearer {os.environ['POSTBRIDGE_API_KEY']}"},
    json={
        "platforms": ["twitter", "linkedin", "threads"],
        "content": {
            "twitter": {"text": x_version},
            "linkedin": {"text": linkedin_version},
            "threads": {"text": threads_version}
        }
    }
)

Manual Posting

Without Postbridge, post to each platform using its native API:

  • X: Use x-api skill patterns
  • LinkedIn: LinkedIn API v2 with OAuth 2.0
  • Threads: Threads API (Meta)
  • Bluesky: AT Protocol API

Quality Gate

Before posting:

  • Each platform version reads naturally for that platform
  • No identical content across platforms
  • Length limits respected
  • Links work and are placed appropriately
  • Tone matches platform conventions
  • Media is sized correctly for each platform

Related Skills

  • content-engine — Generate platform-native content
  • x-api — X/Twitter API integration

Download now (ZIP)

Does it work?

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

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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.