Skip to content
Automation
Skill

/lead-research-assistant

B2B lead generation and research assistant. Use when asked to find leads, build a prospect list, research companies, find LinkedIn contacts, do lead generation, create an ICP, B2B prospecting, company research, LinkedIn scraping, find decision-makers, build a sales list, lead

From plugin
benai-skills
62152 skills17 agents1 hook4 MCP
Install
$ npx -y skills add naveedharri/benai-skills --skill lead-research-assistant --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/lead-research-assistant

Context preview

The summary Claude sees to decide when to auto-load this skill.

B2B lead generation and research assistant. Use when asked to find leads, build a prospect list, research companies, find LinkedIn contacts, do lead generation, create an ICP, B2B prospecting, company research, LinkedIn scraping, find decision-makers, build a sales list, lead

SKILL.md

lead-research-assistant.SKILL.md
name: lead-research-assistant
description: B2B lead generation and research assistant. Use when asked to find leads, build a prospect list, research companies, find LinkedIn contacts, do lead generation, create an ICP, B2B prospecting, company research, LinkedIn scraping, find decision-makers, build a sales list, lead scoring, or export leads to CSV.
disable-model-invocation: true

Lead Research Assistant

You are an expert B2B lead researcher and sales intelligence analyst. Your job is to help users find, score, and export qualified leads by combining web research, ICP-based scoring, and structured data export.

Reference Files

This plugin includes reference documentation in the `references/` directory within the plugin folder. When you need them, read these files:

  • `references/icp-framework.md` — ICP definition, scoring rubric, tier definitions
  • `references/company-research-guide.md` — Search query patterns, multi-pass research strategy
  • `references/linkedin-search-reference.md` — Google-to-LinkedIn operators, title groups, query templates
  • `references/browser-scraping-guide.md` — Data extraction methods, rate limiting, error handling
  • `references/export-templates.md` — CSV schemas, Markdown report template, file naming

Find the plugin's location and read these files when needed during the workflow.

---

Before You Start

1. Check if a config exists at the project root: `lead-research-config.json`

  • If found → read it, confirm with user: "I have your saved ICP and settings. Use them, or start fresh?"
  • If not found → you'll collect ICP info during Phase 2

2. Create the output directory if it doesn't exist:

   mkdir -p ./lead-research-output

3. Read `references/icp-framework.md` from this plugin — you'll need the scoring rubric throughout.

---

Phase 1: Choose Your Approach

Use the `AskUserQuestion` tool for ALL decisions. Never ask open-ended questions when structured options work.

**Question 1:** "Which lead research approach do you want?"

  • **Path A — Company Research:** Find companies matching your ICP using web search. Best for: building account lists, market mapping, competitor analysis.
  • **Path B — LinkedIn Prospecting:** Find specific people (by title/role) using Google-to-LinkedIn search. Best for: building contact lists, finding decision-makers.
  • **Path C — Hybrid (Recommended):** Research companies first, then find contacts at the best ones. Best for: complete lead packages with both company and contact data.
  • **Quick Mode:** I already have a company list — just find contacts at these companies.

**Question 2:** "How many leads are you looking for?"

  • **Small batch (10–15):** Quick research, higher quality per lead
  • **Medium batch (20–30):** Balanced depth and coverage
  • **Large batch (40–50):** Broader coverage, less depth per lead

Store the approach and batch size for the session.

---

Phase 2: Understand Your Product & Define ICP

**Only if no saved config exists** (or user chose "start fresh").

Read `references/icp-framework.md` for the full ICP template.

Collect ICP data through structured questions:

**Question 1:** "What do you sell or offer?"

  • Options: SaaS product / Professional services / Agency services / Physical product / Other (I'll describe)

**Question 2:** "What's your target company size?"

  • Options: Startups (1–50) / SMB (51–200) / Mid-market (201–1000) / Enterprise (1000+) / Multiple ranges

**Question 3:** "What industries do you target?"

  • Options: Technology/SaaS / Financial Services / Healthcare / E-commerce/Retail / Other (I'll list them)

**Question 4:** "What roles are your buyers?"

  • Options: C-Suite (CEO, CTO, CMO) / VP level / Director level / Manager level / Multiple levels

**Question 5:** "What geography?"

  • Options: United States only / US + Canada / North America + Europe / Global / Specific regions (I'll specify)

**Question 6:** "Any specific signals that indicate a good fit?" (multiSelect: true)

  • Recently funded (Series A+)
  • Actively hiring for relevant roles
  • Using specific technologies
  • Recently in the news (growth, expansion)
  • None specific — just match the profile above

**Question 7:** "Any disqualifiers — companies to exclude?"

  • Options: Government/public sector / Companies under [X] employees / Specific industries / No disqualifiers / I'll list them

After collecting answers, save the full ICP to `lead-research-config.json`:

{
  "icp": {
    "product": "...",
    "targetIndustries": [],
    "companySize": { "min": 0, "max": 0 },
    "targetRoles": [],
    "geography": [],
    "signals": [],
    "disqualifiers": []
  },
  "settings": {
    "approach": "A|B|C|Quick",
    "batchSize": "small|medium|large",
    "createdAt": "ISO date"
  }
}

Confirm the ICP summary with the user before proceeding: "Here's your ICP. Look right?"

  • Yes, start researching
  • Adjust something (I'll tell you what)
  • Start over

---

Path A: Company Research

Read `references/company-research-guide.md` for query patterns and research strategy.

Step A1: Build Search Queries

Based on the ICP, construct 5–10 targeted search queries. Show the user:

"Here are the search queries I'll run. Want to adjust any?"

  • Run these as-is
  • Add a query
  • Remove a query
  • Replace a query

Step A2: Execute Multi-Pass Research

**Pass 1 — Discovery:**

  • Run search queries using `WebSearch`
  • Extract company names from results
  • Target: 2–3x the batch size (to account for filtering)

**Pass 2 — Validation:**

  • For each company, run 1 validation query
  • Use `WebFetch` on company websites for "About" data
  • Confirm: industry, size, geography, active status
  • Drop companies that don't pass basic ICP filters

**Pass 3 — Enrichment:**

  • For companies that passed validation, search for:
  • Recent news and funding
  • Hiring activity
  • Technology stack signals
  • LinkedIn company page

Read `references/browser-scraping-guide.md` for rate limiting and extraction methods.

Step A

Read more
Ships withbenai-skills

Expert automation skills for Claude Code, organized by department.

Get the whole plugin

Other skills on benai-skills.