crosspost

Name: crosspost
Author: affaan-m

1.2kinstalls35kforks

How to install crosspost?

affaan-m/ecc/crosspost

$npx -y skills add affaan-m/ECC --skill crosspost

Installs into the current project.

Summary

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.

Files · 1

View on GitHub

SKILL.md

1	# Crosspost
2
3	Distribute content across platforms without turning it into the same fake post in four costumes.
4
5	## When to Activate
6
7	- the user wants to publish the same underlying idea across multiple platforms
8	- a launch, update, release, or essay needs platform-specific versions
9	- the user says "crosspost", "post this everywhere", or "adapt this for X and LinkedIn"
10
11	## Core Rules
12
13	1. Do not publish identical copy across platforms.
14	2. Preserve the author's voice across platforms.
15	3. Adapt for constraints, not stereotypes.
16	4. One post should still be about one thing.
17	5. Do not invent a CTA, question, or moral if the source did not earn one.
18
19	## Workflow
20
21	### Step 1: Start with the Primary Version
22
23	Pick the strongest source version first:
24	- the original X post
25	- the original article
26	- the launch note
27	- the thread
28	- the memo or changelog
29
30	Use `content-engine` first if the source still needs voice shaping.
31
32	### Step 2: Capture the Voice Fingerprint
33
34	Run `brand-voice` first if the source voice is not already captured in the current session.
35
36	Reuse the resulting `VOICE PROFILE` directly.
37	Do not build a second ad hoc voice checklist here unless the user explicitly wants a fresh override for this campaign.
38
39	### Step 3: Adapt by Platform Constraint
40
41	### X
42
43	- keep it compressed
44	- lead with the sharpest claim or artifact
45	- use a thread only when a single post would collapse the argument
46	- avoid hashtags and generic filler
47
48	### LinkedIn
49
50	- add only the context needed for people outside the niche
51	- do not turn it into a fake founder-reflection post
52	- do not add a closing question just because it is LinkedIn
53	- do not force a polished "professional tone" if the author is naturally sharper
54
55	### Threads
56
57	- keep it readable and direct
58	- do not write fake hyper-casual creator copy
59	- do not paste the LinkedIn version and shorten it
60
61	### Bluesky
62
63	- keep it concise
64	- preserve the author's cadence
65	- do not rely on hashtags or feed-gaming language
66
67	## Posting Order
68
69	Default:
70	1. post the strongest native version first
71	2. adapt for the secondary platforms
72	3. stagger timing only if the user wants sequencing help
73
74	Do not add cross-platform references unless useful. Most of the time, the post should stand on its own.
75
76	## Banned Patterns
77
78	Delete and rewrite any of these:
79	- "Excited to share"
80	- "Here's what I learned"
81	- "What do you think?"
82	- "link in bio" unless that is literally true
83	- generic "professional takeaway" paragraphs that were not in the source
84
85	## Output Format
86
87	Return:
88	- the primary platform version
89	- adapted variants for each requested platform
90	- a short note on what changed and why
91	- any publishing constraint the user still needs to resolve
92
93	## Quality Gate
94
95	Before delivering:
96	- each version reads like the same author under different constraints
97	- no platform version feels padded or sanitized
98	- no copy is duplicated verbatim across platforms
99	- any extra context added for LinkedIn or newsletter use is actually necessary
100
101	## Related Skills
102
103	- `brand-voice` for reusable source-derived voice capture
104	- `content-engine` for voice capture and source shaping
105	- `x-api` for X publishing workflows

People who liked this also viewed

6 picks

Type

crosspost

1.2kinstalls35kforks

View on GitHub

How to install crosspost?

affaan-m/ecc/crosspost

$npx -y skills add affaan-m/ECC --skill crosspost

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Crosspost
2
3	Distribute content across platforms without turning it into the same fake post in four costumes.
4
5	## When to Activate
6
7	- the user wants to publish the same underlying idea across multiple platforms
8	- a launch, update, release, or essay needs platform-specific versions
9	- the user says "crosspost", "post this everywhere", or "adapt this for X and LinkedIn"
10
11	## Core Rules
12
13	1. Do not publish identical copy across platforms.
14	2. Preserve the author's voice across platforms.
15	3. Adapt for constraints, not stereotypes.
16	4. One post should still be about one thing.
17	5. Do not invent a CTA, question, or moral if the source did not earn one.
18
19	## Workflow
20
21	### Step 1: Start with the Primary Version
22
23	Pick the strongest source version first:
24	- the original X post
25	- the original article
26	- the launch note
27	- the thread
28	- the memo or changelog
29
30	Use `content-engine` first if the source still needs voice shaping.
31
32	### Step 2: Capture the Voice Fingerprint
33
34	Run `brand-voice` first if the source voice is not already captured in the current session.
35
36	Reuse the resulting `VOICE PROFILE` directly.
37	Do not build a second ad hoc voice checklist here unless the user explicitly wants a fresh override for this campaign.
38
39	### Step 3: Adapt by Platform Constraint
40
41	### X
42
43	- keep it compressed
44	- lead with the sharpest claim or artifact
45	- use a thread only when a single post would collapse the argument
46	- avoid hashtags and generic filler
47
48	### LinkedIn
49
50	- add only the context needed for people outside the niche
51	- do not turn it into a fake founder-reflection post
52	- do not add a closing question just because it is LinkedIn
53	- do not force a polished "professional tone" if the author is naturally sharper
54
55	### Threads
56
57	- keep it readable and direct
58	- do not write fake hyper-casual creator copy
59	- do not paste the LinkedIn version and shorten it
60
61	### Bluesky
62
63	- keep it concise
64	- preserve the author's cadence
65	- do not rely on hashtags or feed-gaming language
66
67	## Posting Order
68
69	Default:
70	1. post the strongest native version first
71	2. adapt for the secondary platforms
72	3. stagger timing only if the user wants sequencing help
73
74	Do not add cross-platform references unless useful. Most of the time, the post should stand on its own.
75
76	## Banned Patterns
77
78	Delete and rewrite any of these:
79	- "Excited to share"
80	- "Here's what I learned"
81	- "What do you think?"
82	- "link in bio" unless that is literally true
83	- generic "professional takeaway" paragraphs that were not in the source
84
85	## Output Format
86
87	Return:
88	- the primary platform version
89	- adapted variants for each requested platform
90	- a short note on what changed and why
91	- any publishing constraint the user still needs to resolve
92
93	## Quality Gate
94
95	Before delivering:
96	- each version reads like the same author under different constraints
97	- no platform version feels padded or sanitized
98	- no copy is duplicated verbatim across platforms
99	- any extra context added for LinkedIn or newsletter use is actually necessary
100
101	## Related Skills
102
103	- `brand-voice` for reusable source-derived voice capture
104	- `content-engine` for voice capture and source shaping
105	- `x-api` for X publishing workflows

People who liked this also viewed

6 picks

Type