li-post — Claude Code skill: posts and setup
The li-post skill turns a rough idea into a LinkedIn post with three hook options, a full draft, and a copy-ready version.
MIT ★ 3,812 updated 2026-09-17
/plugin marketplace add Jakeschincariol/linkedin-agent-skill
/plugin install linkedin-agent@linkedin-agent-skillWhat li-post does
li-post takes one idea and shapes it into a LinkedIn text post. It checks hooks.json, selects three distinct hook formulas, explains which one it would use, then writes the complete draft and runs it through /li-human before showing it.
The output includes three numbered openings, one finished post, and a fenced copy block. Nothing is published automatically: an explicit “yes” is required. After that confirmation, the post is appended to ~/.claude/linkedin/log.md with its date, selected hook, and first line.
The skill first looks for ~/.claude/linkedin/voice.md. Without that profile, it asks for three of the author’s earlier posts and creates the voice file, so the draft is grounded in real examples rather than an invented style.
What it helps with
- turn a rough idea into a LinkedIn post
- generate three distinct hook options
- draft copy in the author’s voice
- produce a paste-ready text block
- log a confirmed post for later audits
Example prompts for the agent
/li-postturn this idea into a LinkedIn post: we replaced the weekly report with a short results review- Use
li-postto create three hooks for a post about how we reduced proposal preparation time - Draft a LinkedIn post from this note in my own voice, then wait for my “yes” before logging it
How to install li-post
1Plugin marketplace
/plugin marketplace add Jakeschincariol/linkedin-agent-skill/plugin install linkedin-agent@linkedin-agent-skillThis installs the whole linkedin-agent plugin with all its skills
2Skills CLI (Vercel)
npx skills add Jakeschincariol/linkedin-agent-skill --skill li-post -a claude-code3Manually: put the files in place
~/.claude/skills/li-post/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/li-post/
1Skills CLI (Vercel)
npx skills add Jakeschincariol/linkedin-agent-skill --skill li-post -a codex2Manually: put the files in place
.agents/skills/li-post/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Jakeschincariol/linkedin-agent-skill --skill li-post -a cursor2Manually: put the files in place
.cursor/skills/li-post/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Jakeschincariol/linkedin-agent-skill skills/li-post2Manually: put the files in place
.github/skills/li-post/SKILL.md1Skills CLI (Vercel)
npx skills add Jakeschincariol/linkedin-agent-skill --skill li-post -a gemini-cli2Platform CLI
gemini skills install https://github.com/Jakeschincariol/linkedin-agent-skill --path skills/li-postManually: put the files in place
.devin/skills/li-post/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about li-post
How do I install li-post in Claude Code?
Add the marketplace with /plugin marketplace add Jakeschincariol/linkedin-agent-skill, then install the plugin with /plugin install linkedin-agent@linkedin-agent-skill.
What does li-post do?
It turns one raw idea into a LinkedIn post. The skill proposes three hooks, writes the full draft, sends it through /li-human, and provides a copy-ready block.
What does li-post need to match my voice?
It reads ~/.claude/linkedin/voice.md. If that file is missing, the skill asks for three earlier posts and builds the voice profile from them.
Source text
SKILL.md · MIT
---
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.
---
# 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 line 2.
## The loop
**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.
## Rules that make the difference
- **One idea per post.** If the draft has two, you have two posts. Say so.
- **Numbers over adjectives.** "$4,200" beats "a lot". If the user has not
given you a number, ask for one rather than writing around the hole.
- **No engagement bait.** "Thoughts?" and "Agree?" are dead. The closing
question has to be one only this post could ask.
- **Three hashtags maximum**, at the bottom, and only if they are real
categories someone follows.
- **No links in the post body.** LinkedIn suppresses posts with outbound
links. Put the link in the first comment and say so in the receipt.
- **Never fabricate.** No invented metrics, clients, revenue figures or
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.
## Example
```
/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.
```
© Jake Schincariol · MIT · Jakeschincariol/linkedin-agent-skill