본문으로 건너뛰기
cccskills
무료GitHub에 공개

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

연동 도구LinkedIn
설치 방법 보기

포함된 파일(2)

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

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.

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.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Primary accessibility skill for VS Code. REQUIRED for new feature and contribution work, and also applies to updates of existing UI. Covers accessibility help dialogs, accessible views, verbosity settings, signals, ARIA announcements, keyboard navigation, and ARIA labels/roles.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

jcasnellie69/homelab-config22026년 10월 16일 업데이트

Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

jcasnellie69/homelab-config22026년 10월 16일 업데이트

Act on user feedback attached to the current session. Use when the user submits feedback on the session's changes via the Submit Feedback button.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

jcasnellie69/homelab-config22026년 10월 16일 업데이트

Add educational comments to the file specified, or prompt asking for file to comment if one is not provided.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

jcasnellie69/homelab-config22026년 10월 16일 업데이트

Use when adding, modifying, or reviewing VS Code configuration policies. Covers the full policy lifecycle from registration to export to platform-specific artifacts. Run on ANY change that adds a `policy:` field to a configuration property.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

jcasnellie69/homelab-config22026년 10월 16일 업데이트

Patterns and techniques for adding governance, safety, and trust controls to AI agent systems. Use this skill when: - Building AI agents that call external tools (APIs, databases, file systems) - Implementing policy-based access controls for agent tool usage - Adding semantic intent classification to detect dangerous prompts - Creating trust scoring systems for multi-agent workflows - Building audit trails for agent actions and decisions - Enforcing rate limits, content filters, or tool restrictions on agents - Working with any agent framework (PydanticAI, CrewAI, OpenAI Agents, LangChain, AutoGen)

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

jcasnellie69/homelab-config22026년 10월 16일 업데이트

jcasnellie69의 스킬 모두 보기

이 스킬의 문제 신고