Skip to content
FunCoding

Search

Search docs, Skills and MCP

li-dm

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.

AI 与智能体1.5kskills/li-dm/SKILL.md

Install

Send this to Claude Code, Codex or Cursor. The agent checks the Skill for safety first and installs it only after you confirm.

读取 https://funcoding.ai/skills/jakeschincariol/linkedin-agent-skill/li-dm/install.md ,按里面的步骤帮我安装这个 Skill。

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.

Similar Skills

brand-guidelines
anthropics/skills180k

brand-guidelines

Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.

AI & agents

internal-comms
anthropics/skills180k

internal-comms

A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).

AI & agents

template-skill
anthropics/skills180k

template-skill

Replace with description of the skill and when Claude should use it.

AI & agents

mcp-builder
anthropics/skills180k

mcp-builder

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

AI & agents

algorithmic-art
anthropics/skills180k

algorithmic-art

Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.

AI & agents

academy-guide
anthropics/skills180k

academy-guide

Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.

AI & agents