SkillAgentSearch skills...

li-post

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

Install / Use

npx skills add Jakeschincariol/linkedin-agent-skill --skill li-post

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

86/100

Category

Other

Supported Platforms

Claude Code
Zed

Our assessment of li-post

li-post scores 86/100 on our quality scale, 189th of 331 Other skills we index.

Its SKILL.md is 4.2 KB long, split into 6 sections with 4 code examples: a solid amount of guidance for an agent.

It has 671 GitHub stars, a meaningful sign that others use it.

Substance
26/30
Structure
18/20
Description
15/15
Adoption
12/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so li-post is actively maintained.
  • Our last check on 2026-11-03 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

li-post compared with similar skills

All 4 of these similar skills score higher than li-post; compare them before choosing.

SkillScoreStarsUpdatedFormat
li-post (this skill)by Jakeschincariol866712mo agoSKILL.md
LocalAIby mudler10050.4ktodayMCP Server
x402by browser-use100121.0k4d agoSKILL.md
algorithmic-artby anthropics100177.9k56d agoSKILL.md
pptxby anthropics100177.9k56d agoSKILL.md

Frequently asked questions

How do I install li-post?
Run npx skills add Jakeschincariol/linkedin-agent-skill --skill li-post. The install tabs above show the steps for each supported agent.
Which AI agents does li-post work with?
It is written for Claude Code and Zed, as a SKILL.md file. Other agents that read the same format can often use it too.
Is li-post safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is li-post still maintained?
The repository was last updated about 2 months ago, so li-post is actively maintained.

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.

Related Skills

View on GitHub
GitHub Stars671
CategoryOther
Updated2mo ago
Forks98

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions