Sales Navigator Prospecting Claude Skill

The Sales Navigator Prospecting Claude skill builds intent-based saved searches and filter-specific outreach for SDRs and founders who sell on LinkedIn. It is free and open source under the MIT license, from the LeadMagic gtm-skills repo. It follows a playbook credited to Morgan J. Ingram of AMP Social.

LinkedIn Intermediate MIT license 72 GitHub stars
Install
Claude Code plugin
/plugin marketplace add LeadMagic/gtm-skills
Claude Code plugin
/plugin install gtm-skills@gtm-skills
Skills CLI
npx skills add LeadMagic/gtm-skills --skill sales-navigator-prospecting
View on GitHub Checked

What the Sales Navigator Prospecting skill does

Many teams use Sales Navigator as a contact export and paste one script into every message. This skill treats each filter as a signal that deserves its own message. Someone who posted recently, follows your company or just started a new role needs a different opener.

It starts by auditing your current outreach and flagging one-template abuse. Then it defines five saved searches with weekly alerts, one per motion, and pairs each with its own message variant.

For executives who post, it uses a comment first, a wait of a day or two, then a connection request that refers back to the exchange. It also lays out a short daily and weekly rhythm and a plan for coordinating several contacts at one account.

  • Audits your recent LinkedIn outreach for single-template blasts and baseline reply rates
  • Defines five saved searches: active executives, warm to brand, profile viewers, new in role, and buying window
  • Writes at least a dozen message variants, each tied to the filter signal that triggered it
  • Builds an executive routine of insight-plus-question comment, wait, connect, then DM
  • Sets a 15-minute daily and weekly workflow around saved-search alerts
  • Plans different outreach plays for different personas at the same target account
  • Specifies a tracking table so you can compare reply rate by filter
  • Includes a checklist to verify the playbook before your team uses it

How it works

  1. Audit current outreach

    Claude reviews your last 30 days of messages, flags copy reused across unlike filters, and sets a baseline reply rate per variant.

  2. Build saved searches

    It defines one saved search per motion, with weekly alerts, and documents the filter stack, message variant and owner in a table.

  3. Write filter-specific messages

    Each filter gets its own opener, with no pitch in the connection request and one clear question per touch.

  4. Engage executives

    For leads who posted recently, Claude plans a thoughtful comment, a 24 to 48 hour wait, then a connection request and value-first DM.

  5. Set the weekly rhythm

    It schedules triage, comments, connection requests and follow-ups across the week, and a plan for multi-contact accounts.

Example prompts

Once the Sales Navigator Prospecting skill is installed, ask Claude in plain language. These prompts trigger it:

  • Sales Nav is not generating meetings. Audit our approach and build a better playbook for my SDR team
  • Build five saved searches for VPs of marketing at 50 to 200 person SaaS companies
  • Write message variants for people who viewed my profile and for people new in role
  • How should I engage executives who post on LinkedIn before sending a connection request?
  • Create a 15-minute daily Sales Navigator routine for one rep

What you get

  • A Sales Navigator playbook with a current-state audit
  • Five saved-search definitions with filter stacks and alert settings
  • At least twelve filter-specific message variants
  • An executive engagement runbook and a daily and weekly calendar
  • A measurement table for reply rate and meetings by search

Who it is for

  • SDRs and founders running outbound on LinkedIn
  • Sales leaders whose reps send one template to everyone
  • Teams with a Sales Navigator seat that is not producing replies

How to install the Sales Navigator Prospecting skill

What you need: A paid LinkedIn Sales Navigator seat, a defined ICP and a CRM or spreadsheet for tracking. The skill produces the plan and copy, and you run it in LinkedIn. It bundles a small Python checker for the final deliverable.

  1. Claude Code plugin
    /plugin marketplace add LeadMagic/gtm-skills
  2. Claude Code plugin
    /plugin install gtm-skills@gtm-skills
  3. Skills CLI
    npx skills add LeadMagic/gtm-skills --skill sales-navigator-prospecting
  4. Manual
    git clone https://github.com/LeadMagic/gtm-skills.git && cp -r gtm-skills/skills/inbound/sales-navigator-prospecting ~/.claude/skills/

After installing, restart Claude Code or start a new session. Claude loads the Sales Navigator Prospecting skill automatically when your request matches it, or you can ask for it by name.

Tips for better results

  • Tell Claude your ICP titles, company size and geography up front so the saved searches are usable as written.
  • Log the filter used for every message. Reply rate by filter is how you retire weak variants.
  • Fix your profile before scaling outreach, since prospects check it after you connect.

Limitations

  • It cannot run searches or send messages. It plans and writes, and you act inside Sales Navigator.
  • It assumes a paid Sales Navigator seat. The filters it relies on are not available on free LinkedIn.

Sales Navigator Prospecting Claude skill FAQ

Yes. It is open source under the MIT license, from the LeadMagic gtm-skills repo. Sales Navigator itself is a paid LinkedIn product, so you need your own seat.

Run /plugin marketplace add LeadMagic/gtm-skills, then /plugin install gtm-skills@gtm-skills. You can also use the Skills CLI line on this page, or copy the skill folder into ~/.claude/skills/.

The playbook is mostly SKILL.md plus reference files, so it can be zipped and uploaded in Claude.ai under Settings, Capabilities, Skills on paid plans. It also bundles a small Python checker, which only runs where Claude has a terminal, such as Claude Code.

Create a saved search per intent signal, such as posted recently or new in role, turn on weekly alerts, and write a separate message for each. This skill builds that setup and the supporting routine.

The skill says no. It recommends a comment that adds an insight and asks a question, then waiting 24 to 48 hours before a connection request that references the exchange.