alirezarezvani/claude-skills / marketing/linkedin/skills/linkedin-engagement
linkedin-engagement
VerifiedUse for LinkedIn comments, connection notes, DMs or outreach plans, or checking outreach volume is safe. Plans targets with comment_target_planner.py, drafts notes with outreach_message_builder.py and checks limits with outreach_volume_guard.py.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.0 KB |
| assets/example_outreach.json | config | 607 B |
| assets/outreach_worksheet.md | markdown | 2.4 KB |
| references/comment_strategy.md | markdown | 6.6 KB |
| references/outreach_ethics_and_benchmarks.md | markdown | 6.5 KB |
| scripts/comment_target_planner.py | script | 10.9 KB |
| scripts/outreach_message_builder.py | script | 13.9 KB |
| scripts/outreach_volume_guard.py | script | 9.2 KB |
references/outreach_ethics_and_benchmarks.md
View on GitHub# Outreach Ethics and Benchmarks β what the numbers say, and what they cost
Cold outreach on LinkedIn works and is widely hated, and both facts have the same
cause: it is cheap to send and expensive to receive. The volume that makes it
economically attractive is the volume that makes it spam, and the platform
enforces against the pattern rather than the intent.
This document holds the numbers, with their provenance, and the rules that keep
the practice on the right side of the line.
---
## The benchmarks, with a correction
Third-party outreach studies are large but self-selected: the data comes from
users of outreach tooling, measured by the vendors of that tooling. Treat all of
it π‘.
| Metric | Reported | Source class |
|---|---|---|
| Connection acceptance, platform-wide average | ~26-29% | π‘ multi-million-touch vendor datasets |
| Acceptance with a personalised note | ~26.4% | π‘ same |
| Acceptance with **no** note | ~26.4% | π‘ same |
| Post-accept reply rate, **without** a note | ~5.4% | π‘ |
| Post-accept reply rate, **with** a note | ~9.4% | π‘ |
| Cold InMail response | 10-25% typical | π‘ |
| Individually sent vs bulk InMail | ~15% higher response individually | π’ LinkedIn-reported |
**The correction that matters.** The widely repeated claim is that a personalised
note roughly triples acceptance (β45% vs β15%). The largest available datasets do
not support it: acceptance is close to identical either way (26.42% vs 26.37% in
one ~13M-touch sample). What the note does move β and moves a lot β is the
**reply rate after acceptance**, roughly 5.4% β 9.4%.
The practical conclusion is the same as the folklore's, but the reasoning is
different and it changes what you write. **The note is not there to get the
connection. It is there to earn the conversation.** Which means it should be
about them and about why this conversation, not about you and what you sell.
`outreach_message_builder.py` encodes exactly this: it refuses an ask in a
first-touch connection note, because the note's job is the conversation, not the
meeting.
## The character caps
| Message type | Free | Premium | Confidence |
|---|---|---|---|
| Connection request note | 200 | 300 | π‘ |
| Direct message | ~1,800 | ~1,800 | π‘ |
| InMail body | ~1,900 | ~1,900 | π‘ |
Two hundred characters is roughly two sentences. That is the entire budget, and
it is why the builder puts the person-specific line first and treats everything
else as optional.
## The person-specific line
The builder refuses to assemble a message without one. It is the single
discriminator between outreach and spam, and it is checkable: **could this
sentence have been sent to anyone else on your list?** If yes, it is not
specific.
What qualifies:
- Something they published, named, with the part that mattered to you.
- A decision they made that you are facing.
- A disagreement. "Your point about X is the opposite of what we found" is a
better opener than any compliment.
What does not:
- "I came across your profile."
- Their job title, company, or industry.
- "As a fellow [category]."
- Praise with no specifics, which reads as a mail merge because it usually is.
## Phrases to delete
The builder flags these because they mark a message as bulk before anyone reads
the content: *I came across your profile Β· I'd love to pick your brain Β· hope
this finds you well Β· quick question Β· just following up Β· touch base Β· synergy Β·
I'll keep it short Β· as a fellow Β· I see we're both in Β· let's connect.*
"Pick your brain" deserves a specific note: it asks for unbounded unpaid time
with no bounded question attached. The version that works is the opposite β
one specific question, answerable in two sentences, with an explicit "no reply
needed if you're busy".
## Volume, and what actually triggers restrictions
Covered in full in `linkedin-skills/references/policy_and_account_safety.md`. The
short version:
- Weekly invitation limit observed around **100**, adjusted per account, with
**pending invitations counting against it**. π‘
- Withdrawn invitations cannot be re-sent to the same person for about three
weeks. π‘
- **Low acceptance rate at volume is the discriminating signal**, not volume
alone. Below ~20%, stop and fix the targeting rather than pushing through.
- Machine-regular pacing looks automated whether or not it is.
`outreach_volume_guard.py` refuses above 40 invitations per day outright: nobody
reads that many profiles and writes that many specific lines, so the plan is an
automation plan whatever the intent.
## Follow-up
One follow-up, at least a week later, **only if you have something new to say**.
A second follow-up with no new information is the point at which you become the
thing you were avoiding.
"Just bumping this up" is not new information. A relevant thing that happened
since, or a genuinely useful link with nothing attached, is.
## The order that actually works
1. **Comment on their work for two weeks.** Substantively, in public.
2. **Then send the invitation**, referencing something specific from that
reading β which by now you have actually done.
3. **After acceptance, do nothing for a while.** Then ask, once, small.
This converts far better than any note optimisation, and it is not a growth hack
β it is what happens when you talk to people whose work you read.
## When outreach is the wrong channel
If the target number is the point rather than the people, LinkedIn outreach is
the wrong instrument. Advertising exists, it is designed for volume, it is
honest about what it is, and it does not risk the account you spent a year
building.
---
## Sources
1. LinkedIn. **User Agreement Β§8.2** β automated messaging, bulk sending, and
inauthentic engagement.
2. LinkedIn Help. **"Account restrictions"** and **"Automated activity on
LinkedIn"** β what LinkedIn says it acts on.
3. Expandi. **LinkedIn Outreach Benchmarks** (2026 edition, ~13.2M data points) β
π‘ acceptance with and without a note, and the post-accept reply-rate gap.
4. Cleverly. **LinkedIn Benchmarks** (~20M outreach touches) β π‘ connection and
reply rates by industry.
5. LinkedIn Sales Solutions. **InMail best-practice guidance** β π’ the
individually-sent vs bulk response-rate difference.
6. Cialdini, R. **Influence** β reciprocity and commitment, and why an ask
arriving before any relationship inverts both.
7. Granovetter, M. **"The Strength of Weak Ties"** (1973) β the structural reason
cold outreach works at all, and why it works better after public visibility.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |