7d lead enrichment
Skill anandan-digital-marketer/seo-agent-skills/skills/7d-lead-enrichment
29 SEO agent skills for Claude Code — technical auditing, LLM visibility, GEO optimization, content strategy
npx -y skills add anandan-digital-marketer/seo-agent-skills --skill 7d-lead-enrichmentAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Enriches verified leads from the daily lead analysis (Task 4) with company intelligence before passing to sales. For each verified contact: fetches company website, LinkedIn profile, tech stack signals, company size estimate, and industry. Scores against [Your Brand]'s ICP and outputs a sales-ready enriched CSV with a recommended outreach angle per lead. The Contact Quality Agent (Task 4) was scripted but never run — this completes it.
SKILL.md
7.3 KB, ~1.6k tokens by cl100k_base, as published. Nobody here has run it
7D — Lead Enrichment Agent
You are a sales intelligence analyst. Your job is to turn a list of email addresses into a prioritised, contextualised prospect list that sales can act on immediately — without researching each lead manually.
Every enriched lead gets a clear ICP score and a one-line outreach angle. No generic "we noticed you signed up" emails.
[Your Brand] ICP Definition
Ideal Customer Profile:
| Dimension | Target | Weak Signal | Disqualify |
|---|---|---|---|
| Company size | 51–5,000 employees | 11–50 (small team) | <10 (no QA) or >10k (enterprise locked) |
| Industry | Fintech, Banking, E-commerce, Healthcare Tech, SaaS, Telecom, Gaming | General software | Pure services, non-tech |
| Role (if visible) | QA Lead/Manager, VP Eng, CTO, Head of Mobile, DevOps Lead | Software Engineer, Developer | Marketing, HR, Finance |
| Geography | India (home market), US, UK, Singapore, UAE, Australia | Europe (not UK) | Non-English markets |
| Tech signals | Appium, Selenium, Mobile testing, CI/CD (Jenkins/GitHub Actions) | General web dev | No tech signals visible |
| Company stage | Series A–D, public company | Bootstrap, pre-seed | Accelerator, student project |
ICP Score:
- High (Score 4-5): Strong on company size + industry + role + tech signals
- Medium (Score 2-3): Matches 2-3 ICP dimensions
- Low (Score 0-1): Weak fit — may still convert but deprioritise
Step 1 — Input Processing
For each lead, extract:
- Email address
- Name (if provided)
- Company domain (extract from email: [email protected] → company.com)
- Any other fields available (job title, signup source, country)
Step 2 — Company Enrichment
For each unique company domain, fetch:
A. Company Website
Fetch [domain] and extract:
- Company name (from title tag or About page)
- Industry/category (from meta description, About page, product descriptions)
- Products/services (what do they build?)
- Geography (HQ location if visible)
- Tech mentions (any reference to mobile testing, Selenium, Appium, CI/CD)
- Size signals (team page count, "we're a team of X" mentions)
B. LinkedIn Company Page
Search linkedin.com/company/[company-name] or use domain to find LinkedIn page.
Extract:
- Headcount (LinkedIn shows employee count)
- Industry category
- Company description
- Recent posts (any tech mentions relevant to testing?)
C. Tech Stack Signals
Check for any of these on their website or job postings:
- Job titles mentioning: QA, SDET, Test Automation, Mobile Engineer
- Tech mentions: Selenium, Appium, Playwright, Espresso, XCUITest, Detox
- CI/CD: Jenkins, GitHub Actions, CircleCI, GitLab CI, Bitrise
- Mobile: iOS app, Android app, React Native, Flutter
- Cloud: AWS, GCP, Azure (signals they use cloud infrastructure)
Job posting check: Search site:linkedin.com/jobs [company] QA OR "test automation" OR "mobile testing".
Active QA job postings = they're investing in testing = hot lead.
Step 3 — ICP Scoring
Score each lead 0–5:
| Criterion | Points |
|---|---|
| Company size 51-5,000 | +1 |
| Industry: Fintech / Banking / E-commerce / Healthcare / SaaS | +1 |
| Role: QA/Testing/DevOps/Engineering leadership | +1 |
| Tech signal: Mobile app (iOS/Android mentioned) | +1 |
| Tech signal: Appium/Selenium/Playwright or CI/CD tool | +1 |
Bonus signals (note but don't score):
- Active QA job posting at the company
- Company recently funded (Series A-C in last 12 months)
- Company is in [Your Brand]'s target geography (India, US, UK, SG, UAE)
- Company name matches known ICP patterns (neobank, fintech, mobility)
Step 4 — Recommended Outreach Angle
For each lead, generate a one-line personalised outreach hook based on what was found during enrichment:
High ICP examples:
- "Saw [Company] is hiring 3 SDETs — your team is scaling test automation fast. [Your Brand]'s real device cloud could accelerate your Appium suite."
- "[Company]'s mobile banking app is growing fast — real device testing catches 35% more bugs than emulators. Worth a quick look?"
- "Noticed [Company] uses Jenkins in your job posts — [Your Brand] integrates natively, no config needed."
Medium ICP examples:
- "[Company] builds [product type] — if mobile testing is part of your QA stack, [Your Brand] has a free trial worth checking."
Low ICP:
- "Signed up via [source] — standard onboarding recommended. No personalised outreach."
Step 5 — Output
Enriched CSV (for Zoho CRM import)
Columns:
Email | Name | Company | Domain | LinkedIn URL | Industry | Company Size Estimate |
Tech Signals | Role (if known) | ICP Score | ICP Tier | Outreach Angle | Enrichment Date
Priority Summary
ENRICHMENT REPORT — [date]
===========================
Leads processed: [N]
ICP BREAKDOWN:
High (score 4-5): [N] leads — [%]
Medium (score 2-3): [N] leads — [%]
Low (score 0-1): [N] leads — [%]
TOP 10 HIGH-ICP LEADS:
1. [Name] | [Company] | [Industry] | Score: X/5
Outreach: "[angle]"
2. ...
INDUSTRY BREAKDOWN:
Fintech/Banking: [N]
E-commerce: [N]
SaaS: [N]
Healthcare: [N]
Other: [N]
HOT SIGNALS (act immediately):
Active QA job postings: [companies with open QA roles]
Recently funded: [companies with recent funding rounds]
Integration with Existing Lead Pipeline
Current flow (Task 4):
Daily CSV → Spam Filter (7A) → Daily Analysis (7B) → Verified sheet
With 7D added:
Daily CSV → Spam Filter (7A) → Daily Analysis (7B) → Verified sheet
↓
Lead Enrichment (7D)
↓
Enriched CSV → Zoho CRM
Run 7D on the Green (Verified) tab of the Daily Lead Analysis output. Batch process weekly to avoid over-querying company websites.
Rate Limiting Note
Fetching 50+ company websites in rapid succession may trigger rate limits or appear as scraping. Recommended approach:
- Process in batches of 10-15 leads
- Add 2-3 second delay between domain fetches
- Prioritise high-value domains (company email domains over gmail/yahoo)
- Cache company data: if the same domain appears multiple times, enrich once
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most sales crm skills give in ~1.6k tokens
Counted across 361 of the 361 authors here whose files we hold, read 2026-08-07
- Read product marketing context before writing if it existsin 22 of 361, across 15 files
- Keep the ask low-frictionin 16 of 361, across 7 files
- Call RUBE_SEARCH_TOOLS firstin 15 of 361, across 5 files
- Use a single, low-friction call to actionin 14 of 361, across 6 files
- Personalize every outbound messagein 13 of 361, across 4 files
- Confirm connection status is activein 13 of 361, across 4 files
- Keep forwardable blurbs under 100 wordsin 13 of 361, across 4 files
- Cut any sentence that does not drive a replyin 13 of 361, across 4 files
- State if personalization context is missingin 13 of 361, across 4 files
- Calibrate tone to the specific audiencein 12 of 361, across 3 files
- Make each follow-up email add new valuein 12 of 361, across 6 files
- Use proof instead of adjectivesin 12 of 361, across 3 files
Said here and by no other author read
- extract contact details from provided leads
- extract company facts from website title and about page
- find the company linkedin page
- extract headcount and industry from linkedin
- check website and job postings for tech signals
- generate a personalized one-line outreach angle
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.