li-audit
Post-mortem on what the user has already published - which posts actually worked, why, and…
Write a LinkedIn post from a raw idea using 21 proven hook formulas, in the user's own voice, humanized so it does not read as AI. Use whenever the user wants a LinkedIn post, a hook, a draft for the feed, "post about X", "turn this into a LinkedIn post", or asks for hook
$ npx -y skills add Jakeschincariol/linkedin-agent-skill --skill li-post --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/li-postContext preview
The summary Claude sees to decide when to auto-load this skill.
Write a LinkedIn post from a raw idea using 21 proven hook formulas, in the user's own voice, humanized so it does not read as AI. Use whenever the user wants a LinkedIn post, a hook, a draft for the feed, "post about X", "turn this into a LinkedIn post", or asks for hook
name: li-post description: >- Write a LinkedIn post from a raw idea using 21 proven hook formulas, in the user's own voice, humanized so it does not read as AI. Use whenever the user wants a LinkedIn post, a hook, a draft for the feed, "post about X", "turn this into a LinkedIn post", or asks for hook options. Produces three hook options, one full draft, and a copy-ready block that is never published without an explicit yes.
Turns one raw idea into a LinkedIn post that sounds like the person who posted it.
1. Read `~/.claude/linkedin/voice.md` if it exists. That file is the user's voice profile: how they talk, what they never say, who they are talking to. If it does not exist, ask for **three of their own past posts**, infer the voice from those, and write the file. Do not skip this and do not invent a voice. A post in the wrong voice is worse than no post. 2. Read `hooks.json` in this folder. All 21 formulas, with templates, filled examples, what each is for, and how each one usually gets ruined. 3. If the idea is thin - "post about AI" - do not pad it. Ask one batched question: what happened, to whom, and what did it cost or return. A post needs one specific true thing. Get it before writing.
LinkedIn rewards dwell time, saves and comments, in that order. So:
Line 1 the hook. Alone. It has to survive truncation at ~140 chars mobile.
Line 2 the payoff of line 1, not setup for line 3.
Body short paragraphs, 1-3 lines each, blank line between every one.
No wall. The white space is the format.
The turn one line that reframes what came before.
Close one specific question, or one instruction. Never both.Length: 900-1,300 characters is the working range for a text post. Under 400 reads as a thought, not a post. Over 2,000 needs to earn every line, and the "see more" tap has to be paid for by line 2.
**1. Pick three hooks, not one.** Run the idea through `hooks.json` and choose the three formulas that genuinely fit it. Different formulas, not three variations of one. Show them as three numbered lines and say which you would ship and why, in one sentence.
**2. Draft the full post** on the strongest hook.
**3. Humanize it.** Run the draft through `/li-human` before showing it. Every post from this skill ships humanized. That is not an optional extra step, it is the reason the draft is worth reading.
**4. Print the block.** Copy-ready, in a fenced block, exactly as it should be pasted. Then, underneath:
POST READY hook: #17 Time Anchor length: 1,140 characters humanizer: 6 artefacts stripped, human score 84 PASS post at: Tuesday 8:15am ET (from your plan) Reply "yes" to log it, or tell me what to change.
**5. Never publish.** This skill produces text. The user posts it. On "yes", append the post to `~/.claude/linkedin/log.md` with the date, the hook used and the first line, so `/li-audit` has a history to work from later.
given you a number, ask for one rather than writing around the hole.
question has to be one only this post could ask.
categories someone follows.
links. Put the link in the first comment and say so in the receipt.
outcomes under the user's name, even as a placeholder. If a number is needed and unknown, leave `{{your number}}` in the draft and flag it.
/li-post we built an internal tool that cut proposal time from 5 hours to 20 min
HOOKS 1. #17 Time Anchor Writing a proposal used to take me 5 hours. It now takes 20 minutes. 2. #12 Comparison A $12,000 proposal writer vs a weekend and a template. The weekend won. 3. #3 Mistake For two years I charged clients for hours I was wasting on formatting. Shipping #17: the ratio is believable and the number is yours.
Eleven Claude skills that run a LinkedIn account. Free, MIT, no signup, no API key, nothing to connect. One of them writes your posts off 21 hook formulas. One comments on other people's posts. One handles the replies under yours.
Post-mortem on what the user has already published - which posts actually worked, why, and…
Build a LinkedIn document post (carousel) - slide-by-slide copy, the cover that earns the…
Write comments on other people's LinkedIn posts that read as a person with an opinion, not a…
Write connection notes and DM follow-ups that get replies - the 200-character invite, the…
Strip the machine fingerprint out of any draft - em dashes, AI slop words, invisible…
Triage the LinkedIn inbox - sort connection requests and DMs into leads, recruiters, peers…