Resources / Sales Nav Search Builder
Live Sales Navigator Lead lists

Any target description, into a paste-safe Sales Nav URL.

Drop a call transcript, a Slack brief, a one-line request, or a rough ICP. The skill extracts targeting signals, maps them to structured Sales Nav filters, and emits a single paste-safe URL plus a readable breakdown. Opinionated about keyword discipline.

Download skill Install instructions
v1.0 Outputs Sales Nav URL Works with Apify, Linked Helper Structured filters first
SS
salesnav-search-builder.zip
19.0 KB · Bundle: .skill file + SKILL.md inside · v1.0
Download skill
Want to read what it does first? View source ↓
What it does

The hard part is not the URL.

URL encoding for Sales Nav is solved. The hard part is fidelity: extracting what the input actually says, knowing when to ask instead of guess, and refusing to fabricate filters the input never established.

The skill accepts every input shape: a meeting transcript, a one-line NL request, a pasted Slack note, a rough ICP doc, or a customer profile. It normalizes each into the same internal signal set, then runs them through the same pipeline. No silent defaults, no padded filters.

Strongest opinion in the skill: the Boolean keywords field is a last resort, not a primary tool. Most "narrow Sales Nav searches" come from keyword stuffing that structured filters could handle better with higher recall. The skill enforces this on every search it builds.

Try saying

Any of these will work.

Turn this call transcript into a Sales Nav search URL.
VP engineering at fintechs in the US, 100 to 500 people. Build the search.
Heads of sales at B2B SaaS, Series B to C. Paste-safe URL please.
Who should we target? Here's my brief...
How it works

Five steps. Asks before assuming.

01

Detect the input

Transcript, brief, NL one-liner, ICP, mixed. Each gets a different reading style, but all normalize into the same internal signals.

02

Extract anchored signals

Pulls every targeting signal actually present, tied to a quote. No anchor means the category is absent, not filled with a default.

03

Map and flag

Direct, inferred, ask, unresolvable. Persona or title with no basis in the input is always an ASK. No safe default for who to target.

04

Apply keyword discipline

Structured filters first. Keywords field is a last resort, capped at 2 terms. The skill asks before stuffing concepts into keywords that have a structural alternative.

05

Emit URL + breakdown

Paste-safe URL plus a readable breakdown with confidence tags per filter. Seat-gated filters flagged. Session params stripped.

Why it doesn't lie to you

Built around the things that usually go wrong.

!

Keywords are a last resort

Most narrow Sales Nav searches come from keyword stuffing. The skill defaults to structured filters and caps keywords at 2 terms even when they're justified.

@

Persona is always an ASK

If the input doesn't establish who to target, the skill stops and asks. There is no safe default for persona. "Just build it" instructions don't override this.

?

Seniority IDs verified live

Sales Nav renumbers seniority IDs periodically. The old 1 to 10 scale silently drops chips. The skill uses confirmed-live 3-digit IDs and recommends paste-testing.

×

Seat-gating surfaced

Spotlights (Posted on LinkedIn, etc.) are Advanced or Advanced Plus only. They silently drop on Core seats. Every search that uses one flags the seat tier explicitly.

The output

A paste-safe URL plus a readable breakdown.

The URL is one line, stripped of session params, ready to paste into Sales Nav or feed into Apify or Linked Helper. The breakdown is for your eyes only: confidence tags per filter, seat-gating notes, and an explicit list of what was not applied and why.

Sample output
ENCODED URL (paste-safe): https://www.linkedin.com/sales/search/people?query=(...) READABLE BREAKDOWN: - CURRENT_TITLE: sales [DIRECT] - SENIORITY_LEVEL: 220,300 [INFERRED] - INDUSTRY: Software Dev [DIRECT] - COMPANY_HEADCOUNT: D, E [DIRECT] - keywords: (empty) [DEFAULT] SEAT NOTES: none (Core-compatible)
Search contract
Output
Sales Nav URL + breakdown
Compatible
Apify, Linked Helper
Filter source
url-encoding-v5
Keyword cap
2 terms (when justified)
Persona missing
Always ASK
Seat tiers
Core, Advanced, Advanced+
Install

Pick your Claude. Drop in the skill.

The download is a zip containing two things: the .skill file (what you upload to Claude) and a SKILL.md sidecar (the human-readable instructions). Unzip first, then follow the steps for your Claude.

⌘
Most people

Claude.ai or Desktop

  1. Download and unzip the bundle.
  2. Open or create a Project in Claude.
  3. Go to Project knowledge, click Add content.
  4. Upload the .skill file from the unzipped bundle.
  5. Start a new chat in that project. Ask it to run the skill.
Download bundle ↓ No restart needed
›_
Developers

Claude Code

  1. Download and unzip the bundle.
  2. Unzip the inner .skill file too (it's also a zip).
  3. Move the resulting folder into ~/.claude/skills/
  4. Restart Claude Code.
  5. Type a prompt that fits the trigger. The skill loads automatically.
Download bundle ↓ macOS / Linux / WSL
{ }
Builders

API or Agent SDK

  1. Download and unzip the bundle.
  2. Open the SKILL.md sidecar to read the full instructions.
  3. Load via the Skills API, or paste the instructions into your agent's system prompt.
  4. Make sure your agent has web_search and file output enabled.
  5. Ship it.
View SKILL.md ↓ v1.0
Source

Read the full instructions.

This is exactly what Claude reads when the skill triggers. No hidden prompts, no separate config. What you see here is what you get.

MD
salesnav-search-builder-SKILL.md 12.7 KB · the full skill instructions
⌄
Loading SKILL.md...

Need help implementing this on your team?

We'll install the skills, customize them to your workflow, and run the output through your team's combined LinkedIn network. Skills do the research, Linkd does the motion.

Book a demo