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
- Rojios/everything-claude-codetheir own version, first seen Nov 8, 2026
- pankaj-mahaur/Agent-Daemontheir own version, first seen Nov 6, 2026
- renepf/claude-skillstheir own version, first seen Oct 25, 2026
- davidanthonyn/claude-skillstheir own version, first seen Oct 20, 2026
- Perufitlife/postwire-skillstheir own version, first seen Oct 15, 2026
- gongyijie85/dsh-ecctheir own version, first seen Oct 13, 2026
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.
niloykumarbarmanSkillagent-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
InfopibeSkilleverything-claude-code
Also in 8 projects that use this
ysyecustSkillbrand-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
ysyecustSkillcompetitive-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
niloykumarbarmanSkillproduct-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
Other versions35 projects use a version of this.
Word for word · 6
- tpavanipradeep/everything-claude-code★ 104100% same
- yapota2018/affaan-m-everything-claude-code★ 4100% same
- CodeWithBehnam/cc-docs★ 2100% same
- divenhuang88/everything-claude-code★ 1100% same
- junimnjw/everything-claude-code★ 1100% same
- mryeastcode/ClaudeCode★ 0100% same
Edited · 6
- loulanyue/awesome-claude-notes★ 27297% same
- GPTtang/skill-atlas★ 496% same
- get-proofpilot/claude-skills-catalog★ 197% same
- rhfl04-dfdf/jychoi_everything-claude-code-ko★ 118% same
- MohamedEssam0-0/claude-skills★ 097% same
- PeterYang888/claude-skills★ 097% same
Wrote their own version · 23
- affaan-m/ECC★ 246ksame name
- mturac/everything-openai-codex★ 89same name
- mit-network/everything-claude-code★ 76same name
- Fmarzochi/EGC★ 61same name
- ysyecust/everything-claude-code★ 44same name
- gongyijie85/dsh-ecc★ 8same name
- ArogyaReddy/https-github.com-affaan-m-everything-claude-code1★ 2same name
- ronmkr/PromptBook★ 2same name
- niloykumarbarman/EVERYTHING-CLAUDE-CODE★ 1same name
- pcoulbourne/everything-claude-code★ 1same name
13 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository82 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .codex/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- examples/CLAUDE.mdCLAUDE.md
- .cursor/rules/common-agents.mdCursor rule
- .cursor/rules/common-coding-style.mdCursor rule
- .cursor/rules/common-development-workflow.mdCursor rule
- .cursor/rules/common-git-workflow.mdCursor rule
- .cursor/rules/common-hooks.mdCursor rule
- .cursor/rules/common-patterns.mdCursor rule
- .cursor/rules/common-performance.mdCursor rule
- .cursor/rules/common-security.mdCursor rule
- .cursor/rules/common-testing.mdCursor rule
- .cursor/rules/golang-coding-style.mdCursor rule
- .cursor/rules/golang-hooks.mdCursor rule
- .cursor/rules/golang-patterns.mdCursor rule
- .cursor/rules/golang-security.mdCursor rule
- .cursor/rules/golang-testing.mdCursor rule
- .cursor/rules/kotlin-coding-style.mdCursor rule
- .cursor/rules/kotlin-hooks.mdCursor rule
- .cursor/rules/kotlin-patterns.mdCursor rule
- .cursor/rules/kotlin-security.mdCursor rule
- .cursor/rules/kotlin-testing.mdCursor rule
- .cursor/rules/php-coding-style.mdCursor rule
- .cursor/rules/php-hooks.mdCursor rule
- .cursor/rules/php-patterns.mdCursor rule
- .cursor/rules/php-security.mdCursor rule
- .cursor/rules/php-testing.mdCursor rule
- .cursor/rules/python-coding-style.mdCursor rule
- .cursor/rules/python-hooks.mdCursor rule
- .cursor/rules/python-patterns.mdCursor rule
- .cursor/rules/python-security.mdCursor rule
- .cursor/rules/python-testing.mdCursor rule
- .cursor/rules/swift-coding-style.mdCursor rule
- .cursor/rules/swift-hooks.mdCursor rule
- .cursor/rules/swift-patterns.mdCursor rule
- .cursor/rules/swift-security.mdCursor rule
- .cursor/rules/swift-testing.mdCursor rule
- .cursor/rules/typescript-coding-style.mdCursor rule
- .cursor/rules/typescript-hooks.mdCursor rule
- .cursor/rules/typescript-patterns.mdCursor rule
- .cursor/rules/typescript-security.mdCursor rule
- .cursor/rules/typescript-testing.mdCursor rule
- api-designSkill
- article-writingSkill
- backend-patternsSkill
- bun-runtimeSkill
- claude-apiSkill
- coding-standardsSkill
- content-engineSkill
- deep-researchSkill
- dmux-workflowsSkill
- documentation-lookupSkill
- e2e-testingSkill
- eval-harnessSkill
- everything-claude-code-conventionsSkill
- exa-searchSkill
- fal-ai-mediaSkill
- frontend-patternsSkill
- frontend-slidesSkill
- The first 60 shown.
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
- Distinctive: line 23
One idea per post: If the source content has multiple ideas, split across posts.
- Distinctive: line 24
Attribution matters: If crossposting someone else's content, credit the source.
- Very specific: line 39
Start with the core idea. Use content-engine skill for high-quality drafts:
- Distinctive: line 46
Ask the user or determine from context:
- Distinctive: line 58
Keep links out of main body when possible
- Distinctive: line 59
Use thread format for longer content
- Distinctive: line 75
Use feeds/lists for topic targeting instead of hashtags
- Very specific: line 80
Use x-api skill for X
- Distinctive: line 81
Use platform-specific APIs or tools for others
- Distinctive: line 148
If using a crossposting service (e.g., Postbridge, Buffer, or a custom API), the pattern looks like:
“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.
Files
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
- Never post identical content cross-platform. Each platform gets a native adaptation.
- Primary platform first. Post to the main platform, then adapt for others.
- Respect platform conventions. Length limits, formatting, link handling all differ.
- One idea per post. If the source content has multiple ideas, split across posts.
- Attribution matters. If crossposting someone else's content, credit the source.
Platform Specifications
| Platform | Max Length | Link Handling | Hashtags | Media |
| X | 280 chars (4000 for Premium) | Counted in length | Minimal (1-2 max) | Images, video, GIFs |
| 3000 chars | Not counted in length | 3-5 relevant | Images, video, docs, carousels | |
| Threads | 500 chars | Separate link attachment | None typical | Images, video |
| Bluesky | 300 chars | Via 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-apiskill 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 bioSource: 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]
#relevantHashtagAPI 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-apiskill 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 contentx-api— X/Twitter API integration
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
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.

