linkedin-post-writer v1.0.0A

Immutable. This exact content never changes and is served at /api/v1/blob/7e7a63cb99c06c13.

---
name: linkedin-post-writer
description: "Use this skill when you need LinkedIn posts that build pipeline, not just likes: \"write a LinkedIn post\", \"turn this idea into a post\", \"ghostwrite posts for our founder\", \"plan a week of LinkedIn content\". Picks a post format (story, lesson, contrarian take, how-to, data, behind the scenes), writes a hook that earns the click on see more, keeps the body skimmable, ends with a conversation-starting question, and matches the author's voice. Includes a content plan that ties posts to the buyer's problems."
license: MIT
metadata:
  title: LinkedIn post writer
  category: linkedin
  tags: "Founders, Marketing, Sales, Agencies"
  author: prosyo
  version: "1.0.0"
  keywords: "linkedin post writer, linkedin post ideas for b2b, ghostwriting linkedin posts, claude linkedin post skill, linkedin hook examples"
  inputs: "Idea, story or data point, Author voice samples, Target buyer"
  outputs: "Post drafts in two or three formats, Hooks, Content plan"
---

Use this to turn an idea, a customer story or an opinion into a post the right buyers read and respond to. Posts that build pipeline teach buyers something about their own problem; posts that only build reach entertain peers.

## Inputs

- The idea, story, lesson or data point.
- Two or three past posts or messages by the author, for voice.
- The target buyer and the problem space.

## The play

### 1. Pick a format
| Format | Shape | Best for |
| --- | --- | --- |
| Story | Situation → tension → turn → lesson | Founders, customer moments |
| Lesson list | Hook → 3-7 numbered lessons → takeaway | Experience-based expertise |
| Contrarian take | Common belief → why it's wrong → what works | Standing out in a crowded topic |
| How-to | Problem → steps → result | Practical, saveable content |
| Data post | Surprising number → what it means → what to do | Credibility with analytical buyers |
| Behind the scenes | What we tried → what happened → what we learned | Trust, transparency |

Read [references/post-formats.md](references/post-formats.md) for a template and an example of each.

### 2. Write the hook
The first two lines decide whether anyone clicks "see more". Hooks that work: a specific number, a counter-intuitive claim, a vivid moment, or the reader's exact problem. Avoid questions as the very first line and avoid "I'm excited to announce".

### 3. Make the body skimmable
One idea per line or short paragraph. White space. No more than 1,300 characters for most posts; long only when the story earns it. No external links in the post body; put them in a comment if needed.

### 4. End with a conversation
A specific question invites comments from buyers: "How long does month-end take your team?" beats "Thoughts?".

### 5. Match the voice
Use the author's words, sentence length and level of formality. A founder who writes plainly should not suddenly sound like a motivational speaker.

## What good looks like

- A buyer would save it or send it to a colleague.
- The hook is specific; the lesson is earned by the story.
- The common mistake is broetry: one-line dramatic sentences, a fake story, and a lesson nobody needed. Readers spot it and so does the algorithm's audience.

## Rules

- MUST keep stories and numbers true; ask the author for details rather than invent them.
- MUST match the author's voice and approve before posting.
- NEVER name customers or share their results without approval.
- NEVER engagement-bait ("comment YES to get the guide") unless the user explicitly chooses that tactic.

## Example prompts

- "Turn this customer story into a LinkedIn post for our founder."
- "Write a contrarian post about why more SDRs doesn't mean more pipeline."
- "Plan 8 posts for the next month aimed at heads of RevOps."