Individual skill

linkedin-post-writer

Write LinkedIn posts built for the feed - a hook that survives the two-line truncation, scannable one-idea-per-line structure, a comment-bait close, and first-hour engagement moves. Use when someone asks "write a LinkedIn post about this", "punch up my LinkedIn hook", "why did my post get no reach", or "turn this win into a LinkedIn post". Do NOT use for Twitter/X threads - use tweet-thread-builder instead. Do NOT use for scheduling across a monthly calendar - use social-content-calendar instead.

skills/linkedin-post-writer/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Not checked yet
Last checked: Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 24
Repository last updated: Oct 13, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

claude Repository topic
claude-skills Repository topic
skill-me Repository topic
writing Derived category
productivity Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 6,937 bytes

Read excerpt


# LinkedIn Post Writer

Write posts for how people actually read LinkedIn: on a phone, fast, in a crowded feed. The feed truncates after roughly two lines, so the costly mistake is spending effort on the body while line one fails to earn the "see more" click - and then abandoning the post at publish, when the first hour of engagement decides whether the algorithm shows it to anyone at all.

## Operating procedure

### Step 1: Gather inputs

1. The story or idea - one concrete moment, result, or claim. If the user offers a vague topic ("leadership"), push for a specific incident or number; specificity is the post.
2. The single takeaway a reader should leave with (one, not five).
3. Proof details: numbers, timeframes, names of situations (anonymized as needed). Label estimates as estimates.
4. The engagement goal: comments (default - comments drive reach hardest), profile visits, or a lead-magnet offer.
5. Whether the user can be online for 60 minutes after posting (this changes the close - see Step 5).