linkedin-outreach

LinkedIn outreach with Curtis

The MCP server already carries its own manual in its instructions (operation order, limits, handling a HALT). This skill covers what those instructions cannot say: how to prepare a campaign that actually works, and how to read the result.

Preparing the list

Before importing, look at the CSV. Only the profile-URL column is required, but the quality of the others decides the quality of the messages:

• A first_name separate from last_name makes {firstName} reliable. With only full_name the tool takes the first word: on "Dr. Mark White" that becomes "Dr.".
• Every extra column becomes {custom.COLUMN_NAME}. One Industry or Event column is worth more than ten lines of generic copy.
• After import_contacts, check rows_invalid and rows_url_inferred. "Inferred" rows carried only a slug: if there are many, the wrong column almost always ended up in the URL field.

Always show the user a preview before enrolling contacts into a campaign.

Writing the first message

It goes in the step after acceptance, never in the invite note (free accounts get 5 notes per month).

Rules that move the acceptance rate more than any setting:

• Spintax is mandatory on the opening: {Hi|Hello|Hey} {firstName}. Identical messages sent in bulk are one of the strongest bot signals.
• One specific reason for writing to this person in particular: {company}, {headline}, or a custom column. If the message works verbatim for anyone, it works for no one.
• No pitch in the first message. Its goal is a reply, not a call.
• Stay under 400 characters.

Before launching, show the user the message rendered against 2–3 real contacts from their list, not an invented example.

Reading the numbers

In get_metrics, the only number that really matters is the acceptance rate:

What you see	What it means	What to do
> 60%	targeting is right	volume can grow, gradually
40–60%	normal	change nothing
< 40%	the list or the message is the problem	the controller brakes on its own: don't fight it, fix the targeting
entries in signals_7d	LinkedIn noticed something	lower the volume, don't raise it