# Write Linkedin Post

> 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.

- Skill: `shyamw-cloud/write-linkedin-post` (Agent Skill)
- Install (CLI): `npx skillmds@latest add shyamw-cloud/write-linkedin-post`
- Raw SKILL.md: https://api.skillmd.com/api/skills/shyamw-cloud/write-linkedin-post/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: shyamw-cloud (https://skillmd.com/u/shyamw-cloud)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/shyamw-cloud/write-linkedin-post

---


# write-linkedin-post

A LinkedIn post that performs has three properties:

1. The first line stops the scroll **before** "see more" is clicked.
2. The body tells a story the reader recognizes (or shows the work behind a result).
3. 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)
```