write-linkedin-post
A LinkedIn post that performs has three properties:
- The first line stops the scroll before "see more" is clicked.
- The body tells a story the reader recognizes (or shows the work behind a result).
- The post earns its CTA — a real, specific ask, not "thoughts?".
Inputs to gather
Before drafting, confirm:
- Topic — what is this post about in one sentence?
- Voice —
founder-operator, technical-builder, analyst-commentator, or community-host. Default founder-operator.
- Goal — awareness, recruiting, demand-gen, recruiting feedback, community building?
- CTA — what should a reader do? (Reply, click, DM, share their answer.) If no CTA, ask whether to skip it.
- Numbers / specifics — any metric, timeline, or named example to anchor the post. If none, ask before inventing.
If the user hasn't given any of these, ask before drafting (one consolidated question).
Structure
<HOOK — ≤ 12 words, ends with a period.>
<context — 1 short sentence>
<the story / data / before-and-after — 3-6 single-sentence paragraphs>
<the takeaway — 1 line, in plain English>
<CTA — optional, single specific ask>
Total length: 80-180 words. White space is a feature.
Hooks that work (templates, not formulas)
- Counterintuitive claim: "Hiring senior engineers slowed us down."
- Specific number: "We replied to 412 cold emails this quarter. 11 became customers."
- Before/after: "Two years ago I couldn't read a P&L. Last week I closed our seed round."
- Confession: "I shipped a bug to production at 4pm on Friday. Here's what we changed."
- Sharp observation: "Most 'AI strategies' I read are 90% AI and 0% strategy."
Hard rules
- No emojis unless the user explicitly requests them.
- Max 3 hashtags, lowercase, end of post.
- No "agree?", "thoughts?", "what do you think?" as the closer.
- No "I'm thrilled to announce" / "humbled and honored" / "incredibly excited."
- Never invent a number. Use
[INSERT METRIC] if the user hasn't supplied one.
Output format
## Draft (voice: <preset>)
<the post>
## Why this hook
<one line on the angle and why it should stop the scroll>
## Variants
1. <alternate first line — different angle>
2. <alternate first line — different angle>
## Posting checklist
- [ ] Numbers verified
- [ ] Tagged people consented
- [ ] Image / carousel attached (if applicable)
- [ ] Posted to personal vs company page (chosen)
1---2name: write-linkedin-post3description: Use when the user wants to draft a LinkedIn post — launch, lesson learned, hot take, or hiring announcement. Produces a feed-stoppable hook, a tight body, a real CTA, and 2 alternate hooks. Never posts; always returns a draft for approval.4---56# write-linkedin-post78A LinkedIn post that performs has three properties:9101. The first line stops the scroll **before** "see more" is clicked.112. The body tells a story the reader recognizes (or shows the work behind a result).123. The post earns its CTA — a real, specific ask, not "thoughts?".1314## Inputs to gather1516Before drafting, confirm:1718- **Topic** — what is this post about in one sentence?19- **Voice** — `founder-operator`, `technical-builder`, `analyst-commentator`, or `community-host`. Default `founder-operator`.20- **Goal** — awareness, recruiting, demand-gen, recruiting feedback, community building?21- **CTA** — what should a reader do? (Reply, click, DM, share their answer.) If no CTA, ask whether to skip it.22- **Numbers / specifics** — any metric, timeline, or named example to anchor the post. If none, ask before inventing.2324If the user hasn't given any of these, ask before drafting (one consolidated question).2526## Structure2728```29<HOOK — ≤ 12 words, ends with a period.>3031<context — 1 short sentence>3233<the story / data / before-and-after — 3-6 single-sentence paragraphs>3435<the takeaway — 1 line, in plain English>3637<CTA — optional, single specific ask>38```3940Total length: 80-180 words. White space is a feature.4142## Hooks that work (templates, not formulas)4344- **Counterintuitive claim:** *"Hiring senior engineers slowed us down."*45- **Specific number:** *"We replied to 412 cold emails this quarter. 11 became customers."*46- **Before/after:** *"Two years ago I couldn't read a P&L. Last week I closed our seed round."*47- **Confession:** *"I shipped a bug to production at 4pm on Friday. Here's what we changed."*48- **Sharp observation:** *"Most 'AI strategies' I read are 90% AI and 0% strategy."*4950## Hard rules5152- No emojis unless the user explicitly requests them.53- Max 3 hashtags, lowercase, end of post.54- No "agree?", "thoughts?", "what do you think?" as the closer.55- No "I'm thrilled to announce" / "humbled and honored" / "incredibly excited."56- Never invent a number. Use `[INSERT METRIC]` if the user hasn't supplied one.5758## Output format5960```61## Draft (voice: <preset>)62<the post>6364## Why this hook65<one line on the angle and why it should stop the scroll>6667## Variants681. <alternate first line — different angle>692. <alternate first line — different angle>7071## Posting checklist72- [ ] Numbers verified73- [ ] Tagged people consented74- [ ] Image / carousel attached (if applicable)75- [ ] Posted to personal vs company page (chosen)76```
shyamw-cloud