Skip to content
cccskills
FreePublished on GitHub

linkedin-post-formatter

Turn ideas, notes, or technical material into LinkedIn posts ready to copy and paste. Organize hooks, short sections, closing prompts, and hashtags, using Unicode characters to give plain text the appearance of bold or italic styling.

OriginalShow the original description

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.

Works withLinkedIn
See how to install

Good for

  • Turn technical material into a LinkedIn post
  • Format an existing draft for easy scanning
  • Share a lesson drawn from work experience
  • Draft a post introducing a guide or tool

Files included (2)

  • SKILL.md5.9 KB
  • references/unicode-charmap.md2.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Map an existing codebase into seven documents covering its technology, structure, architecture, conventions, integrations, tests, and concerns. Link findings to file evidence, mark unknowns, and highlight differences between stated plans and the actual implementation.

  • Get oriented in an unfamiliar codebase
  • Prepare documentation for a project handover
  • Compare documented architecture with implementation
github/awesome-copilot40.2KUpdated Oct 17, 2026

Assess a repository’s readiness for AI agents with AgentRC and generate a standalone HTML dashboard. Review scores across nine areas, see prioritized improvements, and optionally apply scoring policies tailored to an organization.

  • Assessing a repository’s readiness for AI agents
  • Prioritizing improvements from assessment results
  • Reviewing scores under an organization’s own policy
github/awesome-copilot40.2KUpdated Oct 17, 2026

Generate coding agent instruction files from a project's actual code using AgentRC. Capture detected languages, frameworks, and conventions in one shared file or split rules by topic and project area, with a preview before writing.

  • Create project instructions for VS Code Copilot
  • Refresh agent rules after project changes
  • Split monorepo instructions by project area
github/awesome-copilot40.2KUpdated Oct 17, 2026

Customize AgentRC readiness assessments to match team or organization standards. Choose or create policies that adjust check importance, disable irrelevant checks, set pass thresholds, and define requirements for automated checks in CI workflows.

  • Set shared readiness standards across an organization
  • Focus assessments on AI tooling
  • Adjust the importance of individual checks
github/awesome-copilot40.2KUpdated Oct 17, 2026

Analyze supplied ad performance data to identify wasted spend, strong campaigns, and next tests. Compare channels, assess whether test differences are meaningful, and produce budget reallocation recommendations with a prioritized action plan.

  • Identify ads and keywords to pause
  • Find campaigns and audiences worth scaling
  • Assess whether A/B test results are meaningful
github/awesome-copilot40.2KUpdated Oct 17, 2026

Turn code files into learning resources by adding comments that explain syntax, programming concepts, and design choices. Adjust explanation depth and repetition to the reader’s knowledge while preserving file structure, encoding, and syntax.

  • Add beginner-friendly explanations to existing code
  • Document the reasoning behind syntax and design choices
  • Adjust comment depth for readers with different experience
github/awesome-copilot40.2KUpdated Oct 17, 2026

See all skills by github

Report a problem with this skill