Agent Native

li-dm

This skill helps write LinkedIn connection requests and direct messages designed to get replies.

by JakeschincariolCommunityNot reviewed

Community author

Agents
Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode, claude.ai and API
License
MIT (permissive)
Pin
add2c23pinned Oct 9, 2026
Context cost
about 700 tokenswhen the skill loads
GitHub stars
1,558on jakeschincariol/linkedin-agent-skill
Scripts
None found

What it does

“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.”
The author's description, from SKILL.md

Generated summary from the skill's own text

This skill helps write LinkedIn connection requests and direct messages designed to get replies. It generates a 200-character invite note, a first follow-up message after acceptance, and two timed follow-ups, all based on a specific reason to reach out to the person.

When to use it

  • Reaching out to a specific person on LinkedIn with a genuine reason
  • Need a connection request that references something concrete about them
  • Writing follow-up messages after someone accepts a connection

When not to

  • Sending bulk or automated outreach campaigns
  • No specific reason to contact the person beyond generic fit criteria

Install

These commands install from the publisher's repository and need no account.

skills CLI

npx skills add jakeschincariol/linkedin-agent-skill --skill li-dm

Installs from the repository's default branch, which may have changed since the commit we checked.

GitHub CLI 2.90 or later

gh skill install jakeschincariol/linkedin-agent-skill li-dm@add2c23882fe79180737d242ff80a5da205eda6a

Installs the commit we checked (add2c23).

Copy by hand

Download the folder at add2c23 and put it in .claude/skills/li-dm for Claude Code and in .agents/skills/li-dm for Codex, Cursor, Gemini CLI, GitHub Copilot and OpenCode.

Skill folder on GitHub at add2c23

Copy for your agent

A prompt for any coding agent. It installs this skill from GitHub at the pinned commit, copies the files as they are, and runs nothing unless you ask.

Prompt

Install the agent skill "li-dm" by Jakeschincariol.

Source, pinned to commit add2c23882fe79180737d242ff80a5da205eda6a:
https://github.com/jakeschincariol/linkedin-agent-skill/tree/add2c23882fe79180737d242ff80a5da205eda6a/skills/li-dm

1. Download that folder at exactly this commit. Do not use the default branch.
2. Copy every file unchanged, keeping the folder structure, into .claude/skills/li-dm/ for Claude Code and .agents/skills/li-dm/ for Codex, Cursor, Gemini CLI, GitHub Copilot and OpenCode. Create the folders if they do not exist.
3. Do not edit the files, and do not run any script in the folder unless I ask you to.
4. When you are done, list the files you copied and where you put them.

Listing and checks: https://www.agentnative.dev/skills/jakeschincariol/li-dm

SKILL.md at the pin

---
name: li-dm
description: >-
  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.
---

# 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.

From jakeschincariol/linkedin-agent-skill at add2c23, shown as plain text under its license: MIT (permissive). The license text is in LICENSE.

View SKILL.md on GitHub at add2c23

Files

1 file, 3.1 KB in total. Each file has a sha256 in the pin's manifest; the first 12 characters are shown.

Skill folder on GitHub at add2c23
  • accelo-automation

    This skill enables agents to automate Accelo project management tasks by discovering and executing operations through Composio's Accelo toolkit via Rube MCP.

    by ComposioOfficial publisher

    Agents not labelled yet · about 690 tokens · pinned 6 days ago

  • acculynx-automation

    This skill automates Acculynx operations by discovering and executing available tools through the Rube MCP server.

    by ComposioOfficial publisher

    Agents not labelled yet · about 690 tokens · pinned 6 days ago

  • active-campaign-automation

    This skill automates ActiveCampaign tasks by discovering and executing tools through Rube MCP and Composio's ActiveCampaign toolkit.

    by ComposioOfficial publisher

    Agents not labelled yet · about 710 tokens · pinned 6 days ago

  • adrapid-automation

    This skill enables agents to automate Adrapid tasks through Composio's toolkit via Rube MCP.

    by ComposioOfficial publisher

    Agents not labelled yet · about 690 tokens · pinned 6 days ago

  • aeroleads-automation

    This skill automates Aeroleads tasks by connecting to the Aeroleads toolkit via Composio's Rube MCP server.

    by ComposioOfficial publisher

    Agents not labelled yet · about 700 tokens · pinned 6 days ago

  • affinity-automation

    This skill automates Affinity CRM operations by executing tools through Rube MCP and Composio's Affinity toolkit.

    by ComposioOfficial publisher

    Agents not labelled yet · about 690 tokens · pinned 6 days ago

The skills listed here are third-party software, collected from public GitHub repositories as a catalog of recent skills and provided as is. Agent Native does not write or control them and is not responsible for any harm, loss or damage caused by installing or using them. Labels and checks describe what we saw at one commit and are not a guarantee. Read a skill's files before you run it. Terms of use