sales-nav-search

Runs paginated LinkedIn Sales Navigator lead searches through the Powerset Search MCP with artifact persistence.

1|1|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/powerset-co/powerpacks --skill sales-nav-search-powerset-co
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sales-nav-search
Source: https://github.com/powerset-co/powerpacks/tree/main/packs/sales-nav/skills/sales-nav-search
Command: npx skills add https://github.com/powerset-co/powerpacks --skill sales-nav-search-powerset-co

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running LinkedIn Sales Navigator searches from a coding agent requires resolving company and title filters to LinkedIn IDs, paginating large result sets, and persisting results across turns. This Skill orchestrates that entire flow through the Powerset Search MCP so leads, mutual connections, and enriched profiles are captured in durable local files and Supabase artifacts. ## Core Features & Use Cases - Filter Resolution: Converts free-text company names and titles into LinkedIn company IDs and canonical title strings via sales_nav_resolve, with structured fallbacks (past-company IDs before keyword search). - Persisted Paginated Search: Runs sales_nav_search with server-side artifact persistence by default, then pages results through get_artifact instead of re-running expensive searches. - Local Handoff & Export: Normalizes MCP responses into leads.jsonl, mutuals.jsonl, and user-facing CSV exports, plus enrichment of visible leads with full profile fields. - Use Case: Ask "find LinkedIn leads in the finance department at Brookfield" and the skill resolves the company, runs a multi-query search plan, enriches the visible leads, resolves mutual LinkedIn URLs, and exports CSVs. ## Quick Start Use the sales-nav-search skill to find LinkedIn leads who work in the finance department at Brookfield and export the results to CSV.

Frequently Asked Questions about sales-nav-search

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a LinkedIn Sales Navigator search from Claude Code or Codex?▼

Invoke the skill with a query like "/sales-nav-search find staff engineers at Stripe". It resolves company and title filters to LinkedIn IDs, runs a paginated sales_nav_search through the Powerset Search MCP, and presents the first page of leads.

How do I paginate Sales Navigator search results?▼

Pagination goes through the get_artifact MCP tool with the artifact_id returned by the initial search, using offset and limit parameters. This avoids re-running the expensive Sales Navigator fetch and keeps filters stable across pages.

What prerequisites does the Powerset Sales Nav search need?▼

It requires the powerset-search MCP registered via the install-powerset-mcp.sh script, which handles Auth0 login and MCP configuration. Every search also needs a set_id, resolved from the user's default set if not specified.

Why did my Sales Navigator search return no results?▼

Zero results usually mean the company filter is too strict. The skill retries with the same organization ID in past_company_ids before falling back to keyword search, and retries filter resolution with parent company name variants.

Can I export Sales Navigator leads to CSV?▼

Yes, the sales_nav_artifacts export command writes leads.csv and mutuals.csv from the local state files. Lead data is first ingested from full artifact content into leads.jsonl and mutuals.jsonl handoff files.

What does reconnect_required mean in a Sales Nav search response?▼

It means the user's Unipile or LinkedIn session needs upstream re-authentication. The skill instructs the agent to tell the user and stop rather than retrying the search.