linkedin-post-formatter

tarafından github

Unicode kalın/italik stilleri, görsel ayırıcılar, yapılandırılmış bölümler ve etkileşim odaklı desenler kullanarak etkileyici LinkedIn gönderileri biçimlendirin ve taslak haline getirin. KULLAN…

npx skills add https://github.com/github/awesome-copilot --skill linkedin-post-formatter

LinkedIn Post Formatter

Transform raw content, ideas, or technical material into polished, engagement-optimized LinkedIn posts using Unicode typography and proven structural patterns.

Overview

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.

Unicode Typography Reference

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:

Bold (Mathematical Sans-Serif Bold)

Use bold for key phrases, section headers, and emphasis words.

PlainUnicode Bold
A-Z𝗔-𝗭
a-z𝗮-𝘇
0-9𝟬-𝟵

Italic (Mathematical Sans-Serif Italic)

Use italic for subtle emphasis, technical terms, or quotes.

PlainUnicode Italic
A-Z𝘈-𝘡
a-z𝘢-𝘻

Bold-Italic (Mathematical Sans-Serif Bold Italic)

Use sparingly for maximum emphasis.

PlainUnicode Bold-Italic
A-Z𝘼-𝙕
a-z𝙖-𝙯

Visual Separators

Use these characters to create visual structure:

  • Section divider: ━━━━━━━━━━━━━━━━━━━━━━ (box-drawing heavy horizontal)
  • Bullet points: (diamond with dot) or (bullseye)
  • Arrow flow: for vertical flow, for horizontal continuation
  • Sub-points: for indented sub-items
  • Numbered items: Use bold Unicode digits 𝟭. 𝟮. 𝟯. etc.

Post Structure Patterns

Pattern 1: Hook → Content → CTA (General Purpose)

[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

Pattern 2: Listicle (Numbered Insights)

[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

Pattern 3: Story → Lesson (Thought Leadership)

[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

Pattern 4: Resource Share (Cheatsheet/Guide/Tool)

[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.

#Hashtags

Formatting Rules

  1. Line breaks matter: LinkedIn collapses multiple blank lines. Use single blank lines between paragraphs.
  2. Hook above the fold: The first 2-3 lines must compel the reader to click "see more." Front-load value.
  3. Short paragraphs: 1-3 sentences max per paragraph. Wall of text kills engagement.
  4. Bold sparingly: Bold key phrases and headers, not entire paragraphs.
  5. Italic for nuance: Use italic for technical terms, internal thoughts, or subtle emphasis.
  6. Hashtags at the end: 5-8 relevant hashtags on the last line. No mid-post hashtags.
  7. No emojis in body unless the user explicitly requests them. Exception: one strategic emoji in CTA (♻️ for repost).
  8. Character limit: LinkedIn posts can be up to 3000 characters. Aim for 1500-2500 for optimal engagement.
  9. No URLs in body: LinkedIn suppresses reach for posts with links. Add links in comments instead. Mention "link in comments" or "grab it below" as CTA.

Engagement Optimization

  • Opening hooks that work: Questions, bold claims, "If you do X...", contrarian takes, surprising stats.
  • Closing CTAs that work: "♻️ 𝗥𝗲𝗽𝗼𝘀𝘁 if...", "Save this for later", "Tag someone who needs this", "What's your take? 👇"
  • Whitespace is your friend: Dense text gets scrolled past. Airy, scannable layout wins.
  • The "see more" hook: LinkedIn truncates posts after ~210 characters on desktop. Make sure the first 2 lines create enough curiosity to click.

Process

  1. Analyze the source content (text, HTML, image, or idea).
  2. Identify the best post structure pattern (Hook→Content→CTA, Listicle, Story→Lesson, Resource Share).
  3. Extract the core message and 3-5 key points.
  4. Apply Unicode bold/italic formatting to headers and emphasis words using references/unicode-charmap.md.
  5. Add visual separators between sections.
  6. Write a compelling hook for the opening.
  7. Add a CTA and hashtags at the end.
  8. Verify the post is copy-paste ready for LinkedIn.

github tarafından daha fazla skill

console-rendering
github
Go'da struct etiketi tabanlı konsol renderlama sistemini kullanma talimatları
official
acquire-codebase-knowledge
github
Bu beceriyi, kullanıcı açıkça mevcut bir kod tabanını haritalamayı, belgelemeyi veya bu kod tabanına dahil olmayı istediğinde kullanın. "Bu kod tabanını haritala", "belgele…" gibi ifadeler için tetikleyin.
official
acreadiness-assess
github
Run the AgentRC readiness assessment on the current repository and produce a static HTML dashboard at reports/index.html. Wraps `npx github:microsoft/agentrc…
official
acreadiness-generate-instructions
github
AgentRC talimatları komutu aracılığıyla özelleştirilmiş AI ajan talimat dosyaları oluşturur. .github/copilot-instructions.md dosyasını üretir (varsayılan, VS'de Copilot için önerilir…
official
acreadiness-policy
github
Kullanıcının bir AgentRC politikası seçmesine, yazmasına veya uygulamasına yardımcı olun. Politikalar, ilgisiz kontrolleri devre dışı bırakarak, etki/seviyeyi geçersiz kılarak, ayarlayarak…
official
add-educational-comments
github
We need to translate the given English text into Turkish, preserving the name "add-educational-comments" if it appears. The text is a description of an agent skill. We must not add any extra commentary, labels, or formatting. The translation should be accurate and natural in Turkish. The text: "Add educational comments to code files to transform them into effective learning resources. Adapts explanation depth and tone to three configurable knowledge levels: beginner, intermediate, and advanced Automatically requests a file if none is provided, with numbered list matching for quick selection Expands files by up to 125% using educational comments only (hard limit: 400 new lines; 300 for files over 1,000 lines) Preserves file encoding, indentation style, syntax correctness, and..." It seems cut off at the end. The original might have more, but we only have this. We'll translate what's given. Note: The name "add-educational-comments" does not appear in the text, so we don't include it. Translation: "Kod dosyalarına
official
adobe-illustrator-scripting
github
ExtendScript (JavaScript/JSX) kullanarak Adobe Illustrator otomasyon betiklerini yazın, hata ayıklayın ve optimize edin. Oluştururken veya değiştirirken kullanın…
official
agent-governance
github
Yapay zeka aracı erişimi ve davranışını kontrol etmek için bildirimsel politikalar, niyet sınıflandırması ve denetim izleri. Birleştirilebilir yönetişim politikaları, izin verilen/engellenen araçları, içerik filtrelerini, hız sınırlarını ve onay gereksinimlerini tanımlar — kod değil yapılandırma olarak saklanır. Anlamsal niyet sınıflandırması, araç yürütülmeden önce desen tabanlı sinyaller kullanarak tehlikeli istemleri (veri sızdırma, ayrıcalık yükseltme, istem enjeksiyonu) tespit eder. Araç düzeyinde yönetişim dekoratörü, politikaları işlevde u
official