Agent skill

Lead Research

by TheCraigHewitt in TheCraigHewitt/skills

When the user wants to research accounts, contacts, or build target lists.

MITAuto-check passedSales & Support

Install Lead Research

skills CLI
$ npx skills add TheCraigHewitt/skills --skill lead-research -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install TheCraigHewitt/skills lead-research --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/sales/lead-research .claude/skills/lead-research && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
lead-research
GitHub stars
159
Token cost
~5.9k tokens
SKILL.md length
2,627 words
Files
1
Skills in repo
65
Repo updated
First seen
Licence
MIT

At a glance

When the user wants to research accounts, contacts, or build target lists.

  • Works in 5 steps: Trigger Event Discovery → Initial Qualification → Org Chart Mapping → …
  • Wants to research accounts
  • SKILL.md covers Before Starting, Context Questions, Core Principles and When to Stop Researching, plus 8 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Lead Research is an agent skill from TheCraigHewitt/skills. When the user wants to research accounts, contacts, or build target lists. Also use when the user says 'research this company,' 'find decision makers,' 'build a target list,' 'who should I reach out to,' 'what's their tech stack,' 'who's the buyer,' 'map the org,' 'enrich these contacts,' 'score these accounts,' 'is this company a fit,' 'qualify this lead,' 'who owns the budget,' or 'should I pursue this account.' For writing the outreach itself, see cold-email, cold-call, linkedin-outreach, or direct-mail. For…

Its SKILL.md is about 5.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Sales & Support, covering Cold outreach and Lead generation. It works with LinkedIn. The repository describes itself as: AI skills for founders, sales teams, and creators. 47 skills across CEO, Sales, YouTube, and General categories. Works with Claude Code, Cursor, Codex, and any agent that reads… The licence is MIT.

When your agent uses it

  • Wants to research accounts
  • Build target lists
  • The user says research this company
  • Find decision makers

Example prompts

  • “research this company,”
  • “find decision makers,”
  • “build a target list,”
  • “/lead-research”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Trigger Event Discovery
  2. Initial Qualification
  3. Org Chart Mapping
  4. Tech Stack Confirmation
  5. Completed Research Brief

What it can do on your machine

Read from SKILL.md and the folder at commit fdbf39b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Lead Research loads about 5.9k tokens when it runs. Until then it costs about 171 tokens; SKILL.md has 2,627 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~171
When it runs · the whole SKILL.md, loaded when a task matches
~5.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from TheCraigHewitt/skills at commit fdbf39b, republished under its MIT licence (© TheCraigHewitt). 2,627 words, ~5,938 tokens.

Download SKILL.mdSave it as .claude/skills/lead-research/SKILL.md (or your agent's skills folder).
name
lead-research
description
When the user wants to research accounts, contacts, or build target lists. Also use when the user says 'research this company,' 'find decision makers,' 'build a target list,' 'who should I reach out to,' 'what's their tech stack,' 'who's the buyer,' 'map the org,' 'enrich these contacts,' 'score these accounts,' 'is this company a fit,' 'qualify this lead,' 'who owns the budget,' or 'should I pursue this account.' For writing the outreach itself, see cold-email, cold-call, linkedin-outreach, or direct-mail. For sequencing across channels, see outbound-sequence. For deeper persona work, see buyer-persona. For competitor-specific research, see competitive-intel.
metadata.version
1.0.0

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.

When to Stop Researching

The biggest research mistake in B2B is spending 2 hours on a Tier 3 account. Research time must match account value.

TierMax Research TimeWhat You Should Have
Tier 115-20 minutesFull account brief, power map, 2-3 warm paths, trigger context
Tier 25-7 minutesCompany snapshot, primary contact, one relevant trigger
Tier 30-2 minutesVerified contact info, confirmed ICP fit, template variables filled

Stop signals — you have enough:

  • You can write a specific, relevant opening line. That's the bar. If you can write the opener, stop researching and start reaching out.
  • You've identified the trigger and the buyer. Everything else is incremental.
  • You've checked three sources and they agree. Don't go to five for confirmation.

Stop signals — you'll never have enough:

  • The company is too small for public information. Don't spiral. Use what you have.
  • You're reading the CEO's college blog from 2012. You've gone too deep. Come back up.

Research Decay

Research goes stale. A Tier 1 account brief is a snapshot, not a permanent document.

Data TypeShelf LifeRe-Research Trigger
Contact info (email, phone, title)3-6 monthsBefore any re-engagement after 90+ days
Org chart / power map3-6 monthsAny leadership change signal
Trigger events2-4 weeksNew outreach cycle starts
Tech stack6-12 monthsNew job postings or product announcements
Company financialsQuarterlyEarnings, funding, or M&A news

Rule of thumb: If you're re-engaging a Tier 1 account after 90+ days of silence, re-research the whole brief. People change roles, priorities shift, new competitors enter. The account you researched in January is a different account in June.

Disqualification Criteria

Knowing when NOT to pursue is as valuable as knowing when to pursue. Walk away from these:

Hard Disqualifiers (Stop Immediately)
  • Signed a competitor contract in the last 6 months. They're locked in. Come back in 18 months when renewal approaches.
  • Active RFP or vendor selection that's past shortlist stage. You're too late. Note the timeline and come back next cycle.
  • Company is in active M&A (being acquired). All purchasing decisions freeze during acquisition. Nobody is buying anything new.
  • Budget frozen or company-wide hiring freeze. Unless you solve a problem that saves money RIGHT NOW, you'll waste cycles.
  • Contact explicitly said "never contact us again." Respect it. Permanently. This is non-negotiable.
Soft Disqualifiers (Deprioritize, Don't Pursue Now)
  • No trigger event and no intent signal. They might be ICP-fit on paper, but without timing, you're pushing rope. Move to nurture.
  • Your champion just left. Re-research who replaced them and what the new person's priorities are before re-engaging.
  • They just completed a major project in your category. They won't rip and replace for 12-18 months. Set a reminder.
  • The company is shrinking (revenue down, layoffs, office closures). Unless you solve a cost-reduction problem, deprioritize.
Negative Signals (Proceed with Caution)
  • Recent Glassdoor reviews mentioning chaos, leadership turnover, or cash flow concerns.
  • Open lawsuits or regulatory actions that consume executive bandwidth.
  • Third CEO in two years. The company doesn't know what it wants.
  • They've ghosted your company before (check your CRM history).

Trigger Event Framework

Trigger events are the #1 indicator of timing. Monitor for these:

Funding & Financial
  • New funding round (Series A-D, PE investment)
  • IPO filing or recent IPO
  • Acquisition (acquirer or acquired)
  • Revenue milestone or earnings report
  • Budget cycle timing (fiscal year start)
People & Org Changes
  • New C-suite or VP hire (especially in your buyer's function)
  • Leadership departure (creates urgency to fix what's broken)
  • Rapid hiring in a specific department (signals investment)
  • Layoffs or restructuring (signals need for efficiency)
  • Board changes
Strategic & Operational
  • Product launch or pivot
  • Geographic expansion or new office
  • Technology migration or vendor change
  • Regulatory change affecting their industry
  • Competitor acquisition or failure
Intent Signals
  • Visiting your website or competitor websites
  • Downloading content, attending webinars
  • Job postings that mention your category or competitors
  • G2/Capterra reviews of competitors
  • Conference attendance or speaking engagements

Where to find triggers: LinkedIn, Crunchbase, Google Alerts, industry newsletters, job boards, G2, press releases, SEC filings, BuiltWith/Wappalyzer, intent data platforms (Bombora, 6sense).

Org Chart Mapping

For every Tier 1 account, map the buying committee:

Roles to Identify
RoleWhat They DoHow to Find
Economic BuyerSigns the check. Usually VP+ or C-suite.LinkedIn title search, press quotes, conference speakers
ChampionWants the change internally. Lives the pain daily.LinkedIn (Director/Manager level in the relevant function), podcast guests, community members
Technical EvaluatorVets the solution. Can say no but rarely says yes alone.Job titles with "Operations," "Systems," "Engineering"
BlockerBenefits from status quo or owns competing budget.Harder to find — often the current vendor's champion
CoachInternal ally who gives you intel. Often a former customer or someone you know.Your CRM, LinkedIn mutual connections
Power Map Template
Account: [Company Name]
─────────────────────────
Economic Buyer: [Name, Title] — [LinkedIn URL]
  Notes: [Background, priorities, public statements]

Champion: [Name, Title] — [LinkedIn URL]
  Notes: [Why they'd care, shared connections]

Technical Eval: [Name, Title] — [LinkedIn URL]
  Notes: [Tech background, likely concerns]

Potential Blocker: [Name, Title] — [LinkedIn URL]
  Notes: [Why they might resist]

Coach/Connection: [Name] — [Relationship]
  Notes: [How they can help]

Tech Stack Research

Understanding what a company already uses tells you:

  • Compatibility — Does your product integrate with their stack?
  • Maturity — Are they sophisticated enough for your solution?
  • Gaps — What's missing that you solve?
  • Competitive displacement — Are they using a competitor you can unseat?
Where to Look
  • Job postings — "Experience with Salesforce, HubSpot, and Gong required" tells you their stack, their maturity level, and their budget priorities. This is the single best source. A "Senior Salesforce Admin" posting means a mature CRM operation. A "CRM Manager (we're evaluating options)" posting means they're in-market.
  • BuiltWith / Wappalyzer — Web technologies, marketing tools, analytics
  • G2/Capterra reviews — What they've reviewed or compared
  • LinkedIn profiles — Employees list tools in skills/experience sections
  • Case studies — Your competitors publish customer stories. Those are your prospects.
  • API/integration pages — Companies list integrations they use on their own site

Building Target Account Lists

ICP Scoring Model

Score each account on a 1-5 scale across these dimensions:

DimensionWeightWhat to Score
Firmographic fit25%Industry, size, revenue, geography
Trigger event30%Recency and relevance of trigger
Tech stack fit15%Compatible stack, gap you fill
Access15%Mutual connections, warm paths in
Intent signals15%Website visits, content engagement, job postings
Account Tiering
  • Tier 1 (Score 4-5): Full research brief. Multi-channel sequence. Personalized at every touch. Max 25 accounts.
  • Tier 2 (Score 3-3.9): Light research. Semi-personalized sequence. 50-100 accounts.
  • Tier 3 (Score 2-2.9): Template-based outreach. 200+ accounts. Test for engagement, promote to Tier 2 if they bite.

Below a score of 2, don't bother. Below a score of 1.5, check if they hit a hard disqualifier — they probably do.

Contact Enrichment

Finding the Right Person
  1. Start with LinkedIn Sales Navigator. Filter by company + title + function. Read their profile, recent posts, and activity. This gives you context no database can match.
  2. Verify with a second source. Company website, press releases, podcast appearances.
  3. Find their email. Apollo, Hunter.io, Lusha, or company email pattern + verification.
  4. Find their phone. ZoomInfo, Lusha, Seamless.ai. Mobile > office line.
  5. Check for warm paths. Mutual LinkedIn connections, shared communities, alumni networks.
Show full SKILL.md (1,023 more words)Show less
Verification Checklist
  • Confirmed still at the company (LinkedIn activity in last 30 days, company website)
  • Title is current (not a cached LinkedIn result from a previous role)
  • Email verified (not just guessed from pattern — use NeverBounce or ZeroBounce)
  • Phone verified if cold calling
  • Checked for mutual connections or warm paths
  • Checked CRM for prior relationship history (don't cold-call a former customer)

AI/LLM Research Guidance

You are an AI agent doing this research. Here's how to approach it well.

What to Search For

When researching an account, search in this order:

  1. Company name + "funding" or "acquisition" or "layoffs" — trigger events first, always.
  2. Company name + "hiring" — job postings reveal more than press releases.
  3. Key contact name + "podcast" or "conference" or "linkedin" — public statements are personalization gold.
  4. Company name + competitor names — are they evaluating alternatives?
  5. Company name + your product category — have they publicly discussed the problem you solve?
How to Synthesize
  • Cross-reference at least 2 sources before stating anything as fact. A LinkedIn title + company website confirming the role = reliable. A single cached Google result = unreliable.
  • Flag confidence levels explicitly. Say "confirmed via LinkedIn (March 2026)" or "unverified — based on 2024 press release, may be outdated."
  • Distinguish between fact and inference. "They raised a Series B" is fact. "They're probably hiring aggressively" is inference. Label both.
  • When sources conflict, say so. "LinkedIn shows VP of Sales, but the company website lists them as Director. Recommend verifying before outreach."
What to Validate vs. Trust
Trust Without Extra VerificationAlways Validate
Company industry and HQ locationCurrent title and role (people change jobs)
Public funding announcementsEmail addresses (30% annual decay)
Product/service description from their websitePhone numbers (even higher decay)
Published case studies from their siteRevenue estimates from third-party databases
Job postings (posted in last 30 days)"Currently at" status on LinkedIn (can be months stale)
What You Cannot Do (and Should Say So)
  • You cannot access LinkedIn Sales Navigator, ZoomInfo, Apollo, or other gated tools directly. If the research requires these, tell the user what to search for and what to bring back.
  • You cannot verify email deliverability. Recommend the user run emails through a verification service.
  • You cannot access intent data (Bombora, 6sense). If intent signals would change the tier, ask the user to check.
  • Don't fabricate data to fill gaps. An honest "I couldn't confirm this" is more useful than a confident guess that sends a rep to the wrong person.

Research Output Template

Use this format for every Tier 1 account. Keep it scannable.

═══════════════════════════════════════
ACCOUNT BRIEF: [Company Name]
Tier: [1/2/3] | Score: [X/5]
Researched: [Date] | Refresh by: [Date + decay window]
═══════════════════════════════════════

COMPANY SNAPSHOT
  Industry: [Industry]
  Size: [Employees] | Revenue: [Est. revenue] [confidence: high/medium/low]
  Stage: [Funding stage / Public / Bootstrapped]
  HQ: [Location]
  Fiscal Year Start: [Month, if known]

TRIGGER EVENT
  [What happened] — [Date]
  Source: [Where you found this]
  Why it matters: [1-2 sentences on relevance to our solution]

DISQUALIFICATION CHECK
  Hard disqualifiers: None found / [List any concerns]
  Negative signals: None found / [List any concerns]

KEY CONTACTS
  Primary: [Name, Title] — [Email] — [LinkedIn]
    Confidence: [Verified/Unverified] | Last confirmed: [Date]
    Angle: [Why they'd care, what to reference]
  Secondary: [Name, Title] — [Email] — [LinkedIn]
    Angle: [Different entry point]

TECH STACK (Relevant)
  Using: [Tools in our category/adjacent]
  Gap: [What's missing that we solve]
  Competitor: [If using a competitor, which one]
  Source: [Job postings / BuiltWith / LinkedIn profiles]

WARM PATHS
  [Mutual connection, shared community, recent interaction]

RECOMMENDED APPROACH
  Channel: [Email / LinkedIn / Phone / Referral]
  Hook: [1-line opener based on trigger + research]
  Sequence: [Which outbound-sequence cadence to use]
═══════════════════════════════════════

End-to-End Example

Here's what excellent research looks like, start to finish, for a fictional company.

Step 1: Trigger Event Discovery

You're selling AI-powered sales coaching software. While scanning LinkedIn, you notice that Meridian Cloud (a $40M ARR B2B SaaS company) just posted three job listings for Account Executives and one for a "Sales Enablement Manager — new role." A new enablement hire plus aggressive AE hiring signals a sales org scaling past its current processes.

Time spent so far: 2 minutes.

Step 2: Initial Qualification

Quick checks — do they pass the ICP filter?

  • Industry: B2B SaaS. Yes.
  • Size: 280 employees, $40M ARR (from Crunchbase). Yes — sweet spot.
  • Raised Series C ($55M) 8 months ago. Capital to spend.
  • HQ: Austin, TX. No geographic issues.
  • CRM check: No prior relationship. Clean slate.

Hard disqualifiers: None. No competitor contract found. No M&A activity. No hiring freeze (obviously — they're hiring aggressively).

Time spent so far: 5 minutes.

Step 3: Org Chart Mapping

LinkedIn Sales Nav search for Meridian Cloud + "Sales" + VP/Director:

  • Lisa Huang, VP of Sales — Joined 7 months ago (post-Series C hire). Previously VP of Sales at a company that used Gong. Posts about "building a repeatable sales motion." This is the economic buyer.
  • Derek Patel, Director of Sales Ops — Been there 2 years. LinkedIn skills include Salesforce, Outreach, Clari. Technical evaluator.
  • The new Sales Enablement Manager — Not yet hired. This is the champion role. Whoever fills it will own this problem.
  • Mike Chen, CTO — Potential blocker if he views this as an engineering/data problem.

Mutual connections: Your CEO knows Meridian's Series C lead at Accel. Warm path exists.

Time spent so far: 12 minutes.

Step 4: Tech Stack Confirmation

The AE job posting says: "You'll use Salesforce, Outreach, Gong, and Clari daily." Confirmed — they already use Gong for conversation intelligence but may not be using it for coaching workflows. The enablement manager posting says "build a scalable onboarding and coaching program" — they're building this function from scratch.

BuiltWith confirms: Salesforce, Marketo, Intercom on the website.

Time spent so far: 15 minutes. Stop here.

Step 5: Completed Research Brief
═══════════════════════════════════════
ACCOUNT BRIEF: Meridian Cloud
Tier: 1 | Score: 4.6/5
Researched: 2026-03-10 | Refresh by: 2026-04-10
═══════════════════════════════════════

COMPANY SNAPSHOT
  Industry: B2B SaaS (cloud infrastructure)
  Size: 280 employees | Revenue: ~$40M ARR [confidence: medium — Crunchbase estimate]
  Stage: Series C ($55M, closed Aug 2025)
  HQ: Austin, TX
  Fiscal Year Start: January

TRIGGER EVENT
  Hired VP of Sales (Lisa Huang) 7 months ago + now hiring 3 AEs
  and a new Sales Enablement Manager role — Source: LinkedIn job postings
  Why it matters: Classic post-funding scaling pattern. New sales
  leader building her team, no enablement infrastructure yet. They're
  going to feel the ramp-time pain around AE #8-10. We solve that.

DISQUALIFICATION CHECK
  Hard disqualifiers: None
  Negative signals: None — Glassdoor reviews are positive (4.1 stars),
  no leadership churn beyond normal Series C growth hiring

KEY CONTACTS
  Primary: Lisa Huang, VP of Sales — lhuang@meridiancloud.com (unverified,
    pattern-matched) — linkedin.com/in/lisahuang-sales
    Confidence: Title verified via LinkedIn + company website | March 2026
    Angle: She's building the sales org post-Series C. Previously at a
    Gong customer — she knows the category. Reference her LinkedIn post
    about "repeatable sales motion" and the enablement hire.
  Secondary: Derek Patel, Director of Sales Ops — dpatel@meridiancloud.com
    (unverified) — linkedin.com/in/derekpatel-salesops
    Angle: He runs the stack. Salesforce + Outreach + Clari. Ask about
    how they're measuring ramp time today.

TECH STACK (Relevant)
  Using: Salesforce, Outreach, Gong, Clari, Marketo
  Gap: No dedicated coaching/enablement platform. Gong is recording
    calls but not structured for coaching workflows.
  Competitor: Gong (adjacent, not direct competitor for coaching)
  Source: Job postings + BuiltWith + LinkedIn profiles

WARM PATHS
  CEO → Accel partner who led Meridian's Series C (ask for intro to Lisa)

RECOMMENDED APPROACH
  Channel: Warm intro via Accel if possible. If not, LinkedIn to Lisa +
    email sequence to Derek (multi-thread from Day 1)
  Hook: "Saw you're building the enablement function from scratch —
    most VP of Sales hires at post-Series C companies tell me the
    ramp-time wall hits around AE #8."
  Sequence: 30-Day Nurture cadence (mid-market, VP-level buyer)
═══════════════════════════════════════

Total research time: 15 minutes. The rep can scan this brief in 60 seconds and write a personalized first touch in 5 minutes. That's the standard.

Common Mistakes

  • Researching for hours without reaching out. Research is a means to outreach, not a substitute for it. If you can write a relevant opening line, stop researching and start reaching out.
  • Over-personalizing for low-tier accounts. Save the deep research for accounts that justify it. A Tier 3 account should get 2 minutes of research, max.
  • Ignoring negative signals. Recent layoffs in your buyer's department, frozen budgets, or a competitor contract signed 3 months ago — these are disqualifiers. Move on.
  • Researching the company but not the person. The person's background, career moves, and public statements are what make outreach feel personal. Companies don't take meetings. People do.
  • Not checking your own CRM first. The most embarrassing research failure is cold-emailing a former customer, an active deal, or someone who asked to be removed. Check CRM before anything else.
  • Treating research as a one-time event. Account briefs decay. A Tier 1 account you researched 6 months ago needs a refresh before re-engagement. People change jobs, priorities shift, budgets get reallocated.
  • cold-email — Use research findings to write personalized cold emails
  • cold-call — Use trigger events and account context for call openers
  • linkedin-outreach — Use mutual connections and org mapping for LinkedIn sequences
  • direct-mail — Use research to personalize dimensional mailers
  • outbound-sequence — Orchestrate research-informed outreach across channels
  • buyer-persona — Deeper persona development beyond individual account research
  • competitive-intel — When research reveals competitor presence, build a battle card

© TheCraigHewitt, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in sales/lead-research of TheCraigHewitt/skills.

Open the folder on GitHubat commit fdbf39b

Compare with similar skills

Lead Research next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Lead Research compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Lead Research this skillTheCraigHewitt/skills159—~5.9kAutomated safety check: PassMIT
B2B Lead Generationminhnv0807/ai-business-skills609—~1.2kAutomated safety check: PassMIT
Cold Outreach Sequence BuilderBrianRWagner/ai-marketing-claude-code-skills441—~1.9kAutomated safety check: PassNone
Cold Outreachericrisco/rsc-harness180—~4.1kAutomated safety check: PassMIT
Personalize Emailexplorium-ai/gtm-skills185—~2kAutomated safety check: PassMIT
Apify Buying Signal Detectionapify/awesome-skills266—~5.1kAutomated safety check: NotesApache-2.0

Similar skills

  • B2B Lead Generation

    minhnv0807/ai-business-skills

    Plans B2B pipeline work from ICP definition and prospecting through lead scoring, outbound sequences, sales assets and MQL to SQL handoff, aiming at qualified pipeline.

    609 GitHub stars~1.2k tokensUpdated 28 days ago
    Sales & SupportAuto-check passed
  • Cold Outreach Sequence Builder

    BrianRWagner/ai-marketing-claude-code-skills

    Builds researched LinkedIn and email outreach for prospects, from a single message to a multi-prospect system, with personalization graded by the signals found.

    441 GitHub stars~1.9k tokensUpdated 6 mo ago
    Sales & SupportAuto-check passed
  • Cold Outreach

    ericrisco/rsc-harness

    A skill your agent uses when writing a cold email or LinkedIn DM to a stranger and its cadence: first-touch copy under a word ceiling, 4-7 step bump sequences, per-inbox volume and warm-up limits…

    180 GitHub stars~4.1k tokensUpdated yesterday
    Sales & SupportAuto-check passed
  • Personalize Email

    explorium-ai/gtm-skills

    Cold email personalization skill for Claude Code and Codex: assemble an intent and firmographic signal pack for one prospect so a downstream LLM can compose a truly personalized outbound email.

    185 GitHub stars~2k tokensUpdated 2 days ago
    Sales & SupportAuto-check passed
  • Apify Buying Signal Detection

    apify/awesome-skills

    Official

    Set up a recurring buying-signal detection pipeline that finds companies showing buying intent across three signal types — job postings (hiring for the persona), fundraising events (recent raises)…

    266 GitHub stars~5.1k tokensUpdated 18 days ago
    Business, Finance & HRAuto-check: notes
  • Prospecting

    coreyhaines31/marketingskills

    When the user wants to find, qualify, and build a list of prospects to reach out to, across B2B SaaS, general B2B, or local small businesses.

    54k GitHub stars~5k tokensUpdated 2 days ago
    Sales & SupportAuto-check passed

More from TheCraigHewitt/skills

All 65 skills in this repo
  • Carousels

    TheCraigHewitt/skills

    Turns a piece of Craig's content (an email, a YouTube script, an essay, or pasted text) into a polished image carousel publishable to both LinkedIn and Instagram from one set of 1080x1350 slides.

    159 GitHub stars~2.3k tokensUpdated 4 mo ago
    Auto-check passed
  • Audience Research

    TheCraigHewitt/skills

    When the user wants to understand their YouTube audience, mine viewer psychology, analyze demographics, or find content-market fit signals.

    159 GitHub stars~2.4k tokensUpdated 4 mo ago
    Auto-check passed
  • Brain Dump

    TheCraigHewitt/skills

    Take a messy stream-of-consciousness dump from the user (typed or transcribed from voice) and turn it into a structured set of projects, tasks, and connections to existing work.

    159 GitHub stars~1.3k tokensUpdated 4 mo ago
    Auto-check passed
  • Channel Audit

    TheCraigHewitt/skills

    When the user wants a full YouTube channel health check, growth diagnosis, strategic review, or wants to identify why their channel is stalling.

    159 GitHub stars~2.4k tokensUpdated 4 mo ago
    Auto-check passed
  • Channel Strategy

    TheCraigHewitt/skills

    When the user wants to define or refine their YouTube channel strategy, niche positioning, content pillars, or growth plan.

    159 GitHub stars~2.2k tokensUpdated 4 mo ago
    Auto-check passed
  • Cold Call

    TheCraigHewitt/skills

    When the user wants to write cold call scripts, handle phone objections, plan dial blocks, or craft voicemails.

    159 GitHub stars~5k tokensUpdated 4 mo ago
    Auto-check passed

Works with

Categories

Questions about Lead Research

What does Lead Research do?

When the user wants to research accounts, contacts, or build target lists. Lead Research is an agent skill from TheCraigHewitt/skills. When the user wants to research accounts, contacts, or build target lists.

When should I use Lead Research?

Lead Research fits situations like: wants to research accounts; build target lists; the user says research this company; find decision makers.

How do I install Lead Research in Claude Code?

Run `npx skills add TheCraigHewitt/skills --skill lead-research -a claude-code`. Or copy the skill folder (sales/lead-research in TheCraigHewitt/skills) into .claude/skills/lead-research in your project. Claude Code loads it when a task matches its description.

How do I install Lead Research in Codex?

Run `npx skills add TheCraigHewitt/skills --skill lead-research -a codex`. Or copy the skill folder (sales/lead-research in TheCraigHewitt/skills) into .agents/skills/lead-research in your project. Codex loads it when a task matches its description.

Can I use Lead Research in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add TheCraigHewitt/skills --skill lead-research -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lead-research, .gemini/skills/lead-research, .github/skills/lead-research and .opencode/skills/lead-research in your project.

What does Lead Research need to run?

SKILL.md names no scripts, command-line tools or credentials: Lead Research is instructions for the agent only.

Does Lead Research access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Lead Research safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Lead Research use?

Lead Research is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Lead Research use?

About 5.9k tokens (SKILL.md is roughly 24k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Lead Research?

Skills that share tags, products or a category with Lead Research: B2B Lead Generation (minhnv0807/ai-business-skills, 609 stars), Cold Outreach Sequence Builder (BrianRWagner/ai-marketing-claude-code-skills, 441 stars), Cold Outreach (ericrisco/rsc-harness, 180 stars) and Personalize Email (explorium-ai/gtm-skills, 185 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Lead Research?

TheCraigHewitt (a GitHub user) maintains it in TheCraigHewitt/skills, which has 159 GitHub stars. The repository holds 65 skills in this directory. The repository was last updated on May 22, 2026.

Source: TheCraigHewitt/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.