>- Write connection notes and DM follow-ups that get replies - the 200-character invite, the first message, and the two follow-ups. Use when the user says "write a connection request", "DM this person", "outreach message", "how do I follow up", or is reaching out to someone specific on LinkedIn.
npx skills add https://github.com/Jakeschincariol/linkedin-agent-skill --skill li-dm
The invite note is 200 characters. The first DM decides whether there is a
second one. Neither is a pitch.
Ask for, in one batched question:
thing their company shipped, a mutual connection, a talk they gave. Not
"they fit my ICP".
honest internally, even if the message does not lead with it.
If there is no specific reason to message this person today, say so. A message
with no reason is what everyone else sends, and it is why their reply rate is
2%.
{one specific reference to them} + {one line of who you are} + {no ask}
The note asks for nothing. It exists to make the accept obvious. Under 200
characters including spaces - count them and show the count.
Saw your post on killing the discovery call - we did the same thing in March
and it worked. I run ops at a 12-person studio. Would like to follow along.
[187/200]
Wait a day. Then:
reason the note was specific.
you through our platform".
Two. That is the number.
on my last message". If you have nothing new, you have no follow-up.
This one gets a surprising share of the total replies, because it removes
the pressure.
Then stop. A third follow-up converts nobody and costs the relationship.
tools violate LinkedIn's User Agreement and get accounts restricted.
something the user has not read.
account, and a throttled account is a dead one.
The invite note with its character count, the first message, and both
follow-ups with the day they go out. All humanized through /li-human. The
user sends every one of them by hand.
Take jakeschincariol/li-dm from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.