$npx -y skills add ECNU-ICALK/AutoSkill --skill lead-research-assistantIdentifies 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.
| 1 | # Lead Research Assistant |
| 2 | |
| 3 | 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. |
| 4 | |
| 5 | ## When to Use This Skill |
| 6 | |
| 7 | - Finding potential customers or clients for your product/service |
| 8 | - Building a list of companies to reach out to for partnerships |
| 9 | - Identifying target accounts for sales outreach |
| 10 | - Researching companies that match your ideal customer profile |
| 11 | - Preparing for business development activities |
| 12 | |
| 13 | ## What This Skill Does |
| 14 | |
| 15 | 1. **Understands Your Business**: Analyzes your product/service, value proposition, and target market |
| 16 | 2. **Identifies Target Companies**: Finds companies that match your ideal customer profile based on: |
| 17 | - Industry and sector |
| 18 | - Company size and location |
| 19 | - Technology stack and tools they use |
| 20 | - Growth stage and funding |
| 21 | - Pain points your product solves |
| 22 | 3. **Prioritizes Leads**: Ranks companies based on fit score and relevance |
| 23 | 4. **Provides Contact Strategies**: Suggests how to approach each lead with personalized messaging |
| 24 | 5. **Enriches Data**: Gathers relevant information about decision-makers and company context |
| 25 | |
| 26 | ## How to Use |
| 27 | |
| 28 | ### Basic Usage |
| 29 | |
| 30 | Simply describe your product/service and what you're looking for: |
| 31 | |
| 32 | ``` |
| 33 | I'm building [product description]. Find me 10 companies in [location/industry] |
| 34 | that would be good leads for this. |
| 35 | ``` |
| 36 | |
| 37 | ### With Your Codebase |
| 38 | |
| 39 | For even better results, run this from your product's source code directory: |
| 40 | |
| 41 | ``` |
| 42 | Look at what I'm building in this repository and identify the top 10 companies |
| 43 | in [location/industry] that would benefit from this product. |
| 44 | ``` |
| 45 | |
| 46 | ### Advanced Usage |
| 47 | |
| 48 | For more targeted research: |
| 49 | |
| 50 | ``` |
| 51 | My product: [description] |
| 52 | Ideal customer profile: |
| 53 | - Industry: [industry] |
| 54 | - Company size: [size range] |
| 55 | - Location: [location] |
| 56 | - Current pain points: [pain points] |
| 57 | - Technologies they use: [tech stack] |
| 58 | |
| 59 | Find me 20 qualified leads with contact strategies for each. |
| 60 | ``` |
| 61 | |
| 62 | ## Instructions |
| 63 | |
| 64 | When a user requests lead research: |
| 65 | |
| 66 | 1. **Understand the Product/Service** |
| 67 | - If in a code directory, analyze the codebase to understand the product |
| 68 | - Ask clarifying questions about the value proposition |
| 69 | - Identify key features and benefits |
| 70 | - Understand what problems it solves |
| 71 | |
| 72 | 2. **Define Ideal Customer Profile** |
| 73 | - Determine target industries and sectors |
| 74 | - Identify company size ranges |
| 75 | - Consider geographic preferences |
| 76 | - Understand relevant pain points |
| 77 | - Note any technology requirements |
| 78 | |
| 79 | 3. **Research and Identify Leads** |
| 80 | - Search for companies matching the criteria |
| 81 | - Look for signals of need (job postings, tech stack, recent news) |
| 82 | - Consider growth indicators (funding, expansion, hiring) |
| 83 | - Identify companies with complementary products/services |
| 84 | - Check for budget indicators |
| 85 | |
| 86 | 4. **Prioritize and Score** |
| 87 | - Create a fit score (1-10) for each lead |
| 88 | - Consider factors like: |
| 89 | - Alignment with ICP |
| 90 | - Signals of immediate need |
| 91 | - Budget availability |
| 92 | - Competitive landscape |
| 93 | - Timing indicators |
| 94 | |
| 95 | 5. **Provide Actionable Output** |
| 96 | |
| 97 | For each lead, provide: |
| 98 | - **Company Name** and website |
| 99 | - **Why They're a Good Fit**: Specific reasons based on their business |
| 100 | - **Priority Score**: 1-10 with explanation |
| 101 | - **Decision Maker**: Role/title to target (e.g., "VP of Engineering") |
| 102 | - **Contact Strategy**: Personalized approach suggestions |
| 103 | - **Value Proposition**: How your product solves their specific problem |
| 104 | - **Conversation Starters**: Specific points to mention in outreach |
| 105 | - **LinkedIn URL**: If available, for easy connection |
| 106 | |
| 107 | 6. **Format the Output** |
| 108 | |
| 109 | Present results in a clear, scannable format: |
| 110 | |
| 111 | ```markdown |
| 112 | # Lead Research Results |
| 113 | |
| 114 | ## Summary |
| 115 | - Total leads found: [X] |
| 116 | - High priority (8-10): [X] |
| 117 | - Medium priority (5-7): [X] |
| 118 | - Average fit score: [X] |
| 119 | |
| 120 | --- |
| 121 | |
| 122 | ## Lead 1: [Company Name] |
| 123 | |
| 124 | **Website**: [URL] |
| 125 | **Priority Score**: [X/10] |
| 126 | **Industry**: [Industry] |
| 127 | **Size**: [Employee count/revenue range] |
| 128 | |
| 129 | **Why They're a Good Fit**: |
| 130 | [2-3 specific reasons based on their business] |
| 131 | |
| 132 | **Target Decision Maker**: [Role/Title] |
| 133 | **LinkedIn**: [URL if available] |
| 134 | |
| 135 | **Value Proposition for Them**: |
| 136 | [Specific benefit for this company] |
| 137 | |
| 138 | **Outreach Strategy**: |
| 139 | [Personalized approach - mention specific pain points, recent company news, or relevant context] |
| 140 | |
| 141 | **Conversation Starters**: |
| 142 | - [Specific point 1] |
| 143 | - [Specific point 2] |
| 144 | |
| 145 | --- |
| 146 | |
| 147 | [Repeat for each lead] |
| 148 | ``` |
| 149 | |
| 150 | 7. **Offer Next Steps** |
| 151 | - Suggest saving results to a CSV for CRM import |
| 152 | - Offer to d |