Agent skill

Linkedin Outreach

by ericrisco in ericrisco/rsc-harness

A skill your agent uses when running LinkedIn social selling as a repeatable motion — Sales Navigator saved searches and trigger alerts, weekly request budgets, fixing a low acceptance rate, turning…

MITAuto-check passedSales & Support

Install Linkedin Outreach

skills CLI
$ npx skills add ericrisco/rsc-harness --skill linkedin-outreach -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ericrisco/rsc-harness linkedin-outreach --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ericrisco/rsc-harness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/linkedin-outreach .claude/skills/linkedin-outreach && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
linkedin-outreach
GitHub stars
174
Token cost
~2.8k tokens
SKILL.md length
1,477 words
Files
6 (incl. scripts, references)
Skills in repo
233
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when running LinkedIn social selling as a repeatable motion — Sales Navigator saved searches and trigger alerts, weekly request budgets, fixing a low acceptance rate, turning…

  • Works in 5 steps: Target — why: outreach timed to a reason… → Warm — why: a cold, context-free request… → Connect — why: the request is the… → …
  • Running LinkedIn social selling as a repeatable motion — Sales Navigator saved searches and trigger alerts
  • SKILL.md covers Boundary, The loop, Target with Sales Navigator and The connection motion, plus 5 more sections
  • Runs Shell scripts from its folder

What it does

Linkedin Outreach is an agent skill from ericrisco/rsc-harness. Use when running LinkedIn social selling as a repeatable motion — Sales Navigator saved searches and trigger alerts, weekly request budgets, fixing a low acceptance rate, turning profile views and post engagers into warm threads, logging every touch. NOT the note or DM copy (that is cold-outreach), NOT the deal after a reply (that is sales-pipeline).

Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including scripts and reference files (for example `evals/README.md`, `evals/cases.yaml` and `references/ledger-schema.md`).

It sits in Sales & Support, covering Cold outreach and CRM management. It works with LinkedIn. The repository describes itself as: Your agent invents things because it has no memory, and can't touch your database because it has no arms. rsc is the meta-harness that gives it both, plus the trade to know the… The licence is MIT.

When your agent uses it

  • Running LinkedIn social selling as a repeatable motion — Sales Navigator saved searches and trigger alerts
  • Weekly request budgets
  • Fixing a low acceptance rate
  • Turning profile views and post engagers into warm threads

Example prompts

  • “/linkedin-outreach”

Requirements

  • A Bash shell

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Target — why: outreach timed to a reason beats outreach timed to a calendar. → Yields a Sales Nav saved search + trigger alerts (job…
  2. Warm — why: a cold, context-free request is the worst-accepting move you can make; engaging first is what fixes it. → Yields a logged…
  3. Connect — why: the request is the smallest, most rate-limited move; spend it deliberately. → Yields a sent request inside the weekly…
  4. Convert — why: an accept is not a conversation; the choreography turns a signal into a warm 1:1. → Yields a thread with a real reply, copy…
  5. Log — why: a motion you can't measure you can't repeat or fix. → Yields a row in the 02-DOCS/ ledger with the outcome.

What it can do on your machine

Read from SKILL.md and the folder at commit e3d5b33. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Shell), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Linkedin Outreach loads about 2.8k tokens when it runs, and up to ~4.4k if it reads all its reference files. Until then it costs about 94 tokens; SKILL.md has 1,477 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~94
When it runs · the whole SKILL.md, loaded when a task matches
~2.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from ericrisco/rsc-harness at commit e3d5b33, republished under its MIT licence (© ericrisco). 1,477 words, ~2,799 tokens.

Download SKILL.mdSave it as .claude/skills/linkedin-outreach/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
linkedin-outreach
description
Use when running LinkedIn social selling as a repeatable motion — Sales Navigator saved searches and trigger alerts, weekly request budgets, fixing a low acceptance rate, turning profile views and post engagers into warm threads, logging every touch. NOT the note or DM copy (that is `cold-outreach`), NOT the deal after a reply (that is `sales-pipeline`).
tags
linkedin, social-selling, sales-navigator, outreach, pipeline
recommends
cold-outreach, lead-gen, sales-pipeline, linkedin-strategy, linkedin-content
origin
risco

Linkedin Outreach — The Loop and Its Ledger

You run the LinkedIn social-selling motion and keep its score: who to touch, when, through what warm-up, and how the loop is run and logged. The thesis is warm-first — engagement before connection, signal before send, ledger before "I'll remember it." The output is a running system plus a touch ledger under 02-DOCS/, never a finished line of copy: when prose is needed you write the brief and hand it off, then stay in the loop.

Boundary

The sharpest line is against ../cold-outreach/SKILL.md, and it splits on message-vs-system:

  • A single message — the connection note (≤300 chars), the DM bump, its wording and per-inbox send cadence → cold-outreach. If the ask is "write this" or "fix this template," it is not yours.
  • The system — who to touch, when, the warm-up, the budget, the ledger → here. When both are in play, this skill drives and delegates the copy.

Also not yours: sourcing / scoring the raw prospect list and ICP definition → ../lead-gen/SKILL.md; the deal after a reply, i.e. stages, forecast, CRM tasks → ../sales-pipeline/SKILL.md; writing or scheduling LinkedIn posts → ../linkedin-content/SKILL.md; brand growth and positioning → ../linkedin-strategy/SKILL.md.

The loop

Five phases, in order. Each has a why and yields one artifact; the artifact gates the next phase. Skipping a phase is how acceptance collapses.

  1. Target — why: outreach timed to a reason beats outreach timed to a calendar. → Yields a Sales Nav saved search + trigger alerts (job change, funding, recent post).
  2. Warm — why: a cold, context-free request is the worst-accepting move you can make; engaging first is what fixes it. → Yields a logged pre-touch (profile view + one genuine comment/like 1–2 days prior).
  3. Connect — why: the request is the smallest, most rate-limited move; spend it deliberately. → Yields a sent request inside the weekly budget, note-or-no-note chosen by goal.
  4. Convert — why: an accept is not a conversation; the choreography turns a signal into a warm 1:1. → Yields a thread with a real reply, copy delegated to cold-outreach when needed.
  5. Log — why: a motion you can't measure you can't repeat or fix. → Yields a row in the 02-DOCS/ ledger with the outcome.

Each phase gets a section below; the last one compresses all five into a day.

Target with Sales Navigator

Build the saved search from the ICP, not from a name list:

  • Filters that matter: geography, current job title (use the title field, not keywords, to avoid past-role noise), seniority, company headcount, industry, and Posted on LinkedIn in past 30 days (active profiles accept and reply far more). Save it; Sales Nav re-runs it and surfaces new matches.
  • Trigger alerts worth turning on: changed jobs in last 90 days (new role = new budget, new pain), company funding events, and posted recently (a fresh post is your warm-up hook). Time the request to a trigger, never to a Tuesday.
  • InMail reality: Core and Advanced both ship 50 InMail credits/mo, rolling over up to 3 months (max 150 accumulated); an InMail that gets a reply within 90 days is credited back. Spend InMail on out-of-network leads where a connection request can't reach — not on people you could warm up and connect to for free.

Free vs Core vs Advanced — buy on the job, not the brand:

You needTier2025 priceWhy
Run the loop on a tight ICP, manual budgetFree$0Works if you stay disciplined; no saved-search alerts.
Saved searches, 40+ filters, lead/account alerts, 50 InMail/moCore$119.99/mo ($1,079.88/yr)The default for a working social seller.
+ TeamLink, Smart Links, buyer-intent, Account/Lead IQ, CRM syncAdvanced$159.99/mo ($1,799.88/yr)Only when a team or CRM sync is real.

Filter recipes per ICP, trigger-alert setup, and the full Core-vs-Advanced buy math → references/sales-navigator-playbook.md.

The connection motion

Engagement-before-connect ritual. 1–2 days before the request: view the profile, follow the company page, and drop one genuine comment or like on a recent post. This is what moves acceptance from ~20–30% (cold) to ~60%+. Log the pre-touch — it is phase 2, not optional flavor.

Note or no note — read the paradox correctly. A personalized note barely moves acceptance (26.42% with vs 26.37% without; some 2025/26 datasets show no-note accepting higher). But a note with real context nearly doubles the post-accept reply rate (9.36% vs 5.44%). So decide by goal:

Your goalNote?Why
Maximize the accept (build network, retarget later)No note (or near-empty)Notes don't lift acceptance; an empty request often accepts as well or better.
Maximize the reply after acceptShort context noteReal context roughly doubles reply; worth the friction only when you have a true hook.
No genuine hook existsNo noteA generic note is worse than none — it reads as a pitch.

When you do send a note, you do not write it here — hand the brief (the hook, the person, the goal) to ../cold-outreach/SKILL.md.

Weekly request budget — the cap is a rolling weekly limit, not a daily reset.

AccountRealistic weekly capDaily targetHealth rule
Free~100/wk~20/weekday, stay under ~80/wkPause and warm more if acceptance drops below ~30%.
Premium / Sales Navup to ~200/wkup to ~40/dayOnly with strong SSI and acceptance >40%; otherwise treat as free.

Over the cap, requests get throttled or the account flagged. Below ~30% acceptance you are spraying — go back to phase 2 instead of pushing volume, and withdraw stale pending requests before they pile up.

Show full SKILL.md (590 more words)Show less

Engagement → conversation

A signal is an opening. Match the signal to a play; the play is choreography (timing, sequence, what to reference), never finished prose.

SignalPlayCopy?
Connection just acceptedWait, don't pitch. Reference why you reached out (their post/role/trigger), ask one genuine question.Brief → cold-outreach
Profile viewer (they viewed you)Soft, warm reply: "Saw you stopped by — noticed [their thing], curious how you handle X?"Brief → cold-outreach
Post engager (liked/commented your post)Thank or build on their comment, then DM a related question tied to their work.Brief → cold-outreach
Comment thread (they engaged a third party's post)Add value in-thread first, connect with that context the next day.Brief → cold-outreach

Worked example — the move, not the words:

text
Bad  (pitch-on-accept):
  Accepted → "Thanks for connecting! We help teams like yours cut reporting
  time 40% with our analytics platform — open to a 15-min demo Thursday?"
  Reads as a trap; reply rate craters.

Good (reference-then-ask):
  Accepted → "Appreciate the connect — your post on attribution gaps in
  ecommerce hit home. How are you splitting paid vs organic credit right now?"
  Opens a real thread; the product never comes up until they ask.

Hand off to pipeline

You run the loop up to a warm intro or a booked call — then you stop and hand off.

Buying-signal tells in a thread: they ask about price/timeline, mention an active project or pain, reference budget or a decision date, or say "send me more." When you see one:

  1. Book the call or send the warm intro.
  2. Log the outcome (call_booked) in the ledger.
  3. Hand the thread + context to ../sales-pipeline/SKILL.md — the moment a deal exists it is theirs, and you set no stages or forecasts.

The ledger (02-DOCS)

One file. Path: 02-DOCS/linkedin-outreach/touches.csv. The header row is fixed (verify.sh checks it verbatim):

csv
date,name,profile_url,channel,trigger,action,stage,outcome,next_touch
  • channel: connect | inmail | dm | comment | view.
  • outcome (enum, no blanks): requested | accepted | replied | conversation | call_booked | dead.
  • Never leave a literal merge token ({first_name}, [company], XXXX, TODO) in a cell — verify.sh fails on it.

Full column spec, the outcome enum, a filled 5-row example, and the weekly-review formulas → references/ledger-schema.md.

Weekly review ritual (15 min, same day each week). Compute from the ledger:

  • Acceptance % = accepted ÷ requested.
  • Post-accept reply % = replied ÷ accepted.
  • Conversations → calls % = call_booked ÷ conversation.
  • Touches/week = rows added this week (is the loop actually running?).

If acceptance < ~30%, warm harder (phase 2). If reply < ~10%, your hooks are weak (better brief to cold-outreach). If touches/week is near zero, the loop stopped — that's the real failure.

Anti-patterns

BadWhy it bitesDo instead
Spray connection requests over the capRolling weekly limit; throttled or account-flaggedStay under ~80/wk free, ~200 Premium with >40% accept
Pitch the instant a connection acceptsReads as a trap; reply rate cratersReference their context, ask one real question first
Automation that ignores the rolling limitBursts trip LinkedIn's detection; account at riskPace within the budget; warm-up beats volume
Read "notes don't help" as "context never helps"Notes don't lift accept, but context doubles replyDecide note by goal: accept→none, reply→context
Chase SSI as the goalSSI is a lagging proxy; high SSI ≠ pipelineTrack acceptance/reply/calls; let SSI follow
Run outreach with no ledgerNo measurement → no repeatable motionLog every touch + outcome to 02-DOCS/

Daily 30-minute routine

Run this as a checklist; it is the loop compressed into a day.

  • Engage (10 min): comment genuinely on 5–8 posts from your saved search and from people you plan to connect with this week (phase 2 warm-up bank).
  • Connect (5 min): send today's requests from the saved search / trigger alerts, inside the weekly budget; note-or-no-note by goal (phase 3).
  • Convert (10 min): progress 2–3 warm threads — accepted connections, profile viewers, post engagers — using the signal→play table; delegate any copy to cold-outreach.
  • Hand off (2 min): any buying signal → book/intro, then route to sales-pipeline.
  • Log (3 min): write every touch and outcome to 02-DOCS/linkedin-outreach/touches.csv.

Weekly, run the review ritual and adjust the next week's targeting. That closes the loop back to phase 1.

© ericrisco, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (scripts, references) in skills/linkedin-outreach of ericrisco/rsc-harness.

  • SKILL.md
  • evals/README.md
  • evals/cases.yaml
  • references/ledger-schema.md
  • references/sales-navigator-playbook.md
  • scripts/verify.sh

Open the folder on GitHubat commit e3d5b33

Compare with similar skills

Linkedin Outreach next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Linkedin Outreach compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Linkedin Outreach this skillericrisco/rsc-harness174—~2.8kAutomated safety check: PassMIT
B2B Lead Generationminhnv0807/ai-business-skills610—~1.2kAutomated safety check: PassMIT
Prospectingcoreyhaines31/marketingskills54k—~5kAutomated safety check: PassMIT
Sales OsromangojiberryAI/gojiberryai-sales-os139—~2kAutomated safety check: PassMIT
Cold Outreach Personalizeraiskilloftheweek/claude-ai-skill-of-the-week148—~2.6kAutomated safety check: PassNone
Cold Emailcoreyhaines31/marketingskills54k—~3.1kAutomated safety check: PassMIT

Similar skills

  • B2B Lead Generation

    minhnv0807/ai-business-skills

    Plans B2B pipeline work from ICP definition and prospecting through lead scoring, outbound sequences, sales assets and MQL to SQL handoff, aiming at qualified pipeline.

    610 GitHub stars~1.2k tokensUpdated 27 days ago
    Sales & SupportAuto-check passed
  • Prospecting

    coreyhaines31/marketingskills

    When the user wants to find, qualify, and build a list of prospects to reach out to, across B2B SaaS, general B2B, or local small businesses.

    54k GitHub stars~5k tokensUpdated today
    Sales & SupportAuto-check passed
  • Sales Os

    romangojiberryAI/gojiberryai-sales-os

    A complete outbound sales department in one skill. An agent skill from romangojiberryAI/gojiberryai-sales-os.

    139 GitHub stars~2k tokensUpdated 1 mo ago
    Sales & SupportAuto-check passed
  • Cold Outreach Personalizer

    aiskilloftheweek/claude-ai-skill-of-the-week

    Generates hyper-personalized cold outreach messages (email, LinkedIn DM, connection request) from raw prospect research.

    148 GitHub stars~2.6k tokensUpdated 4 mo ago
    Sales & SupportAuto-check passed
  • Cold Email

    coreyhaines31/marketingskills

    Write and run B2B cold outbound that gets replies, from cold emails and follow-ups to sending setup, LinkedIn, multichannel cadences, and reply handling.

    54k GitHub stars~3.1k tokensUpdated today
    Sales & SupportAuto-check passed
  • Cold Outreach Sequence Builder

    BrianRWagner/ai-marketing-claude-code-skills

    Builds researched LinkedIn and email outreach for prospects, from a single message to a multi-prospect system, with personalization graded by the signals found.

    440 GitHub stars~1.9k tokensUpdated 6 mo ago
    Sales & SupportAuto-check passed

More from ericrisco/rsc-harness

All 233 skills in this repo
  • Ab Testing

    ericrisco/rsc-harness

    A skill your agent uses when designing or analyzing a controlled experiment — falsifiable hypothesis, sample size from an MDE, reading significance/CI/power, CUPED, or rescuing tests that won't go…

    174 GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed
  • Accessibility

    ericrisco/rsc-harness

    A skill your agent uses when making a web UI conform to WCAG 2.2 Level AA — axe-core or Lighthouse a11y violations, keyboard operability, focus management, ARIA roles/names/live regions, contrast…

    174 GitHub stars~3.4k tokensUpdated yesterday
    Auto-check passed
  • Ads

    ericrisco/rsc-harness

    A skill your agent uses when running or fixing paid acquisition on Google or Meta — campaign structure (Performance Max, Demand Gen, Search, Advantage+), platform-fit creative, budget/scaling rules…

    174 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check passed
  • Agent Eval

    ericrisco/rsc-harness

    A skill your agent uses when measuring whether an LLM or agent system actually got better and gating merges on it: golden sets, fixing an inflated LLM-as-judge, scoring RAG (faithfulness, contextual…

    174 GitHub stars~3.2k tokensUpdated yesterday
    Auto-check passed
  • AI Media

    ericrisco/rsc-harness

    A skill your agent uses when a creative goal must become a finished media file: pick and order generative-media models per modality — AI voiceover, image-to-video clips, score — then glue them with…

    174 GitHub stars~3.3k tokensUpdated yesterday
    Auto-check passed
  • Analytics

    ericrisco/rsc-harness

    A skill your agent uses when instrumenting product or web analytics — GA4/PostHog SDK wiring, event taxonomy, funnels, double-counted events, consent gating, PII scrubbing.

    174 GitHub stars~2.8k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Linkedin Outreach

What does Linkedin Outreach do?

A skill your agent uses when running LinkedIn social selling as a repeatable motion — Sales Navigator saved searches and trigger alerts, weekly request budgets, fixing a low acceptance rate, turning…. Linkedin Outreach is an agent skill from ericrisco/rsc-harness. Use when running LinkedIn social selling as a repeatable motion — Sales Navigator saved searches and trigger alerts, weekly request budgets, fixing a low acceptance rate, turning profile views and post engagers into warm threads, logging every touch.

When should I use Linkedin Outreach?

Linkedin Outreach fits situations like: running LinkedIn social selling as a repeatable motion — Sales Navigator saved searches and trigger alerts; weekly request budgets; fixing a low acceptance rate; turning profile views and post engagers into warm threads.

How do I install Linkedin Outreach in Claude Code?

Run `npx skills add ericrisco/rsc-harness --skill linkedin-outreach -a claude-code`. Or copy the skill folder (skills/linkedin-outreach in ericrisco/rsc-harness) into .claude/skills/linkedin-outreach in your project. Claude Code loads it when a task matches its description.

How do I install Linkedin Outreach in Codex?

Run `npx skills add ericrisco/rsc-harness --skill linkedin-outreach -a codex`. Or copy the skill folder (skills/linkedin-outreach in ericrisco/rsc-harness) into .agents/skills/linkedin-outreach in your project. Codex loads it when a task matches its description.

Can I use Linkedin Outreach in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ericrisco/rsc-harness --skill linkedin-outreach -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/linkedin-outreach, .gemini/skills/linkedin-outreach, .github/skills/linkedin-outreach and .opencode/skills/linkedin-outreach in your project.

What does Linkedin Outreach need to run?

Going by SKILL.md and its folder, Linkedin Outreach needs a shell for the scripts in its folder. Our summary lists: A Bash shell.

Does Linkedin Outreach access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Linkedin Outreach safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Linkedin Outreach use?

Linkedin Outreach is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Linkedin Outreach use?

About 2.8k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.6k tokens, read only when the agent opens those files.

What are the alternatives to Linkedin Outreach?

Skills that share tags, products or a category with Linkedin Outreach: B2B Lead Generation (minhnv0807/ai-business-skills, 610 stars), Prospecting (coreyhaines31/marketingskills, 54k stars), Sales Os (romangojiberryAI/gojiberryai-sales-os, 139 stars) and Cold Outreach Personalizer (aiskilloftheweek/claude-ai-skill-of-the-week, 148 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Linkedin Outreach?

ericrisco (a GitHub user) maintains it in ericrisco/rsc-harness, which has 174 GitHub stars. The repository holds 233 skills in this directory. The repository was last updated on October 7, 2026.

Source: ericrisco/rsc-harness on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.