Skip to main content
creating-linkedin-posts
Published by @askskills
Writes a scroll-stopping LinkedIn feed post that builds professional authority. Use when drafting a short-form LinkedIn text post to grow reach, credibility, or inbound.
Third-Party Content
This skill is created by a third-party developer, not Asterism. While security-scanned, we cannot guarantee safety. By using any skill, you accept our Terms of Service and assume all risk.
Installation
aster install creating-linkedin-postsUniversal installation
By installing, you accept the Terms of Service. Skills are third-party content; Asterism is not liable for their use.
README
# Creating LinkedIn Posts
LinkedIn's feed rewards **dwell time** (how long a reader stops on your post) and **early engagement** (comments/reactions in the first 60–90 minutes). Everything below optimizes for those two signals. This is for native, short-form **text posts** — the format that consistently out-reaches links, reshares, and polished graphics for most accounts.
## The one rule that governs everything: the fold
On desktop and mobile, LinkedIn truncates your post at roughly **210 characters** (about 3 short lines) and hides the rest behind **"…see more."** Most readers decide to expand or scroll based on those 210 characters alone. If they don't click "see more," the algorithm reads it as a low-dwell impression and throttles distribution.
So the hook is not the "intro." **The hook is the entire job of the first two lines.** Write the body second.
### Hook rules
- Front-load the tension, number, or claim in **line 1**. No warm-up ("I've been thinking a lot about…" is dead on arrival).
- Keep line 1 under ~50 characters so it never wraps awkwardly on mobile.
- Put a **line break after the first sentence.** White space above the fold pulls the eye down.
- Never spend hook real estate on a link, a hashtag, or "Excited to announce."
- Create an **open loop** — a question the reader can only close by expanding.
### 5 hook templates (steal these)
1. **Contrarian claim:** `Most [role]s optimize for the wrong metric.` → then reveal which.
2. **Specific result + timeframe:** `We cut onboarding from 14 days to 3. Here's the exact change:`
3. **Confession / vulnerability:** `I got fired from the best job I ever had.`
4. **Curiosity gap with a number:** `9 words changed how my team runs standups.`
5. **Named-enemy / myth-bust:** `"Post daily to grow" is terrible advice. Do this instead.`
Bonus for B2B — **the two-line problem→promise:** `Your best rep just quit. / Here's the retention playbook that would've kept them.`
## Ideal length
**900–1,300 characters** (roughly 150–220 words) is the sweet spot. Long enough to deliver a real idea and rack up dwell time; short enough that mobile readers finish it. Under ~500 chars usually feels thin and gets little dwell; over ~1,800 and completion rate drops. If you have more to say, it's a carousel or an article, not a feed post.
## Formatting for the phone (most reading happens on mobile)
- **1–2 sentences per "paragraph."** Then a blank line. Dense blocks get scrolled past.
- Line length: aim for **6–12 words** so nothing wraps mid-thought.
- Use a **blank line between every idea.** White space _is_ the design.
- Lists: use `→`, `•`, or `—` as bullets. LinkedIn strips real markdown, so type the glyph.
- No markdown bold/italics — LinkedIn renders `**text**` literally. Use Unicode bold (𝗹𝗶𝗸𝗲 𝘁𝗵𝗶𝘀) sparingly; it breaks screen readers, so prefer plain structure.
- **Emojis:** 0–3, functional not decorative (a checkmark, an arrow). A wall of 🔥🚀💯 reads as spam.
## Links kill reach — put them in the first comment
LinkedIn suppresses posts with **outbound links in the body** because it wants readers to stay on-platform. A raw link in the post can cut reach materially.
**The fix:** post with **no link in the body.** End with `Link in the comments 👇`, then drop the URL as the **first comment** within seconds of publishing. You keep the reach and still route clicks. (If you must include a link in-body, strip UTM clutter and put it on its own line at the very end.)
## One idea per post
The highest-performing posts make **exactly one point.** If a reader can't finish the sentence "This post is about \_\_\_" in five words, it's two posts. A tight single idea is more shareable, more quotable in comments, and easier for the algorithm to match to an audience. Save the other ideas — that's next week's content.
## The repeatable post skeleton
```
HOOK 1–2 lines. Tension/claim/number. Break after line 1.
CONTEXT 2–3 lines. The situation or stakes. Why this matters now.
INSIGHT The one idea. The reframe, the lesson, the "here's what nobody says."
EXAMPLE A concrete proof point. Real numbers, real dialogue, real outcome.
TAKEAWAY Distill it to a line the reader can repeat to a colleague.
CTA A soft, genuine question that invites a story — not "Agree? 👇"
```
The CTA should ask for an **experience**, not a vote. "What's the worst hiring advice you ever got?" earns comments. "Thoughts?" does not. Comments are the single strongest reach lever — an open question at the end is how you earn them.
## Hashtags: the reality
3–5 **relevant** hashtags, placed at the **bottom** after a blank line. They're a weak topical signal, not a discovery engine — 30 hashtags looks desperate and does nothing. Mix one broad (#Leadership), one niche (#B2BSaaS), one you'd genuinely follow. Don't invent a "branded" hashtag nobody searches and expect magic.
## Best-performing formats
- **Personal story** — a specific moment (a firing, a failed launch, a mentor's line) → the lesson. Highest dwell, highest shares.
- **Contrarian take** — name the conventional wisdom, then dismantle it with evidence. Generates comments (people argue).
- **How-I-did-X** — a transparent teardown with real numbers and the exact steps. Builds authority fastest.
- **Listicle** — "5 things I'd tell my younger self." Scannable, saveable, screenshot-able.
- **Framework** — name a repeatable model (give it a memorable name). Named frameworks get quoted back to you and travel.
Rotate them. An account that only posts wins looks like a highlight reel; mix vulnerability, teaching, and opinion.
## Cadence & timing
- **2–4 posts/week** beats daily-mediocre. Consistency > volume.
- Best windows for most B2B audiences: **Tue–Thu, 7:30–9:30am** in your audience's timezone (before/at the start of the workday).
- **Reply to every comment in the first hour.** Each reply is fresh engagement that extends the post's life in the feed.
- Don't edit the post for ~60 minutes after publishing — some accounts see a distribution reset on early edits. Proofread _before_ you hit post.
---
## Example post 1 — Contrarian take (how-I-did-X)
```
"Post every day" is the worst LinkedIn advice I ever followed.
I did it for 90 days straight.
Reach went down.
Here's what actually happened:
Daily posting forced me to publish half-baked ideas
just to keep the streak alive. My audience learned
that most of my posts weren't worth stopping for —
so they stopped stopping.
Then I switched to 3 posts a week.
One rule: don't publish unless I'd text it to a smart friend.
30 days later:
→ 2.4x the reach per post
→ 5x the comments
→ 11 inbound conversations (vs. 1 the month before)
The algorithm doesn't reward how often you post.
It rewards how long people stop when you do.
Fewer posts. Higher standard. More reach.
What's a "best practice" you followed that quietly backfired?
#ContentStrategy #LinkedInTips #B2BMarketing
```
_Why it works:_ contrarian hook with an open loop, one idea (quality > frequency), concrete before/after numbers, a quotable takeaway, and a CTA that asks for a story. ~1,050 characters.
## Example post 2 — Personal story (framework)
```
A junior designer asked me for feedback and I made her cry.
Not because the work was bad.
Because I led with everything wrong with it.
That was the day I built the "1-1-1" feedback rule,
and I've used it for every review since:
1 thing that's working (be specific — "the spacing on
the pricing table makes it scannable," not "looks good").
1 thing that would make the biggest difference if changed
(just one — not the whole list).
1 question that hands them the wheel
("what were you going for in the header?").
Same honesty. None of the ambush.
Her next revision was the best work on the team.
Harsh feedback feels efficient. It isn't.
People can't hear the fix while they're defending themselves.
What's the best feedback anyone ever gave you —
and how did they frame it?
#Leadership #DesignManagement #Feedback
```
_Why it works:_ vulnerable one-line hook, single idea (framing feedback), a named framework that travels ("1-1-1"), a specific example, and a question that invites the reader's own story. ~1,080 characters.
---
## Common mistakes
- **Burying the hook.** Opening with context/credentials instead of the claim. The first line must earn the "see more."
- **Putting the link in the body.** Instant reach penalty. First comment, always.
- **Two ideas in one post.** Dilutes the message and the algorithm's targeting. Split it.
- **Dense paragraphs.** Desktop-written walls of text no one reads on a phone. One breath per line.
- **Fake vulnerability / manufactured "inspiration."** Formulaic "broetry" ("And then it hit me. / Everything changed.") reads as a template. Earn the emotion with specifics.
- **Weak CTA.** "Thoughts?" / "Agree?" get nothing. Ask for a concrete experience.
- **Engagement bait.** "Comment YES to get my free guide" tanks credibility and gets down-ranked.
- **Posting and ghosting.** Not replying to early comments wastes the reach window.
- **30 hashtags.** Signals spam. 3–5, relevant, at the bottom.
- **Broadcasting, never conversing.** Only announcing your wins/launches. Teach and reflect ~80% of the time; promote ~20%.
- **Editing right after posting.** Proof first; early edits can reset distribution.
- **Ignoring the first 5 words.** They're all a scroller sees before deciding. Rewrite them last, and make them the sharpest in the post.
## Pre-publish checklist
- [ ] Line 1 lands the hook in < 50 characters and creates an open loop
- [ ] Body is 900–1,300 characters, one idea only
- [ ] Every paragraph is 1–2 short lines with white space between
- [ ] No link in the body (URL staged for first comment)
- [ ] Ends with a specific, story-inviting question
- [ ] 3–5 relevant hashtags at the bottom
- [ ] Proofread — no post-publish edits for the first hour
- [ ] Posted in the audience's morning window; ready to reply for 60 minutes
Sign in to leave a comment