agentleFS
styfinitystyfinity/linkedin-engine/skills/linkedin-outreach/SKILL.md

linkedin-outreach

Skill9 starsChanged 4 months agoMITView on GitHub

Find decision-makers by title and seniority, draft connection notes under 200 characters referencing something specific, and send via the connected CLI capped at 20 per day. Use when you want to start outbound connection requests to a defined ICP.

7 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use cold-email.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ukunal91appSkill

    cold-email

    Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions "cold outreach," "prospecting email," "outbound email," "email to leads," "reach out to prospects," "sales email," "follow-up email sequence," "nobody's replying to my emails," or "how do I write a cold email." Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences. For warm/lifecycle email sequences, see email-sequence. For sales collateral beyond emails, see sales-enablement.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 4

    Distinctive

    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:

    Search for matching decision-makers, live via the connected MCP layer if it is wired, or from a pasted or seed list if not.

    line 16
  2. Distinctive:

    After approval: a send summary - sent count, remaining in today's 20, and what was held for tomorrow.

    line 24
  3. Distinctive:

    Every note references one real, specific detail.

    line 30
  4. Distinctive:

    No em-dashes. No exclamation marks.

    line 31

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “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

LinkedIn Outreach

The hero outbound skill. Find the right decision-makers, write a short human connection note for each, and send only what the operator approves, inside the ban-safe daily cap.

Inputs

  • Target title(s), seniority, geography, and how many: $ARGUMENTS
  • The brief (ICP, voice profile, offer, pains) loads automatically.

Do this

  1. Search for matching decision-makers, live via the connected MCP layer if it is wired, or from a pasted or seed list if not. State which source you used.
  2. Filter the results to the brief's ICP. Drop anyone outside the title, seniority, or geography rules. Say who you cut and why.
  3. For each person, draft a connection note UNDER 200 characters that references one real specific detail (a post they wrote, a recent role move, a shared context). Count the characters and show the count.
  4. Present the whole queue as DRAFTS for approval. Nothing leaves yet.
  5. On explicit approval, send through the CLI's send command. It hard-caps at 20 per day for new accounts and logs every send. If approval covers more than today's remaining 20, send what fits and hold the rest.

Output

  • The drafted queue: each row is target (name, role, company), the under-200-char note with its character count, and the real detail referenced.
  • After approval: a send summary - sent count, remaining in today's 20, and what was held for tomorrow.
  • For people who accept the request, hand the thread to /linkedin-reply-triager and run /linkedin-humanizer on any reply draft.

Rules

  • Nothing sends without the connected CLI/MCP layer AND explicit approval. Draft-first, always.
  • The 20-per-day cap is a ban-safety guardrail for new accounts. Do not exceed it.
  • Every note references one real, specific detail. No generic "I'd love to connect" or "great to connect with people in your space".
  • No em-dashes. No exclamation marks. No fake familiarity.
  • Real numbers are fine, but never name the person or company they came from.

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.