LinkedIn Manager · Setup Guide
00 / LinkedIn manager
This is the set of Claude skills I run my LinkedIn on. One writes the post. One writes comments for the posts you want to be seen under. One sorts the comments on your own posts into leads and noise. One plans the week. Nothing posts by itself: every skill ends in text you copy and paste.
The pack is linkedin-agent-skill by Avi Grondin and Jake Schincariol, free under the MIT license. The skills are theirs. What follows is the setup order and the weekly routine I use.
01 / Before you start
| Item | What | Note |
|---|---|---|
| Claude | A Claude plan that includes Claude Code | Claude Code runs all eleven skills and the humanizer's two scripts |
| Your writing | Three posts or emails that sound like you | They become your voice file in step 2 |
| Time | One paste to install, ten minutes on the voice file | The voice file is where the time should go |
| Not needed | No API key, no signup, nothing connected to your LinkedIn account | The skills write. You post |
No Claude Code? You can paste a single skill file at the top of a normal Claude chat and it works as a mode. You lose the humanizer's scripts that way, and the humanizer is the reason the rest is usable, so Claude Code is worth setting up.
02 / The setup
The fastest way is to let Claude do it. Open Claude Code and paste this.
https://github.com/avi691/linkedin-agent-skill Install this skill, then confirm /li-post works.
Or do it yourself in a terminal. This copies the eleven skill folders to where Claude Code looks for them.
git clone https://github.com/avi691/linkedin-agent-skill.git cp -r linkedin-agent-skill/skills/li-* ~/.claude/skills/
Every skill reads one file: ~/.claude/linkedin/voice.md. It says who you are, who you
write for, what you sell, the words you use and the words you would never use. The pack ships a
template.
mkdir -p ~/.claude/linkedin cp linkedin-agent-skill/templates/voice.md ~/.claude/linkedin/voice.md
You can fill it in by hand. The better way is to hand Claude your own writing and let it do the first pass, then correct what it got wrong.
Write my voice.md from these three posts and save it to ~/.claude/linkedin/voice.md
Skip it and every draft comes out sounding like everyone else's. Ten minutes here is the difference between drafts you post and drafts you rewrite.
Give /li-post one raw idea. Something that happened this week works better than a topic.
/li-post why we text back every missed call inside a minute
You get three hook options, one full draft, and a copy-ready block. Pick the hook that sounds like something you would say out loud. Edit the draft once. It is your name on it.
/li-human is two small scripts that run on your machine. The first strips what your
keyboard never types: invisible characters, em dashes, curly quotes, and a list of stock phrases. The
second scores what is left.
/li-human check this draft before I post it
Or run the scripts directly from ~/.claude/skills/li-human/.
python3 humanize.py draft.txt --report # clean it, show every change python3 detect.py draft.txt # score it, five checks
These are local checks modelled on what detectors look for. They are not a detector, and they cannot promise what one will say. Nobody can sell you "undetectable". What they do is catch the things a reader notices too.
03 / The week
This is the order I run them in. The inbox comes first, because a person waiting on a reply is worth more than a new post.
| When | Skill | What you get |
|---|---|---|
| Every day | /li-inbox |
Your inbox sorted into lead, recruiter, peer, ask and spam, with replies drafted |
| Every day | /li-comment |
Paste a post you want to be seen under and get a comment that adds something. Never "Great post!" |
| Every day | /li-reply |
The comments under your own post sorted into lead, substance, peer, support and noise, answered in that order |
| When you reach out | /li-dm |
The invite note, the first message, and two follow-ups |
| Mon, Wed, Fri | /li-post |
One post per slot, humanized before you see it |
| Sunday | /li-plan |
What to post, when to post it, and the 10 people to engage with |
| Weekly | /li-audit |
What worked in what you already published, ranked by engagement rate, not impressions |
| As needed | /li-carousel /li-repurpose /li-profile |
Document posts, one long piece into a week of posts, and a profile score out of 100 with rewrites |
| Every draft | /li-human |
The last step before anything is pasted into LinkedIn |
Watch /li-reply. It reads the thread under your post and tells you which commenters are
leads and which are noise, so the person worth a conversation does not get the same thank you as
everyone else.
04 / Guardrails
These are how the pack is built, not settings you have to remember to switch on.
05 / If you get stuck
Almost nobody stalls on the install. They stall on the voice file, because writing down who you sell to and what you sound like is harder than it looks. Then they stall in week three, when the novelty is gone and the Monday post still has to go out.
The tool is free and stays free. If you would rather set it up with someone who runs it every day, that is a conversation I am happy to have.
Tell me what you sell and who buys it. I will tell you which skill to start with.