← ClaudeAtlas

li-postlisted

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.
robbiehaynes/job-search · ★ 0 · AI & Automation · score 62
Install: claude install-skill robbiehaynes/job-search
# li-post Turns one raw idea into a LinkedIn post that sounds like the person who posted it. ## Before you write 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. ## The shape 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