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.
What this skill does
# 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.
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing โ use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.