Skip to main content
Version History
v2.0.0
Latest
Breaking
No changelog provided
Jul 20, 2026
11 downloads100/100
v1.0.0
No changelog provided
Mar 7, 2026
11 downloads100/100
Compare Versions
View differences between any two versions of this skill.
From:
→To:
+176
-23
SKILL.md
| 1 | 1 | --- | |
| 2 | 2 | name: creating-linkedin-posts | |
| 3 | - | description: Writes professional LinkedIn content that builds authority. Use when you need assistance with creating linkedin posts. | |
| 3 | + | version: 2.0.0 | |
| 4 | + | description: 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. | |
| 5 | + | category: marketing | |
| 6 | + | license: MIT | |
| 4 | 7 | --- | |
| 5 | 8 | ||
| 6 | - | # Creating Linkedin Posts | |
| 9 | + | # Creating LinkedIn Posts | |
| 7 | 10 | ||
| 8 | - | Writes professional LinkedIn content that builds authority | |
| 11 | + | 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. | |
| 9 | 12 | ||
| 10 | - | ## Viral Potential: ⭐⭐⭐⭐⭐ | |
| 13 | + | ## The one rule that governs everything: the fold | |
| 11 | 14 | ||
| 12 | - | **⭐ FEATURED SKILL** - Top 10 in ${category.name} | |
| 15 | + | 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. | |
| 13 | 16 | ||
| 14 | - | ## When to Use | |
| 17 | + | So the hook is not the "intro." **The hook is the entire job of the first two lines.** Write the body second. | |
| 15 | 18 | ||
| 16 | - | - Writes professional LinkedIn content that builds authority | |
| 19 | + | ### Hook rules | |
| 17 | - | - Working on related social media tasks | |
| 18 | - | - Need expert guidance on creating linkedin posts | |
| 19 | 20 | ||
| 20 | - | ## Instructions | |
| 21 | + | - Front-load the tension, number, or claim in **line 1**. No warm-up ("I've been thinking a lot about…" is dead on arrival). | |
| 22 | + | - Keep line 1 under ~50 characters so it never wraps awkwardly on mobile. | |
| 23 | + | - Put a **line break after the first sentence.** White space above the fold pulls the eye down. | |
| 24 | + | - Never spend hook real estate on a link, a hashtag, or "Excited to announce." | |
| 25 | + | - Create an **open loop** — a question the reader can only close by expanding. | |
| 21 | 26 | ||
| 22 | - | 1. Understand the context and requirements | |
| 27 | + | ### 5 hook templates (steal these) | |
| 23 | - | 2. Apply best practices for creating linkedin posts | |
| 24 | - | 3. Provide actionable recommendations | |
| 25 | - | 4. Iterate based on feedback | |
| 26 | 28 | ||
| 27 | - | ## Examples | |
| 29 | + | 1. **Contrarian claim:** `Most [role]s optimize for the wrong metric.` → then reveal which. | |
| 30 | + | 2. **Specific result + timeframe:** `We cut onboarding from 14 days to 3. Here's the exact change:` | |
| 31 | + | 3. **Confession / vulnerability:** `I got fired from the best job I ever had.` | |
| 32 | + | 4. **Curiosity gap with a number:** `9 words changed how my team runs standups.` | |
| 33 | + | 5. **Named-enemy / myth-bust:** `"Post daily to grow" is terrible advice. Do this instead.` | |
| 28 | 34 | ||
| 29 | - | ### Example: Basic Request | |
| 35 | + | Bonus for B2B — **the two-line problem→promise:** `Your best rep just quit. / Here's the retention playbook that would've kept them.` | |
| 30 | - | User: "Help me with creating linkedin posts" | |
| 31 | - | Response: Provide tailored assistance based on the specific need. | |
| 32 | 36 | ||
| 33 | - | ## Guidelines | |
| 37 | + | ## Ideal length | |
| 34 | 38 | ||
| 35 | - | - Follow industry best practices | |
| 39 | + | **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. | |
| 36 | - | - Provide actionable, specific advice | |
| 37 | - | - Consider the target audience | |
| 38 | - | - Iterate and refine based on feedback | |
| 39 | 40 | ||
| 41 | + | ## Formatting for the phone (most reading happens on mobile) | |
| 42 | + | ||
| 43 | + | - **1–2 sentences per "paragraph."** Then a blank line. Dense blocks get scrolled past. | |
| 44 | + | - Line length: aim for **6–12 words** so nothing wraps mid-thought. | |
| 45 | + | - Use a **blank line between every idea.** White space _is_ the design. | |
| 46 | + | - Lists: use `→`, `•`, or `—` as bullets. LinkedIn strips real markdown, so type the glyph. | |
| 47 | + | - No markdown bold/italics — LinkedIn renders `**text**` literally. Use Unicode bold (𝗹𝗶𝗸𝗲 𝘁𝗵𝗶𝘀) sparingly; it breaks screen readers, so prefer plain structure. | |
| 48 | + | - **Emojis:** 0–3, functional not decorative (a checkmark, an arrow). A wall of 🔥🚀💯 reads as spam. | |
| 49 | + | ||
| 50 | + | ## Links kill reach — put them in the first comment | |
| 51 | + | ||
| 52 | + | 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. | |
| 53 | + | ||
| 54 | + | **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.) | |
| 55 | + | ||
| 56 | + | ## One idea per post | |
| 57 | + | ||
| 58 | + | 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. | |
| 59 | + | ||
| 60 | + | ## The repeatable post skeleton | |
| 61 | + | ||
| 62 | + | ``` | |
| 63 | + | HOOK 1–2 lines. Tension/claim/number. Break after line 1. | |
| 64 | + | CONTEXT 2–3 lines. The situation or stakes. Why this matters now. | |
| 65 | + | INSIGHT The one idea. The reframe, the lesson, the "here's what nobody says." | |
| 66 | + | EXAMPLE A concrete proof point. Real numbers, real dialogue, real outcome. | |
| 67 | + | TAKEAWAY Distill it to a line the reader can repeat to a colleague. | |
| 68 | + | CTA A soft, genuine question that invites a story — not "Agree? 👇" | |
| 69 | + | ``` | |
| 70 | + | ||
| 71 | + | 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. | |
| 72 | + | ||
| 73 | + | ## Hashtags: the reality | |
| 74 | + | ||
| 75 | + | 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. | |
| 76 | + | ||
| 77 | + | ## Best-performing formats | |
| 78 | + | ||
| 79 | + | - **Personal story** — a specific moment (a firing, a failed launch, a mentor's line) → the lesson. Highest dwell, highest shares. | |
| 80 | + | - **Contrarian take** — name the conventional wisdom, then dismantle it with evidence. Generates comments (people argue). | |
| 81 | + | - **How-I-did-X** — a transparent teardown with real numbers and the exact steps. Builds authority fastest. | |
| 82 | + | - **Listicle** — "5 things I'd tell my younger self." Scannable, saveable, screenshot-able. | |
| 83 | + | - **Framework** — name a repeatable model (give it a memorable name). Named frameworks get quoted back to you and travel. | |
| 84 | + | ||
| 85 | + | Rotate them. An account that only posts wins looks like a highlight reel; mix vulnerability, teaching, and opinion. | |
| 86 | + | ||
| 87 | + | ## Cadence & timing | |
| 88 | + | ||
| 89 | + | - **2–4 posts/week** beats daily-mediocre. Consistency > volume. | |
| 90 | + | - Best windows for most B2B audiences: **Tue–Thu, 7:30–9:30am** in your audience's timezone (before/at the start of the workday). | |
| 91 | + | - **Reply to every comment in the first hour.** Each reply is fresh engagement that extends the post's life in the feed. | |
| 92 | + | - Don't edit the post for ~60 minutes after publishing — some accounts see a distribution reset on early edits. Proofread _before_ you hit post. | |
| 93 | + | ||
| 94 | + | --- | |
| 95 | + | ||
| 96 | + | ## Example post 1 — Contrarian take (how-I-did-X) | |
| 97 | + | ||
| 98 | + | ``` | |
| 99 | + | "Post every day" is the worst LinkedIn advice I ever followed. | |
| 100 | + | ||
| 101 | + | I did it for 90 days straight. | |
| 102 | + | Reach went down. | |
| 103 | + | ||
| 104 | + | Here's what actually happened: | |
| 105 | + | ||
| 106 | + | Daily posting forced me to publish half-baked ideas | |
| 107 | + | just to keep the streak alive. My audience learned | |
| 108 | + | that most of my posts weren't worth stopping for — | |
| 109 | + | so they stopped stopping. | |
| 110 | + | ||
| 111 | + | Then I switched to 3 posts a week. | |
| 112 | + | One rule: don't publish unless I'd text it to a smart friend. | |
| 113 | + | ||
| 114 | + | 30 days later: | |
| 115 | + | → 2.4x the reach per post | |
| 116 | + | → 5x the comments | |
| 117 | + | → 11 inbound conversations (vs. 1 the month before) | |
| 118 | + | ||
| 119 | + | The algorithm doesn't reward how often you post. | |
| 120 | + | It rewards how long people stop when you do. | |
| 121 | + | ||
| 122 | + | Fewer posts. Higher standard. More reach. | |
| 123 | + | ||
| 124 | + | What's a "best practice" you followed that quietly backfired? | |
| 125 | + | ||
| 126 | + | #ContentStrategy #LinkedInTips #B2BMarketing | |
| 127 | + | ``` | |
| 128 | + | ||
| 129 | + | _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. | |
| 130 | + | ||
| 131 | + | ## Example post 2 — Personal story (framework) | |
| 132 | + | ||
| 133 | + | ``` | |
| 134 | + | A junior designer asked me for feedback and I made her cry. | |
| 135 | + | ||
| 136 | + | Not because the work was bad. | |
| 137 | + | Because I led with everything wrong with it. | |
| 138 | + | ||
| 139 | + | That was the day I built the "1-1-1" feedback rule, | |
| 140 | + | and I've used it for every review since: | |
| 141 | + | ||
| 142 | + | 1 thing that's working (be specific — "the spacing on | |
| 143 | + | the pricing table makes it scannable," not "looks good"). | |
| 144 | + | ||
| 145 | + | 1 thing that would make the biggest difference if changed | |
| 146 | + | (just one — not the whole list). | |
| 147 | + | ||
| 148 | + | 1 question that hands them the wheel | |
| 149 | + | ("what were you going for in the header?"). | |
| 150 | + | ||
| 151 | + | Same honesty. None of the ambush. | |
| 152 | + | Her next revision was the best work on the team. | |
| 153 | + | ||
| 154 | + | Harsh feedback feels efficient. It isn't. | |
| 155 | + | People can't hear the fix while they're defending themselves. | |
| 156 | + | ||
| 157 | + | What's the best feedback anyone ever gave you — | |
| 158 | + | and how did they frame it? | |
| 159 | + | ||
| 160 | + | #Leadership #DesignManagement #Feedback | |
| 161 | + | ``` | |
| 162 | + | ||
| 163 | + | _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. | |
| 164 | + | ||
| 165 | + | --- | |
| 166 | + | ||
| 167 | + | ## Common mistakes | |
| 168 | + | ||
| 169 | + | - **Burying the hook.** Opening with context/credentials instead of the claim. The first line must earn the "see more." | |
| 170 | + | - **Putting the link in the body.** Instant reach penalty. First comment, always. | |
| 171 | + | - **Two ideas in one post.** Dilutes the message and the algorithm's targeting. Split it. | |
| 172 | + | - **Dense paragraphs.** Desktop-written walls of text no one reads on a phone. One breath per line. | |
| 173 | + | - **Fake vulnerability / manufactured "inspiration."** Formulaic "broetry" ("And then it hit me. / Everything changed.") reads as a template. Earn the emotion with specifics. | |
| 174 | + | - **Weak CTA.** "Thoughts?" / "Agree?" get nothing. Ask for a concrete experience. | |
| 175 | + | - **Engagement bait.** "Comment YES to get my free guide" tanks credibility and gets down-ranked. | |
| 176 | + | - **Posting and ghosting.** Not replying to early comments wastes the reach window. | |
| 177 | + | - **30 hashtags.** Signals spam. 3–5, relevant, at the bottom. | |
| 178 | + | - **Broadcasting, never conversing.** Only announcing your wins/launches. Teach and reflect ~80% of the time; promote ~20%. | |
| 179 | + | - **Editing right after posting.** Proof first; early edits can reset distribution. | |
| 180 | + | - **Ignoring the first 5 words.** They're all a scroller sees before deciding. Rewrite them last, and make them the sharpest in the post. | |
| 181 | + | ||
| 182 | + | ## Pre-publish checklist | |
| 183 | + | ||
| 184 | + | - [ ] Line 1 lands the hook in < 50 characters and creates an open loop | |
| 185 | + | - [ ] Body is 900–1,300 characters, one idea only | |
| 186 | + | - [ ] Every paragraph is 1–2 short lines with white space between | |
| 187 | + | - [ ] No link in the body (URL staged for first comment) | |
| 188 | + | - [ ] Ends with a specific, story-inviting question | |
| 189 | + | - [ ] 3–5 relevant hashtags at the bottom | |
| 190 | + | - [ ] Proofread — no post-publish edits for the first hour | |
| 191 | + | - [ ] Posted in the audience's morning window; ready to reply for 60 minutes | |
| 192 | + |