Lead Scorer

LinkedIn outreach

Core

LinkedIn connection requests that get accepted

Signal-first notes under 200 characters, real daily caps respected, and a hard skip when there is nothing true to say.

Download for claude.ai

What you get

  • Connection notes built on a dated signal, not “I'd love to grow my network”
  • Volume kept inside LinkedIn's real limits — the account is the asset
  • A queue you review before anything is sent

Suggested cadence: Daily batch, capped

MCP tools used

get_leads_from_listget_leadget_lead_postsfetch_profile_postsget_company_infoadd_tags_to_lead

Full tool documentation lives in the app: Lead Scorer → Setup → MCP.

The skill

# LinkedIn connection requests that get accepted

You have the "lead-scorer" MCP server connected (Lead Scorer CRM — endpoint https://mcp.lead-scorer.com/mcp, Bearer key created in Lead Scorer → Settings). Use its tools for every read and write. Never invent data: if a tool result is empty, say so.

> **Context first.** If I have an ICP & offer context pack (see the "ICP & offer context pack" skill), read it before anything else and use it instead of guessing. If I do not, ask me the three questions you actually need answered, then continue.

## Goal
Prepare today's connection requests for list <LIST_ID>: a short, signal-based note per person, inside safe volume limits. I review the batch and send.

## Steps
1. **Pick the batch.** `get_leads_from_list`, keep leads with a verified LinkedIn URL. Cap the batch (see limits below) and prioritize by score and signal freshness.
2. **Find the signal** per lead, best available first: `get_lead_posts` / `fetch_profile_posts` (their own recent post — strongest), then a mutual context or shared background, then a company event (`get_company_info`), then their role reality. **If none of these exists, skip the lead and say so.** A generic note is worse than no note.
3. **Write the note.** Target 150-200 characters:
   - Reference the signal in the first clause, concretely.
   - One sentence on why you specifically are reaching out to them.
   - No pitch, no link, no meeting request. The ask is the connection itself.
4. **Tag** what you used with `add_tags_to_lead` (e.g. `signal:post`, `signal:hiring`) so the post-accept follow-up knows what to build on.
5. **Report** the batch as a table: lead · signal level · note · character count · skip reason if skipped.

## Limits that protect the account (check yours before scaling)
- Personalized note length: **300 characters on Premium/Sales Navigator, 200 on Free/Basic** — and Free/Basic accounts can only add a note to a handful of invitations per month. Write for 200 unless I tell you I'm on Premium.
- Volume: stay around **20-25 invitations per day** and under **~100 per rolling 7 days**. These are LinkedIn's throttling thresholds, not targets.
- Stop immediately on a CAPTCHA or a "weekly invitation limit reached" warning, and tell me.

## Benchmarks (industry figures, not guarantees)
Personalized requests land roughly 35-55% acceptance; generic or blank ones 15-25%. Above 40% is healthy; sustained below 20% means the targeting or the note is wrong — and a low accept rate is itself an account risk. Diagnose the signal level before rewriting the copy.

## Hard rules
- Never guess a LinkedIn profile URL. Verified or skipped.
- Never claim a shared connection, event or read you have not verified.
- Draft only. I send the batch myself.

Pairs well with

Make it yours

Paste the skill into Claude (as a Skill or project instruction) or ChatGPT (custom instructions), edit the My inputs block with your product and ICP, and connect the Lead Scorer MCP. Everything the agent does lands in your Lead Scorer workspace for review — nothing sends without you.