agentleFS
Sign inStart free
prosyo-aiprosyo-ai/gtm-skill/skills/linkedin-connection-note/SKILL.md

linkedin-connection-note

Skill13 starsChanged 21 days agoMITView on GitHub

Use this skill when you need LinkedIn connection request notes that get accepted: \"write a connection note\", \"my acceptance rate is low\", \"connect with prospects without being salesy\". Writes short notes under the character limit built on a real reason to connect (shared topic, trigger, community, event or their content), with no pitch, and gives variants for cold prospects, event attendees, post engagers and referrals. Includes when to send no note at all.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    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. Distinctive:

    Use this for the first step of LinkedIn outreach.

    line 16
  2. Distinctive:

    No links, no product, no "I'd love to tell you about".

    line 39
  3. Distinctive:

    Write it now, so acceptance leads into a conversation within 1-3 days while you are still recognised.

    line 45
  4. Distinctive:

    MUST stay under the character limit of the user's account.

    line 62
  5. Distinctive:

    MUST use a real reason; never invent a mutual connection, event or shared interest.

    line 63
  6. Distinctive:

    NEVER pitch or include links in a connection note.

    line 64
  7. Distinctive:

    NEVER exceed safe daily invitation volumes (typically 15-25 per day per account).

    line 65

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Use this for the first step of LinkedIn outreach. The note has one job: get accepted by giving a genuine reason to connect. Selling comes later, and only if the conversation earns it.

Inputs

  • The prospect: name, role, company, recent activity.
  • The reason to connect: shared topic, trigger, event, community, mutual connection, their content.
  • Who you are, in a few words.

The play

1. Find the reason

ReasonStrengthNote pattern
Referral from a mutual connectionStrongest"Sam suggested we connect about..." (only if true)
They engaged with your contentStrong"Thanks for your comment on..."
Same event or communityStrong"Saw you're at <event> next week too..."
Their contentStrong"Your post on <specific point>..."
Role or industry peerMedium"I work with a lot of <role>s in <industry>..."
Trigger (new role, hiring)Medium"Congrats on <role>, <specific note>"

2. Write the note

  • Under 200 characters; shorter is usually better. Free accounts may have a lower limit and a monthly cap on notes, so check yours.
  • One reason, one sentence about it, no ask beyond the connection.
  • No links, no product, no "I'd love to tell you about".

3. Decide whether to send a note at all

For senior executives with no real hook, and for people who post a lot and connect openly, a blank request often performs as well or better. Test both on 100+ requests before deciding.

4. Plan the first message after acceptance

Write it now, so acceptance leads into a conversation within 1-3 days while you are still recognised.

Examples

  • Content: "Your post on why SDR ramp is a data problem made me rethink our onboarding. Would be good to connect."
  • Event: "See you're at the RevOps summit next week, I'll be there too. Happy to connect beforehand."
  • Peer: "I spend most of my week with heads of ops at multi-site restaurant groups. Would be good to have you in my network."
  • New role: "Congrats on the move to Fabrikam. Building ops from scratch at that stage is a fun problem."

What good looks like

  • Acceptance rate of 30-50% on a targeted list. Under 20% means the targeting or the note is wrong.
  • Nothing in the note could be called a pitch.
  • The common mistake is the "pitch in the invite": a note that ends in "would love to show you how we help companies like yours".

Rules

  • MUST stay under the character limit of the user's account.
  • MUST use a real reason; never invent a mutual connection, event or shared interest.
  • NEVER pitch or include links in a connection note.
  • NEVER exceed safe daily invitation volumes (typically 15-25 per day per account).

Example prompts

  • "Write connection notes for these 25 VPs of Sales. Most have posted about hiring."
  • "My acceptance rate is 12%. Rewrite my note."
  • "Write notes for people attending the same conference as me."

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.

Check your setup, free