# Linkedin Copy

> Write LinkedIn posts, profile copy, and professional content. Use when user asks to "write a LinkedIn post", "draft a post for LinkedIn", "update my LinkedIn bio", "write about my experience", "help me post about this", or wants professional content for LinkedIn. Creates authentic, non-cringe professional content.

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

---


# LinkedIn Copy Skill

## The Problem with Most LinkedIn Content

LinkedIn is saturated with:
- Humble brags disguised as lessons ("I was rejected 47 times before...")
- Fake vulnerability ("I almost quit until...")
- Generic advice ("5 things I wish I knew earlier")
- Engagement bait ("Comment YES if you agree")

Good LinkedIn content is rare precisely because it's genuinely useful, honest, and specific.

## What Works

**Specificity over generality**: "We increased checkout conversion by 23% by removing one field" beats "small changes = big results"

**Show the work**: What actually happened, what you built, what you learned. Data > inspiration.

**Honest takes**: Disagree with conventional wisdom if you have evidence. Nuance beats hot takes.

**Short paragraphs**: One idea per paragraph. No walls of text. LinkedIn is a scroll feed.

## Post Formats

### The Observation Post
Share something you noticed that others might have missed.
```
[Specific observation about your field/work]

[Why this matters - the implication]

[Your take or what you're doing about it]
```

### The Build Post
Show something you built, shipped, or created.
```
[What you built - one sentence]

[Why it was hard / what problem it solves]

[Key result or learning]

[Link or call to action if relevant]
```

### The Learning Post
Share something you learned that changed how you think.
```
[The old assumption you had]

[What changed your mind - specific incident, data, or experience]

[The new way you think about it]
```

### The Contrarian Take
Disagree with conventional wisdom, backed by evidence.
```
[The common advice / conventional wisdom]

[Why it's wrong or incomplete - with your evidence]

[What you think instead]
```

## Formatting Rules

- **First line is the hook** - must make someone stop scrolling
- **Short paragraphs** - 1-3 sentences max
- **No bullet lists** on first post (LinkedIn de-ranks heavy formatting)
- **End with a question** only if you genuinely want answers (not engagement bait)
- **No hashtag spam** - 2-3 relevant hashtags maximum, at the end
- **No "thoughts?" at the end** - it's a tell that the post is engagement farming

## Writing the Hook

The first line determines if anyone reads the rest.

**Bad hooks:**
- "Excited to share..."
- "Big news!"
- "After 10 years in [industry]..."
- "Something happened today that changed my perspective..."

**Good hooks:**
- A specific, surprising fact: "We cut our churn by 40% without adding a single feature."
- A counterintuitive claim: "The best engineers I know write less code, not more."
- A specific question: "Why do most SaaS companies die at $10K MRR?"
- The punchline first: "I turned down a $200K offer last month. Here's why it was the right call."

## Profile Copy

### Headline (220 chars)
Not just your job title. What do you do and for whom?
- Bad: "Software Engineer at Acme Corp"
- Good: "Building AI tools for researchers | ex-Google | Founder @ OpenPaper"

### About section
3 paragraphs:
1. What you do now and the problem you solve
2. What you've built or accomplished (specific, with numbers)
3. What you're looking for or interested in connecting about

No buzzwords (passionate, innovative, results-driven). Show, don't tell.

## Output Format

When generating LinkedIn content:
1. The post (ready to copy-paste)
2. Alternative hook options (2-3 variations)
3. Note any parts that sound generic or could be more specific