AGENT SKILL

lead-research-assistant

Identifies high-quality leads for your product or service by analyzing your business, searching for target companies, and providing actionable contact strategies. Perfect for sales, business development, and marketing professionals.

License 许可
MIT
最近更新
2026-11-14
Stars
★ 3.3w
Forks
3.9k

01 前言 Front Matter

name
lead-research-assistant
description
Identifies high-quality leads for your product or service by analyzing your business, searching for target companies, and providing actionable contact strategies. Perfect for sales, business development, and marketing professionals.

03 SKILL.md 正文

Lead Research Assistant

This skill helps you identify and qualify potential leads for your business by analyzing your product/service, understanding your ideal customer profile, and providing actionable outreach strategies.

When to Use This Skill

  • Finding potential customers or clients for your product/service
  • Building a list of companies to reach out to for partnerships
  • Identifying target accounts for sales outreach
  • Researching companies that match your ideal customer profile
  • Preparing for business development activities

What This Skill Does

  1. Understands Your Business: Analyzes your product/service, value proposition, and target market
  2. Identifies Target Companies: Finds companies that match your ideal customer profile based on:
    • Industry and sector
    • Company size and location
    • Technology stack and tools they use
    • Growth stage and funding
    • Pain points your product solves
  3. Prioritizes Leads: Ranks companies based on fit score and relevance
  4. Provides Contact Strategies: Suggests how to approach each lead with personalized messaging
  5. Enriches Data: Gathers relevant information about decision-makers and company context

How to Use

Basic Usage

Simply describe your product/service and what you're looking for:

I'm building [product description]. Find me 10 companies in [location/industry] 
that would be good leads for this.

With Your Codebase

For even better results, run this from your product's source code directory:

Look at what I'm building in this repository and identify the top 10 companies 
in [location/industry] that would benefit from this product.

Advanced Usage

For more targeted research:

My product: [description]
Ideal customer profile:
- Industry: [industry]
- Company size: [size range]
- Location: [location]
- Current pain points: [pain points]
- Technologies they use: [tech stack]

Find me 20 qualified leads with contact strategies for each.

Instructions

When a user requests lead research:

  1. Understand the Product/Service

    • If in a code directory, analyze the codebase to understand the product
    • Ask clarifying questions about the value proposition
    • Identify key features and benefits
    • Understand what problems it solves
  2. Define Ideal Customer Profile

    • Determine target industries and sectors
    • Identify company size ranges
    • Consider geographic preferences
    • Understand relevant pain points
    • Note any technology requirements
  3. Research and Identify Leads

    • Search for companies matching the criteria
    • Look for signals of need (job postings, tech stack, recent news)
    • Consider growth indicators (funding, expansion, hiring)
    • Identify companies with complementary products/services
    • Check for budget indicators
  4. Prioritize and Score

    • Create a fit score (1-10) for each lead
    • Consider factors like:
      • Alignment with ICP
      • Signals of immediate need
      • Budget availability
      • Competitive landscape
      • Timing indicators
  5. Provide Actionable Output

    For each lead, provide:

    • Company Name and website
    • Why They're a Good Fit: Specific reasons based on their business
    • Priority Score: 1-10 with explanation
    • Decision Maker: Role/title to target (e.g., "VP of Engineering")
    • Contact Strategy: Personalized approach suggestions
    • Value Proposition: How your product solves their specific problem
    • Conversation Starters: Specific points to mention in outreach
    • LinkedIn URL: If available, for easy connection
  6. Format the Output

    Present results in a clear, scannable format:

    # Lead Research Results
    
    ## Summary
    - Total leads found: [X]
    - High priority (8-10): [X]
    - Medium priority (5-7): [X]
    - Average fit score: [X]
    
    ---
    
    ## Lead 1: [Company Name]
    
    **Website**: [URL]
    **Priority Score**: [X/10]
    **Industry**: [Industry]
    **Size**: [Employee count/revenue range]
    
    **Why They're a Good Fit**:
    [2-3 specific reasons based on their business]
    
    **Target Decision Maker**: [Role/Title]
    **LinkedIn**: [URL if available]
    
    **Value Proposition for Them**:
    [Specific benefit for this company]
    
    **Outreach Strategy**:
    [Personalized approach - mention specific pain points, recent company news, or relevant context]
    
    **Conversation Starters**:
    - [Specific point 1]
    - [Specific point 2]
    
    ---
    
    [Repeat for each lead]
    
  7. Offer Next Steps

    • Suggest saving results to a CSV for CRM import
    • Offer to draft personalized outreach messages
    • Recommend prioritization based on timing
    • Suggest follow-up research for top leads

Examples

Example 1: From Lenny's Newsletter

User: "I'm building a tool that masks sensitive data in AI coding assistant queries. Find potential leads."

Output: Creates a prioritized list of companies that:

  • Use AI coding assistants (Copilot, Cursor, etc.)
  • Handle sensitive data (fintech, healthcare, legal)
  • Have evidence in their GitHub repos of using coding agents
  • May have accidentally exposed sensitive data in code
  • Includes LinkedIn URLs of relevant decision-makers

Example 2: Local Business

User: "I run a consulting practice for remote team productivity. Find me 10 companies in the Bay Area that recently went remote."

Output: Identifies companies that:

  • Recently posted remote job listings
  • Announced remote-first policies
  • Are hiring distributed teams
  • Show signs of remote work challenges
  • Provides personalized outreach strategies for each

Tips for Best Results

  • Be specific about your product and its unique value
  • Run from your codebase if applicable for automatic context
  • Provide context about your ideal customer profile
  • Specify constraints like industry, location, or company size
  • Request follow-up research on promising leads for deeper insights

Related Use Cases

  • Drafting personalized outreach emails after identifying leads
  • Building a CRM-ready CSV of qualified prospects
  • Researching specific companies in detail
  • Analyzing competitor customer bases
  • Identifying partnership opportunities

04 同仓库更多 Skills

davila7
davila7/claude-code-templates

wealthville-pool-scoring

Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter/Hold/Exit/Reduce/Avoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.

Skill与智能体开发
★ 3.3w
davila7
davila7/claude-code-templates

technical-debt-auditor

Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO/FIXME/HACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like "where should I focus refactoring", "find code smells", "audit my codebase", "what technical debt do we have", "prioritize cleanup work", or asks about code quality metrics. Also trigger when the user mentions "code rot", "legacy cleanup", "refactoring priorities", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say "technical debt" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.

Skill与智能体开发
★ 3.3w
davila7
davila7/claude-code-templates

readonly-sql-guard

Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production/ERP/analytics database (a "query" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write/DDL/side-effect/transaction-escape risks. Checks what a statement CALLS, not just its shape.

数据分析师后端与接口Skill与智能体开发
★ 3.3w
davila7
davila7/claude-code-templates

web-artifacts-builder

Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.

前端开发
★ 3.3w
davila7
davila7/claude-code-templates

webapp-testing

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

测试与质量前端开发
★ 3.3w
davila7
davila7/claude-code-templates

discernment-nudge

After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.

内容创作者写作与文案Skill与智能体开发
★ 3.3w