Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Format and draft compelling LinkedIn posts using Unicode bold/italic styling, visual separators, structured sections, and engagement-optimized patterns. USE FOR: draft LinkedIn post, format text for LinkedIn, create social media post, write thought leadership post, convert content to LinkedIn format, LinkedIn carousel text, Unicode bold italic formatting.
.claude/skills/linkedin-post-formatter/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-05 | ✗→✓ | ▲ Improved | — | — |
| case-10 | ✗→✓ | ▲ Improved | — | — |
| case-12 | ✗→✓ | ▲ Improved | — | — |
| case-15 | ✗→✓ | ▲ Improved | — | — |
| case-09 | ✗→✓ | ▲ Improved | — | — |
Transform raw content, ideas, or technical material into polished, engagement-optimized LinkedIn posts using Unicode typography and proven structural patterns.
LinkedIn only supports plain text — no Markdown rendering, no rich formatting. This skill uses Unicode Mathematical Alphanumeric Symbols to simulate bold, italic, and bold-italic text that renders natively in the LinkedIn editor without any external tools.
When converting plain text into Unicode-styled LinkedIn text, first load and use references/unicode-charmap.md as the authoritative character mapping reference.
Apply these character mappings to create visual emphasis in plain text:
Use bold for key phrases, section headers, and emphasis words.
| Plain | Unicode Bold | |-------|-------------| | A-Z | 𝗔-𝗭 | | a-z | 𝗮-𝘇 | | 0-9 | 𝟬-𝟵 |
Use italic for subtle emphasis, technical terms, or quotes.
| Plain | Unicode Italic | |-------|---------------| | A-Z | 𝘈-𝘡 | | a-z | 𝘢-𝘻 |
Use sparingly for maximum emphasis.
| Plain | Unicode Bold-Italic | |-------|-------------------| | A-Z | 𝘼-𝙕 | | a-z | 𝙖-𝙯 |
Use these characters to create visual structure:
━━━━━━━━━━━━━━━━━━━━━━ (box-drawing heavy horizontal)◈ (diamond with dot) or ◎ (bullseye)↓ for vertical flow, → for horizontal continuation↳ for indented sub-items𝟭. 𝟮. 𝟯. etc.[Bold hook line — provocative statement or question]
[1-2 lines of context setting the stage]
━━━━━━━━━━━━━━━━━━━━━━
[Main content with bold section headers]
[Bullet points using ◈ or numbered with bold digits]
━━━━━━━━━━━━━━━━━━━━━━
[Bold takeaway or summary]
[Call to action — repost, comment, or grab resource]
#Hashtags[Bold opening line with a strong claim]
[Setup line explaining what follows]
𝟭. [Bold item title]
[Supporting detail]
𝟮. [Bold item title]
[Supporting detail]
...
𝗧𝗵𝗲 𝗸𝗲𝘆 𝘁𝗮𝗸𝗲𝗮𝘄𝗮𝘆: [Summary in italic]
#Hashtags[Italic opening with a personal or observed moment]
[2-3 short paragraphs telling the story]
━━━━━━━━━━━━━━━━━━━━━━
𝗧𝗵𝗲 𝗹𝗲𝘀𝘀𝗼𝗻:
[Bold lesson or principle extracted from the story]
[CTA]
#Hashtags[Hook: "If you do X, you cannot miss this..."]
[Brief description of what the resource covers]
━━━━━━━━━━━━━━━━━━━━━━
[Bold section count]. [Bold section titles as numbered list]
━━━━━━━━━━━━━━━━━━━━━━
𝗧𝗵𝗲 𝗿𝗲𝗮𝗹 𝘁𝗮𝗸𝗲𝗮𝘄𝗮𝘆:
[Why this resource matters — bold key phrase]
[Grab it / Share it CTA]
♻️ 𝗥𝗲𝗽𝗼𝘀𝘁 if this is useful to your network.
#Hashtagsreferences/unicode-charmap.md.| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-05 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-10 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-12 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-15 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-09 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-21 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-13 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-11 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-01 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-19 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-23 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-22 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-18 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-20 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-02 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-06 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-03 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-07 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-17 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-14 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-16 | pass→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-04 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-08 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 23 cases were attempted. The headline lift of +74 percentage points is the difference between those two pass rates over the 23 comparable cases. 1 case got worse with the skill loaded, and it is included in that figure.
The per-case answers from this run were removed by the retention sweep, so the case table below shows the verdicts without the text either arm produced. The counts above were recorded at the time and are unaffected. Answers are now kept for 180 days.
Other measured skills in the registry, with their headline benchmark lift.