agentleFS
avi691avi691/linkedin-agent-skill/skills/li-dm/SKILL.md

li-dm

Skill5 starsChanged 37 days agoMITView on GitHub

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.

7 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

8 rules. 8 are common, 0 are distinctive, and 0 are very specific to this project.

  • 8

    Common

    Most of the 3 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Ask for, in one batched question:

    line 17
  2. Common:

    If there is no specific reason to message this person today, say so.

    line 26
  3. Common:

    Wait a day. Then:

    line 47
  4. Common:

    +4 days: - add something new. Never "just bumping this" or "following up on my last message".

    line 61
  5. Common:

    Never send an automated connection or message sequence.

    line 71
  6. Common:

    Never fabricate a mutual connection, a shared school, or having read something the user has not read.

    line 73
  7. Common:

    Never write the message that opens "I hope this message finds you well".

    line 75
  8. Common:

    Never send more than 20 invites a day.

    line 76

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

li-dm

The invite note is 200 characters. The first DM decides whether there is a second one. Neither is a pitch.

Before writing, get the specifics

Ask for, in one batched question:

  1. Who - name, role, company.
  2. The hook - the actual reason to reach out now. A post they wrote, a thing their company shipped, a mutual connection, a talk they gave. Not "they fit my ICP".
  3. What the user wants - a conversation, a referral, a job, a sale. Be 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%.

The invite note (200 characters)

{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]

The first message, after they accept

Wait a day. Then:

  • Two to four sentences. A screen of text is a delete.
  • Reference the specific thing from the note - continuity is the whole reason the note was specific.
  • Give something before asking. A number, a template, a name, an answer.
  • One ask, and make it small. "Worth a 15-minute call?" beats "let me walk you through our platform".
  • No calendar link in message one. It reads as a funnel, because it is.

Follow-ups

Two. That is the number.

  • +4 days - add something new. Never "just bumping this" or "following up on my last message". If you have nothing new, you have no follow-up.
  • +10 days - the close-the-loop message. Say you will stop, and mean it. 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.

Never

  • Never send an automated connection or message sequence. Automated outreach tools violate LinkedIn's User Agreement and get accounts restricted.
  • Never fabricate a mutual connection, a shared school, or having read something the user has not read.
  • Never write the message that opens "I hope this message finds you well".
  • Never send more than 20 invites a day. Beyond that, LinkedIn throttles the account, and a throttled account is a dead one.

Output

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.