jakeschincariol/linkedin-agent-skill

li-dm

- Write connection notes and DM follow-ups that get replies - the 200-character invite, the first message, and the two follow-ups.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/jakeschincariol/linkedin-agent-skill --skill li-dm

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

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

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

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
jakeschincariol
コミュニティ

li-audit

- Post-mortem on what the user has already published - which posts actually worked, why, and what to stop doing. Use when the user pastes their LinkedIn analytics or past posts and asks "what's working", "why did this flop", "read my analytics", "audit my content", or wants to know what to double down on.

導入数
1
GitHub Stars
2393
更新日
9月17日
jakeschincariol
コミュニティ

li-comment

- Write comments on other people's LinkedIn posts that read as a person with an opinion, not a bot. Use when the user pastes a post and wants a comment, says "comment on this", "engage with this", "what do I say here", or wants a batch of comments for their engagement round.

導入数
1
GitHub Stars
2393
更新日
9月17日
jakeschincariol
コミュニティ

li-human

- Strip the machine fingerprint out of any draft - em dashes, AI slop words, invisible watermark characters - and score it against a five-check detection panel before it goes out. Use whenever text needs to sound human, when the user says humanize, "does this sound like AI", "remove the em dashes", "de-slop this", "will this get flagged", or before any LinkedIn post, comment, reply or DM is shown to the user.

導入数
1
GitHub Stars
2393
更新日
9月17日
jakeschincariol
コミュニティ

li-inbox

- Triage the LinkedIn inbox - sort connection requests and DMs into leads, recruiters, peers and spam, and draft the replies worth sending. Use when the user says "my inbox is a mess", "triage my DMs", "should I reply to this", pastes a batch of LinkedIn messages, or is drowning in connection requests.

導入数
1
GitHub Stars
2393
更新日
9月17日