linkedin-post

Category: Content & Multimedia | Uploader: stefanros481 | Downloads: 0 | Version: v1.0（Latest）

Write LinkedIn posts that sound genuinely human — not AI-generated, not corporate, not hollow. Use this skill whenever the user wants to write, draft, rewrite, or improve a LinkedIn post, share a thought on LinkedIn, turn an experience or opinion into a post, announce something professionally, or write about their work, industry insight, or personal story for LinkedIn. Also triggers for "write something for LinkedIn", "help me post about X", or "LinkedIn content". --- # LinkedIn Post Writer Your job is to write LinkedIn posts that feel like they came from a real, confident person — not from a content marketing template. The writing should be specific, direct, and a little bit personal. ## The #1 Rule: Sound Like a Human Before writing anything, internalize what makes LinkedIn writing feel fake: ### ❌ Never do these things - **Hollow openers**: "I'm humbled to announce...", "Excited to share...", "Big news!", "Grateful for this journey" - **Buzzword soup**: leverage, synergy, game-changer, paradigm shift, move the needle, circle back, bandwidth, ninja, rockstar, guru - **Fake vulnerability**: "I failed. Here's what I learned." (as a formula, not a real story) - **Listicle filler**: "5 things I wish I knew about X" with obvious, generic items - **The triple-newline wall**: Every. Single. Sentence. On. Its. Own. Line. For. No. Reason. - **Excessive emojis**: 🚀🔥💡✨ as decoration - **Vague calls to action**: "What do you think? Drop a comment below!" - **Corporate plural voice**: "We are thrilled to announce that our team has..." - **Starting with "I"**: Most LinkedIn posts that start with "I" immediately feel self-promotional. Find a different entry point. ### ✅ Do these things instead - Open with something specific — a detail, a question, an observation, a number - Write in the first person but don't make it *about* you — make it about the idea or the situation - Be direct. If you have an opinion, state it. Don't hedge everything. - Use short paragraphs (2–4 lines max o

Changelog: Source: GitHub https://github.com/stefanros481/ott-platform

Directory Structure

Current level: .claude/skills/linkedin-post/

📁 references/
- 📄 anti-buzzword-list.md 2.8 KB
- 📄 voice-examples.md 5.3 KB
📄 SKILL.md 6.1 KB

SKILL.md

---
name: linkedin-post
description: >
  Write LinkedIn posts that sound genuinely human — not AI-generated, not corporate, not hollow.
  Use this skill whenever the user wants to write, draft, rewrite, or improve a LinkedIn post,
  share a thought on LinkedIn, turn an experience or opinion into a post, announce something
  professionally, or write about their work, industry insight, or personal story for LinkedIn.
  Also triggers for "write something for LinkedIn", "help me post about X", or "LinkedIn content".
---

# LinkedIn Post Writer

Your job is to write LinkedIn posts that feel like they came from a real, confident person — not from a content marketing template. The writing should be specific, direct, and a little bit personal.

## The #1 Rule: Sound Like a Human

Before writing anything, internalize what makes LinkedIn writing feel fake:

### ❌ Never do these things
- **Hollow openers**: "I'm humbled to announce...", "Excited to share...", "Big news!", "Grateful for this journey"
- **Buzzword soup**: leverage, synergy, game-changer, paradigm shift, move the needle, circle back, bandwidth, ninja, rockstar, guru
- **Fake vulnerability**: "I failed. Here's what I learned." (as a formula, not a real story)
- **Listicle filler**: "5 things I wish I knew about X" with obvious, generic items
- **The triple-newline wall**: Every. Single. Sentence. On. Its. Own. Line. For. No. Reason.
- **Excessive emojis**: 🚀🔥💡✨ as decoration
- **Vague calls to action**: "What do you think? Drop a comment below!"
- **Corporate plural voice**: "We are thrilled to announce that our team has..."
- **Starting with "I"**: Most LinkedIn posts that start with "I" immediately feel self-promotional. Find a different entry point.

### ✅ Do these things instead
- Open with something specific — a detail, a question, an observation, a number
- Write in the first person but don't make it *about* you — make it about the idea or the situation
- Be direct. If you have an opinion, state it. Don't hedge everything.
- Use short paragraphs (2–4 lines max on mobile), but don't fragment sentences artificially
- Let the writing breathe — not every paragraph needs a new idea
- Use specific details: companies, tools, dates, numbers, places
- End with a thought, not a prompt — or if you do ask a question, make it genuinely interesting

---

## Post Formats

### 1. Thought Leadership / Hot Take
A direct opinion or observation about the industry. Works best when it's slightly contrarian or when it names something people feel but don't say.

**Structure:**
- Open with the claim or observation (no preamble)
- 2–3 short paragraphs explaining/supporting it
- Optional: one concrete example
- Close with what this means or what you'd do differently

**Good for:** Technical opinions, industry trends, things you've changed your mind about

---

### 2. Story / Lesson Learned
A real experience that taught you something worth sharing. Not a template — an actual thing that happened.

**Structure:**
- Start in the middle of the moment (not "last week I..." — instead, describe the situation)
- What happened, briefly
- What you actually did or thought (the honest version)
- The insight — but only if it's genuinely non-obvious
- Don't moralize. Let the story carry the point.

**Good for:** Career turning points, unexpected problems, things that surprised you

---

### 3. Technical Insight
Explaining something technical in plain language, or sharing something you learned about a specific tool/system/approach.

**Structure:**
- Lead with the problem or question that prompted the insight
- Explain what you found (specific, not vague)
- Brief practical implication
- Optional: code snippet, architecture note, or comparison

**Good for:** Engineering insights, platform learnings, technology recommendations

---

### 4. Announcement
Sharing a new job, project, award, publication, talk, or milestone.

**Structure:**
- Don't lead with "I'm thrilled/honored/humbled"
- Lead with the *thing* itself, stated plainly
- One or two sentences on why it matters or what's next
- Optional: one genuine thank-you that names specific people and why
- Keep it short — announcements don't need much copy

**Good for:** New roles, launches, milestones, talks, publications

---

### 5. Engaging Question / Conversation Starter
A post designed to get substantive replies — not "what do you think?" but a real, specific question that smart people in your field would want to answer.

**Structure:**
- Frame the tension or dilemma clearly
- State your current position or what you're uncertain about
- Ask one specific question

**Good for:** Soliciting peer input, testing ideas, sparking discussion

---

## Workflow

1. **Ask for context** if you don't have it:
   - What's the topic or experience?
   - Any specific angle, tone, or takeaway they want?
   - Audience (technical, general LinkedIn, specific industry)?
   - Any details, numbers, or specifics they can share?

2. **Choose the best format** based on the content. If unsure, suggest 2 options and ask.

3. **Write a draft.** Don't hedge. Write it confidently, as if the person knows their voice.

4. **After the draft**, briefly explain your choices — why this format, what you were going for tonally — and ask if they want a different angle or tone.

5. **If they want revisions**, adjust. Don't rewrite from scratch unless the direction changes fundamentally.

---

## On Length

LinkedIn's sweet spot:
- **Short** (150–300 words): Strong opinions, announcements, quick insights
- **Medium** (300–600 words): Stories, lessons, technical explains
- **Long** (600+ words): Deep-dives, narratives — only if the content genuinely requires it

When in doubt, write shorter. It's harder to cut than to add.

---

## Hashtags

- 3–5 maximum
- Put them at the end, after the body text
- Use specific ones over generic ones: `#StreamingTech` over `#Innovation`
- Never interrupt the flow of writing with inline hashtags unless deliberately building a personal brand keyword

---

## Reference Files

- `references/voice-examples.md` — Good and bad LinkedIn post examples, annotated
- `references/anti-buzzword-list.md` — Extended list of corporate language to avoid

Comments 0

Latest | Hot

Please login before commenting.

No comments yet. Be the first one!

linkedin-post

Directory Structure

SKILL.md

Report

Notice