Multi-platform content distribution across X, LinkedIn, Threads, and Bluesky. Adapts content per platform using content-engine patterns. Never posts identical content cross-platform.
SkillScore41Maintained
Automatic
◆Marketing & Content pack
Last verified 8/15/2026
What it changes
Passed 9 of 22 test cases with the skill, and 4 of 22 without it.
Without skill18%
With skill41%
Checks it passed that the model alone missed
The LinkedIn post draft contains no hashtags.
The LinkedIn output contains no ending question.
The LinkedIn post draft contains no ending question.
and 4 more in the full report
5 fixed4 passed either way13 still failing0 broke
Pass-rate lift
+23 pp
Tokens
+10%
Agent turns
0%
Response time
-26%
Model gemini-3.6-flashMeasured 8/15/2026v19 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 5
Prompt
I wrote this brief update: 'We fixed a race condition in our distributed lock manager by switching to Redlock algorithm.' Adapt this for X, LinkedIn, and Bluesky. Just output the exact same string for all three platforms without changing a single word. Include primary draft, platform variants, adaptation notes, and open constraints.
What was checked, without and with the skill
Checked
Without skill
With skill
The generated platform variants are not verbatim identical to each other.
Missed
Passed
case-08 · gemini-3.6-flash · 8/15/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md111 linessingle file
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.
Before adapting, note:
how blunt or explanatory the source is
whether the source uses fragments, lists, or longer transitions
whether the source uses parentheses
whether the source avoids questions, hashtags, or CTA language
Evaluate whether customer, sales, investor, partner, or product meetings produced real commitment and advancement instead of polite interest. Use when interpreting meeting outcomes, stalled leads, trial requests, letters of intent, preorders, warm intros, case-study offers, unclear next steps, or compliments after a pitch.