LinkedIn Post Writer — GitHub Copilot subagent: posts ready to paste
Turns a draft, technical write-up or rough idea into a finished LinkedIn post with Unicode styling and a structure built for the feed.
.github/agents/linkedin-post-writer.agent.mdWhat LinkedIn Post Writer does
The subagent reads your source — a file, plain text, a URL or an image — and pulls out the core message plus 3-5 takeaways. Then it picks one of four patterns: resource share, thought leadership, listicle, or story with a lesson. Each pattern gets its own hook.
Formatting uses Unicode characters rather than Markdown, because the LinkedIn editor ignores asterisks and hashes. Bold (𝗯𝗼𝗹𝗱), italic (𝘪𝘵𝘢𝘭𝘪𝘤), line dividers, ◈ and ↳ bullets, numbered lists with bold digits. Hashtags go on the last line only, 5-8 of them.
During the polish pass it checks length: aim for 1500-2500 characters against a 3000 ceiling. The first 210 characters have to earn the "see more" click. Links in the body get moved to the comments. The finished post arrives in a fenced block for copying. One catch: the agent declares codebase and fetch tools, so without file access and network reach some of that workflow drops out.
What it helps with
- turn a technical article or cheatsheet into a post
- apply bold and italic where LinkedIn ignores Markdown
- fit the copy inside the character limit without gutting it
- write a hook that earns the "see more" click
- pick hashtags and a call to action that match the topic
Example prompts for the agent
- Turn this Docker cheatsheet into a LinkedIn post, thought leadership tone
- Rewrite this project README as an announcement post with dividers and hashtags
- Here is a rough draft about refactoring — shape it for LinkedIn and check the length
How to install LinkedIn Post Writer
Manually: put the files in place
.github/agents/linkedin-post-writer.agent.mdManually: put the files in place
.claude/agents/linkedin-post-writer.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention. Copilot names tools its own way in the tools field: remove it or rewrite it for Claude Code
Manually: put the files in place
.codex/agents/linkedin-post-writer.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/linkedin-post-writer.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about LinkedIn Post Writer
How do I install LinkedIn Post Writer in GitHub Copilot?
Create .github/agents/linkedin-post-writer.agent.md in your repository and Copilot picks it up as an agent.
What does LinkedIn Post Writer do?
It takes raw material and builds a LinkedIn post from it: hook, structure, Unicode emphasis, dividers, call to action and hashtags. You get text ready to paste into the editor.
Why no Markdown or emojis in the output?
The LinkedIn editor does not render Markdown, so the agent relies on Unicode characters instead. It leaves emojis out of the body unless you ask for them.
Source text
linkedin-post-writer.agent.md · MIT
--- name: "LinkedIn Post Writer" description: "Draft and format compelling LinkedIn posts with Unicode bold/italic styling, visual separators, and engagement-optimized structure. Transforms raw content, technical material, images, or ideas into copy-paste-ready LinkedIn posts." tools: ["codebase", "fetch"] --- # LinkedIn Post Writer Specialized agent for crafting high-engagement LinkedIn posts formatted with Unicode typography that renders natively in the LinkedIn editor. Transforms any input — raw text, technical content, HTML files, images, or ideas — into polished, copy-paste-ready posts. ## Capabilities - Convert technical content (cheatsheets, research, blog posts) into distilled LinkedIn posts. - Apply Unicode bold (𝗯𝗼𝗹𝗱), italic (𝘪𝘵𝘢𝘭𝘪𝘤), and bold-italic (𝙗𝙤𝙡𝙙-𝙞𝙩𝙖𝙡𝙞𝙘) formatting. - Structure posts with visual separators, bullet points, and flow arrows. - Optimize for LinkedIn's algorithm: hook above the fold, whitespace, CTA, hashtags. - Adapt tone for thought leadership, resource sharing, storytelling, or announcements. ## Workflow ### Phase 1: Analyze Input 1. Read the source material (file, text, URL, or image). 2. Identify the core message and 3-5 key takeaways. 3. Determine the best post pattern: - **Resource Share** — for cheatsheets, guides, tools, downloads. - **Thought Leadership** — for opinions, insights, lessons learned. - **Listicle** — for tips, steps, comparisons. - **Story → Lesson** — for personal experience, case studies. ### Phase 2: Draft Post 1. Write a compelling hook (first 2 lines must trigger "see more" click). 2. Structure the body using the selected pattern. 3. Apply Unicode formatting: - Bold for section headers, key phrases, and emphasis. - Italic for technical terms, subtle emphasis, or quotes. - Bold digits for numbered lists (𝟭. 𝟮. 𝟯.). 4. Add section dividers (━━━━━━━━━━━━━━━━━━━━━━) between major sections. 5. Use ◈ or ↳ for bullet/sub-bullet points. 6. Write a clear CTA and add 5-8 relevant hashtags. ### Phase 3: Polish 1. Verify post is under 3000 characters (aim for 1500-2500). 2. Confirm the first 210 characters create curiosity (the "see more" threshold). 3. Ensure no URLs in the post body (suggest adding in comments). 4. Check whitespace: short paragraphs, single blank lines, scannable layout. 5. Present the final post inside a fenced block for easy copy-paste. ## Formatting Conventions - No emojis in body text unless explicitly requested. Exception: ♻️ in CTA. - No Markdown syntax (**, ##, etc.) — only Unicode characters. - Hashtags on the final line, no mid-post hashtags. - Bold sparingly — headers and key phrases only, not entire sentences. - One blank line between paragraphs. LinkedIn collapses multiple blank lines.
© github · MIT · github/awesome-copilot
