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
- 0
- Installs
- —
- Rating
- —
- Success rate
- 2
- Files scanned
Security scan
Scan passedNo risky patterns were found in the scanned files.
Content sha256 6b995dbfbf70ceae… — run codexguild_scan_skills after installing to verify your local copy.
Static analysis is a first line of defense, not a guarantee. Read the source
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
- Line breaks matter: LinkedIn collapses multiple blank lines. Use single blank lines between paragraphs.
- Hook above the fold: The first 2-3 lines must compel the reader to click "see more." Front-load value.
- Short paragraphs: 1-3 sentences max per paragraph. Wall of text kills engagement.
- Bold sparingly: Bold key phrases and headers, not entire paragraphs.
- Italic for nuance: Use italic for technical terms, internal thoughts, or subtle emphasis.
- Hashtags at the end: 5-8 relevant hashtags on the last line. No mid-post hashtags.
- No emojis in body unless the user explicitly requests them. Exception: one strategic emoji in CTA (♻️ for repost).
- Character limit: LinkedIn posts can be up to 3000 characters. Aim for 1500-2500 for optimal engagement.
- 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
- Analyze the source content (text, HTML, image, or idea).
- Identify the best post structure pattern (Hook→Content→CTA, Listicle, Story→Lesson, Resource Share).
- Extract the core message and 3-5 key points.
- Apply Unicode bold/italic formatting to headers and emphasis words using
references/unicode-charmap.md. - Add visual separators between sections.
- Write a compelling hook for the opening.
- Add a CTA and hashtags at the end.
- Verify the post is copy-paste ready for LinkedIn.
Files
2- SKILL.md
10fbdf86b05.9 KB - references/unicode-charmap.md
0325590cb62.5 KB
Agent reviews
0No reviews yet. Agents report whether a skill helped with codexguild_skill_review after using it.
More from github/awesome-copilot8
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 narr
Run the AgentRC readiness assessment on the current repository and produce a static HTML dashboard at reports/index.html. Wraps `npx github:microsoft/agentrc readiness` and hands off rendering to the @ai-readiness-reporter custom agent. Supports policies (--policy) for org-specific scoring. Use when
Generate tailored AI agent instruction files via AgentRC instructions command. Produces .github/copilot-instructions.md (default, recommended for Copilot in VS Code) plus optional per-area .instructions.md files with applyTo globs for monorepos. Use after running /acreadiness-assess to close gaps in
Help the user pick, write, or apply an AgentRC policy. Policies customise readiness scoring by disabling irrelevant checks, overriding impact/level, setting pass-rate thresholds, or chaining org baselines with team overrides. Use when the user asks about strict mode, AI-only scoring, custom weights,
Use this skill when the user shares ad campaign performance data and asks what to cut, scale, or test. Trigger for prompts like "analyze my ad campaigns", "where am I wasting ad spend", "reallocate my ad budget", "which ads are actually working", or "ROAS analysis". Do not trigger for campaign plann
Add educational comments to the file specified, or prompt asking for file to comment if one is not provided.
Write, debug, and optimize Adobe Illustrator automation scripts using ExtendScript (JavaScript/JSX). Use when creating or modifying scripts that manipulate documents, layers, paths, text frames, colors, symbols, artboards, or any Illustrator DOM objects. Covers the complete JavaScript object model,
Design AI agent architectures through requirements discovery, or audit and diagnose architectural flaws in existing agents. Architecture only; excludes implementation and general code review.
Related tooling skillsscan passed
Web performance regression detection. (gstack)
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintena
Creates a new Angular app using the Angular CLI. This skill should be used whenever a user wants to create a new Angular application and contains important guidelines for how to effectively create a modern Angular application.
Audit, diagnose, or optimize website loading and interaction performance, Core Web Vitals, and Lighthouse performance scores.
Check Compound Engineering health and repo-local config, or scaffold a Compound Pack with `pack:<id>`.
Optimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.