AGENT SKILL

linkedin-post-formatter

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.

License 许可
MIT
最近更新
2026-11-15
Stars
★ 4.1w
Forks
5.4k

01 前言 Front Matter

name
linkedin-post-formatter
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.

02 资源文件 2

03 SKILL.md 正文

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.

Plain Unicode Bold
A-Z ?-?
a-z ?-?
0-9 ?-?

Italic (Mathematical Sans-Serif Italic)

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

Plain Unicode Italic
A-Z ?-?
a-z ?-?

Bold-Italic (Mathematical Sans-Serif Bold Italic)

Use sparingly for maximum emphasis.

Plain Unicode 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.

04 同仓库更多 Skills

github
github/awesome-copilot

supabase-rls-policies

Write, review, and test Supabase Row Level Security (RLS) policies so that one user cannot read or change another user's rows. Use when creating or changing tables, policies, views, or security definer functions in a Supabase project, when reviewing a migration that touches RLS, or when asked to prove user isolation with pgTAP tests that sign in as two users.

测试与质量Skill与智能体开发
★ 4.1w
github
github/awesome-copilot

skill-distribution-audit

Audit a skill collection before release or investigate installer omissions, archived/template leakage, duplicate identities, and manifest drift. Reconcile the intended public source set, distribution manifest, and actual discovery output for a specified consumer version. Includes a deterministic set-comparison helper.

Skill与智能体开发
★ 4.1w
github
github/awesome-copilot

logicapps-custom-code-net10-migration

Migrate Azure Logic Apps Standard local-function custom-code projects from .NET 8 to .NET 10. Use for legacy Logic Apps custom-code workspace upgrades, project/package configuration, custom-worker settings, publication, and integrated VS Code debugging. Not for ordinary .NET applications, standalone Azure Functions, Consumption workflows, or cloud deployment.

开发工程师
★ 4.1w
github
github/awesome-copilot

winmd-api-search

Find and explore Windows desktop APIs. Use when building features that need platform capabilities — camera, file access, notifications, UI controls, AI/ML, sensors, networking, etc. Discovers the right API for a task and retrieves full type details (methods, properties, events, enumeration values).

开发工程师后端与接口
★ 4.1w
github
github/awesome-copilot

resemble-detect

Deepfake detection and media safety — detect AI-generated audio, images, video, and text, trace synthesis sources, apply watermarks, verify speaker identity, and analyze media intelligence using Resemble AI

后端与接口图像与多媒体
★ 4.1w
github
github/awesome-copilot

quality-playbook

Run a complete quality engineering audit on any codebase. Derives behavioral requirements from the code, generates spec-traced functional tests, runs a three-pass code review with regression tests, executes a multi-model spec audit (Council of Three), and produces a consolidated bug report with TDD-verified patches. Finds the 35% of real defects that structural code review alone cannot catch. Works with any language. Trigger on 'quality playbook', 'spec audit', 'Council of Three', 'fitness-to-purpose', or 'coverage theater'.

代码审查Skill与智能体开发
★ 4.1w