agentleFS
aakashgaakashg/pm-claude-skills/skills/linkedin-post-writer/SKILL.md

linkedin-post-writer

Skill106 starsChanged 3 months agoMITView on GitHub

Use when the user asks to write, draft, or rewrite a LinkedIn post, turn notes or an article into a LinkedIn post, or fix a hook that is not landing. Do NOT use for X/Twitter threads, newsletters, or blog posts — those need different length and hook rules.

22 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use linkedin-comment-drafter, linkedin-content-planner and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • sergebulaevSkill

    linkedin-comment-drafter

    Draft a LinkedIn comment on someone else's post from its URL, or reshare (repost) it to your feed with optional commentary. Use when the user pastes a post URL and asks to comment, engage, be first commenter, or repost with their thoughts. Produces 1-3 variants in the user's voice, picks a reaction, and publishes via Publora on approval. Not for replying to existing comments (use linkedin-reply-handler).

    Also in 7 projects that use this

  • sergebulaevSkill

    linkedin-content-planner

    Generate a 7-day LinkedIn content plan from a theme, audience, and pillars. Produces per-day post pillar, format, hook type, CTA, posting time, daily comment targets, and a weekly inbound-readiness check. Use when the user wants to plan a week or month of content, not draft a single post (use linkedin-post-writer).

    Also in 7 projects that use this

  • az9713Skill

    linkedin-profile-optimizer

    Optimize LinkedIn profile sections for maximum impact and conversions. Use when the user wants to improve their LinkedIn headline, about section, experience descriptions, or overall profile strategy.

    Also in 10 projects that use this

  • +9 more from sergebulaev

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. 0 are common, 10 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 21 edited versions we read keep these.

  • 10

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read these before writing a single line.

    line 12
  2. Very specific:

    If references/post-patterns.md is missing, say so and proceed with the worked example below only.

    line 21
  3. Distinctive:

    No paragraph longer than 3 lines.

    line 31
  4. Distinctive:

    Never use: delve, landscape, synergy, leverage, robust, streamline, cutting-edge.

    line 33
  5. Distinctive:

    Never open with "I'm excited to announce" or "Thrilled to share."

    line 34
  6. Distinctive:

    No hashtags in the body. If requested, 3–5 after a line break at the end.

    line 35
  7. Distinctive:

    Before drafting, verify three things:

    line 40
  8. Distinctive:

    If two of three are missing, do not draft.

    line 46
  9. Distinctive:

    Ask, in one message:

    line 50
  10. Distinctive:

    If the user pasted raw notes, a thread, or an article, extract the insight yourself and confirm it in one line.

    line 56
  11. Very specific:

    Run this silently. Fix every failure, then present the clean draft.

    line 145
  12. Distinctive:

    If the user liked the post and wants more from the same insight → offer to spin it into a 3-post sequence.

    line 163
  13. Very specific:

    If the insight turns out to be about a product idea they have not validated → recommend /idea-validator before they post a claim they …

    line 164
  14. Very specific:

    If they want to reuse this post as a prompt for future drafts → recommend /prompt-engineer.

    line 165

“Common” is measured: kept by at least 6 in 10 of the 21 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

LinkedIn Post Writer

Turn a rough idea into one publishable LinkedIn post: one hook, one format, one CTA.

Step 0 — Read first

Read these before writing a single line. Do not write from memory of "how LinkedIn posts go."

SourcePathWhat to extract
Project contextCLAUDE.mdWho the user is, their product, banned words, audience
Post patternsreferences/post-patterns.md5 full worked posts + why each works
User's raw inputwhatever they pastedThe one insight, the specific numbers, the personal detail
Prior postsany file/link the user namesTheir actual voice — match it, do not invent one

If references/post-patterns.md is missing, say so and proceed with the worked example below only.

Constraints

These are mandatory. Violating any one means the draft is not done.

  • Hook is ONE line. Two-line hooks lose reach. No exceptions.
  • Total body 800–1,300 characters. Under 800 reads thin; over 1,300 truncates in feed.
  • Exactly ONE call to action. Not two, not "and follow me."
  • Zero or one emoji. Zero is the default.
  • No paragraph longer than 3 lines.
  • The post must contain at least one specific number, name, or timeframe.
  • Never use: delve, landscape, synergy, leverage, robust, streamline, cutting-edge.
  • Never open with "I'm excited to announce" or "Thrilled to share."
  • No hashtags in the body. If requested, 3–5 after a line break at the end.
  • Lead with the insight, never the product. Product appears in context or not at all.

Existence check

Before drafting, verify three things:

  1. The insight — one sentence the reader did not already know.
  2. The evidence — a number, a named result, a specific story the user actually lived.
  3. The audience — a specific person or role, not "professionals."

If two of three are missing, do not draft. Say which are missing and ask for exactly those. A post with no insight and no evidence is engagement bait, and publishing it costs the user credibility.

Step 1 — Gather

Ask, in one message:

  1. What is the one insight or takeaway?
  2. Who is the target reader?
  3. Any hook or angle you want?
  4. Format preference — listicle, story, hot take, before/after, framework, observation — or should I pick?

If the user pasted raw notes, a thread, or an article, extract the insight yourself and confirm it in one line. Never ask the user to organize their notes first.

Step 2 — Pick the format

FormatBest forOptimizes for
ListicleTips, lessons, frameworksSaves
Story arcPersonal turning pointsComments
Hot takeChallenging conventional wisdomShares
Before/afterTransformations, resultsSaves
FrameworkTeaching a conceptSaves
ObservationIndustry trendsSpeed

Output template

Produce exactly this, in this order. No preamble, no "here's your post!"

[HOOK — one line, no context needed to understand it]
[RE-HOOK — one line: adds heft, creates contrast, or preempts the objection]

[BODY — 8–16 lines. Chosen format. 1-3 line paragraphs, alternating single
lines with short clusters. At least one signpost line showing how the author
knows this. Specific numbers throughout.]

[CLOSER — the reusable line. The part someone screenshots.]

[CTA — one question, low friction, easy to answer. "P.S." form works well.]

Then, below the post, output:

  • Character count: [number]
  • Format used: [name]
  • Hook alternatives: two more one-line hooks the user can swap in.

Example

Input: "I want to write about how I only got clients once I stopped posting about myself. Got my first 10 clients in 2024 with under 1,000 followers."

Output:

How to get your first 10 clients on LinkedIn:
(even if you have less than 1,000 followers)

Most people overcomplicate this.

They build funnels, run ads, and buy courses.

But the people I've watched go from 0 to 6 figures did 4 things:

1. Picked ONE problem they solve
→ Not 5. Not "I help businesses grow." One specific pain.

2. Posted 3x/week about that problem
→ Not about themselves. About the reader's pain.

3. Commented on 20 posts a day from their ideal clients
→ Not "Great post!" — they added a missing insight or tip #8.

4. Ended every conversation with "How can I help?"
→ Not "Buy my thing." Just helped. For free. Consistently.

That's it. No funnel. No ads. No viral post needed.

The boring stuff works. Most people just won't do it long enough.

P.S. What's the one thing that got YOU your first client?

Character count: 1,043 Format used: Listicle Why this works: the parenthetical re-hook removes the reader's excuse before they raise it. Each point carries a DO and a DON'T, which forces specificity. The P.S. is low friction.

Four more worked posts — story arc, framework, contrarian, observation — are in references/post-patterns.md. Read them before choosing a format.

Shortcuts Claude takes

What Claude might thinkWhy it's wrong
"The hook works, the checklist is a formality"The checklist catches character count and double-CTA every time. Run it.
"Two lines make a stronger hook"Two-line hooks measurably lose reach. Cut to one.
"I'll add a second CTA so they can also follow"Two CTAs halve the response rate on both.
"The user has no numbers, I'll write it generically"A post with no specifics is indistinguishable from every other post. Ask for the number.
"This is a product launch, so lead with the product"Product-first posts get scrolled. Insight first, always.
"I'll show the draft, then run the checklist"Run it silently first and fix the issues. Show only the clean version.

Exit checklist

Run this silently. Fix every failure, then present the clean draft. Not complete until every box is checked. Any placeholder left in the draft — [name], [number], [company] — is an automatic unchecked box.

  • Hook is one line and works with zero context
  • Re-hook adds contrast, heft, or handles an objection
  • Body is 800–1,300 characters
  • At least one specific number, name, or timeframe appears
  • A signpost line establishes why the author knows this
  • No paragraph exceeds 3 lines
  • Exactly one CTA, phrased as an easy question
  • Zero or one emoji
  • No banned words
  • Read aloud: sounds like a coffee chat, not a keynote
  • Remove any sentence starting with "I'm excited to," "I believe that," "It's important to"
  • No placeholders remain
  • Two alternative hooks are included below the post

Next

  • If the user liked the post and wants more from the same insight → offer to spin it into a 3-post sequence.
  • If the insight turns out to be about a product idea they have not validated → recommend /idea-validator before they post a claim they cannot back.
  • If they want to reuse this post as a prompt for future drafts → recommend /prompt-engineer.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.