# LinkedIn post formatter Human Guide

## What This Is For
Transform raw content, ideas, or technical material into polished, engagement-optimized LinkedIn posts using Unicode typography and proven structural patterns. It gives the agent a clearer input/output frame for social content: what context to ask for, what decisions to make, and what usable artifact to return.

Use this as a human-readable version of the LinkedIn post formatter agent skill. It is meant for marketers, operators, founders, and other non-coders who want the workflow without reading agent-specific implementation instructions.

## When To Use This
- Use this when you need a repeatable process for LinkedIn post formatter.
- Use this when the task needs judgment, examples, constraints, or a clear output format rather than a one-off prompt.
- Use this when you want to hand an AI assistant enough context to produce a usable marketing artifact.

## When Not To Use This
- Do not use this when you only need a quick factual answer.
- Do not use this when the work depends on private data you cannot share with the assistant.
- Do not use this as a replacement for legal, compliance, financial, or medical review.

## What You Need Before Starting
- The goal or business outcome you want.
- The audience, customer segment, or market context.
- Any source material the assistant should respect, such as notes, briefs, examples, URLs, or brand guidance.
- Constraints such as tone, length, channel, deadline, region, or approval requirements.
- A clear definition of what a good final answer should look like.

## Step-By-Step Workflow
1. State the job clearly: "Use the LinkedIn post formatter guide to help me with..."
2. Add context: audience, goal, offer, channel, source material, and constraints.
3. Ask the assistant to identify missing inputs before producing the final output.
4. Have the assistant follow the skill-specific guidance below.
5. Review the result against the final checklist and ask for revisions where needed.

## Skill-Specific Guidance
- **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.
- **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).

## Decision Points And Nuance
The original skill emphasizes: Overview, Unicode Typography Reference, Bold (Mathematical Sans-Serif Bold), Italic (Mathematical Sans-Serif Italic), Bold-Italic (Mathematical Sans-Serif Bold Italic), Visual Separators, Post Structure Patterns, Pattern 1: Hook → Content → CTA (General Purpose), Pattern 2: Listicle (Numbered Insights), Pattern 3: Story → Lesson (Thought Leadership).

Use these questions to steer the work:
- What is the intended audience or buyer?
- What source material must be preserved?
- What should the assistant optimize for: clarity, persuasion, accuracy, speed, creativity, or conversion?
- What examples represent the desired quality bar?
- What should the assistant avoid?

## Common Mistakes
- **Hook above the fold**: The first 2-3 lines must compel the reader to click "see more." Front-load value.

## Copy-And-Paste Prompt
```text
Use the LinkedIn post formatter human guide.

My goal:
[Describe the business outcome]

Audience:
[Describe who this is for]

Context and source material:
[Paste notes, examples, links, or existing copy]

Constraints:
[Tone, length, channel, timeline, must-include items, must-avoid items]

Before producing the final output, ask me for any missing information that would materially improve the result.
```

## Final Checklist
- [ ] The output matches the original goal.
- [ ] The audience and context are reflected in the answer.
- [ ] Important constraints and source material were preserved.
- [ ] The assistant made the relevant decisions explicit.
- [ ] The final artifact is ready to use, review, or hand to the next person.

## Source
This guide was generated from the github/awesome-copilot skill entry for `linkedin-post-formatter`.

## Source Skill Notes
These notes preserve the nuance from the original skill. Use them as supporting reference when the workflow above feels too generic.

# 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]