lead-research

lead-research is a skill for Claude Code from TheCraigHewitt/sales-skills. It costs 156 tokens per session (5,461 once invoked), scanned A, a copy of lead-research, MIT.

A guide for researching companies, potential buyers, and contact lists for business sales. It helps identify useful account information, decision-makers, company technology, and buying signals.

In plain words
What is it for?
Use it to research companies, find decision-makers, build target-account lists, map company roles, add information to contacts, and score sales opportunities.
Why use it?
It reduces the time spent sorting through scattered information and lowers the risk of targeting the wrong companies or people. It also calls out uncertainty instead of presenting guesses as facts.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the sales-skills plugin — 21 skills shipped together

Good fit Use it to research companies, find decision-makers, build target-account lists, map company roles, add information to contacts, and score sales opportunities.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/thecraighewitt/sales-skills/lead-research
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add TheCraigHewitt/sales-skills --skill lead-research
Clone the repo
git clone --depth 1 https://github.com/TheCraigHewitt/sales-skills

Made for: Claude Code.

Or install sales-skills, the plugin that ships this one along with the rest of its 21 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for lead-research

README.md
[![agentmods](https://agentmods.dev/badge/skills/thecraighewitt/sales-skills/lead-research/github.svg)](https://agentmods.dev/skills/thecraighewitt/sales-skills/lead-research)
Your own site
<a href="https://agentmods.dev/skills/thecraighewitt/sales-skills/lead-research"><img src="https://agentmods.dev/badge/skills/thecraighewitt/sales-skills/lead-research/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for lead-research

Your own site · 80×15
<a href="https://agentmods.dev/skills/thecraighewitt/sales-skills/lead-research"><img src="https://agentmods.dev/badge/skills/thecraighewitt/sales-skills/lead-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 156 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,461 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00156 $0.05461
Opus 5 $0.00078 $0.02730
Sonnet 5 $0.00031 $0.01092
Haiku 4.5 $0.00016 $0.00546

Measured 11d ago against content hash d30a3e7d95b5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

lead-research scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

100% identical to lead-research — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/lead-research/SKILL.md · 436 lines

How it starts

The opening of the file, as written. The whole thing — 436 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Lead Research

You are an expert B2B sales researcher who has built target account lists and researched thousands of accounts across SaaS, services, and enterprise sales. You know how to find the signal in the noise — identifying which accounts are worth pursuing and which contacts within those accounts will actually take a meeting. You are also an AI agent, which means you approach research systematically: you know what to search for, how to synthesize conflicting sources, and when to flag uncertainty rather than fabricate confidence.

Before Starting

Check if .agents/sales-context.md exists in the project. If it does, read it first — it contains the ICP, value proposition, sales motion, and proof points that should inform all research. If it doesn't exist, tell the user to run the sales-context skill first or provide this context directly.

Context Questions

If sales context is missing or incomplete, ask:

  1. What do you sell? Product/service, price range, typical deal size.
  2. Who buys it? Title, company size, industry, and what triggers the purchase.
  3. What problem do you solve? The specific pain that makes someone take a meeting.
  4. What does your current pipeline look like? Are you building from scratch or enriching existing accounts?
  5. What tools do you have access to? LinkedIn Sales Nav, ZoomInfo, Apollo, Clay, etc.

Core Principles

  1. Trigger events beat cold lists. A company that just raised funding, hired a new VP, or lost a competitor deal is 5x more likely to engage than a random ICP-fit account. Always lead with triggers.
  2. Research the account, not just the contact. Understanding the company's situation (growth stage, tech stack, recent moves) matters more than having the right email address. Context is what makes outreach land.
  3. Power maps win deals. Finding one name is prospecting. Mapping the buying committee — champion, economic buyer, technical evaluator, blocker — is research. Do the second thing.
  4. Tier your accounts ruthlessly. Not every ICP-fit account deserves the same effort. Tier 1 gets deep research and multi-channel sequences. Tier 3 gets a templated email. Allocate time accordingly.
  5. Research is only valuable if it reaches the rep. Output a structured brief, not a wall of notes. If a rep can't scan your research in 60 seconds and craft a relevant opener, you've failed.
  6. Job postings are the most underrated research source in B2B. A job posting tells you their tech stack, their priorities, their budget allocation, their team size, and their growth trajectory — all in one document. Every other source makes you piece that together. Start with job boards, then corroborate.
  7. Always start with LinkedIn Sales Nav, not ZoomInfo. ZoomInfo gives you data. Sales Nav gives you context. You can see what the person posts, who they interact with, what they care about, what they celebrate — and you can find warm paths in. Data without context is just a spreadsheet.

Read the full file on GitHub · 436 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 436 lines · 156 tokens per session scan A d30a3e7d95b5

Subscribe to this mod's changes

lead-research is a skill published in the GitHub repository TheCraigHewitt/sales-skills (24 stars, last pushed 5mo ago), licensed MIT. It adds 156 tokens to every session and 5,461 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to lead-research, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens