agentleFS
styfinitystyfinity/linkedin-engine/skills/linkedin-post-writer/SKILL.md

linkedin-post-writer

Skill9 starsChanged 4 months agoMITView on GitHub

Draft a viral-ready LinkedIn post using one of ten proven hook formulas, sized 900 to 1,300 characters, shown as a draft before anything touches LinkedIn. Use when you have a topic and want a post that proves competence and pulls engagement.

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 7 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

  • +6 more from sergebulaev

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 21 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write the hook so the first 210 to 235 characters (everything visible before "see more") carry all four value levers at once: dream outcome …

    line 18
  2. Distinctive:

    No em-dashes. No banned hype words.

    line 35

“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

The hero skill. Turns a topic and a shred of proof into a post that earns attention and proves the competence the buyer is buying. Drafts only, never posts.

Inputs

  • The topic or angle, plus any proof you have (a number, a before/after, a build): $ARGUMENTS
  • The brief (persona, voice profile, offer, pains) loads automatically.

Do this

  1. Pick the best-fit hook formula from THE TEN, given the topic and proof: Pattern-Break, Counter-Intuitive Insight, Experience-Led Observation, Direct Consequence, Confession+Result, Numbered Promise, Enemy-Hero-Gasoline-Teaser, BREAKING/News framing, Stat-Anchored (X% vs Y%), Mechanism-Reveal.
  2. Write the hook so the first 210 to 235 characters (everything visible before "see more") carry all four value levers at once: dream outcome up, perceived likelihood up, time-delay down, effort down.
  3. Body gives a SYSTEM, not tips: name the parts and show the arrows between them. Include one copy-paste-able artefact line (a prompt, a check, a template line). Quantify one before/after in money and hours. Land one contrarian quotable line.
  4. Close with a comment-keyword CTA plus a connect line (e.g. "comment WORD and I'll send it").
  5. Total length 900 to 1,300 characters. Count it.

Output

  • The post, ready to read top to bottom.
  • The hook formula used (one of THE TEN).
  • The visible-before-cut preview (first 210 to 235 chars, exactly what shows before "see more").
  • The character count.
  • A suggested comment keyword.
  • A note: run /linkedin-humanizer next before posting.

Rules

  • Sell the operator, not the artefact: the topic must PROVE the competence the buyer is buying, even when it is not literally the product.
  • Outcome + mechanism: name the outcome and reveal the mechanism. AI does the volume, operator judgment picks the targets. Position the operator as a Revenue Partner who uses AI to do the heavy lifting.
  • Proof attributes to "a post", "a client", or "an operator", never to a named person or company.
  • No em-dashes. No banned hype words.
  • Draft only. Pass the draft through /linkedin-humanizer before posting. Nothing auto-posts; the operator approves and publishes.

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.