skills/lead-enrichment/SKILL.md
Enrich contact and lead records with LinkedIn profiles, email addresses, company data, and education info. Use when asked to "enrich contacts", "fill in missing data", "find emails for leads", "complete lead profiles", "look up company info", or any bulk data completion task for CRM records.
npx skillsauth add aspenas/ironclaw-skills lead-enrichmentInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Enrich CRM contact records by filling missing fields from multiple sources. Works with DuckDB workspace entries or standalone JSON data.
-- Query the target object to find gaps
SELECT "Name", "Email", "LinkedIn URL", "Company", "Title", "Location"
FROM v_leads
WHERE "Email" IS NULL OR "LinkedIn URL" IS NULL OR "Title" IS NULL;
For each record with gaps:
{name} {company} or {name} {title}"email" "{name}" site:{domain}"{name}" "{title}" or check LinkedIn-- Update via DuckDB pivot view
UPDATE v_leads SET
"Email" = ?,
"LinkedIn URL" = ?,
"Title" = ?,
"Company" = ?,
"Location" = ?
WHERE id = ?;
For enriching many records at once:
Enrichment Progress: 45/120 leads (38%)
├── Emails found: 32/45 (71%)
├── LinkedIn matched: 41/45 (91%)
├── Titles updated: 38/45 (84%)
└── ETA: ~15 min remaining
Common corporate email formats by frequency:
[email protected] (most common, ~45%)[email protected] (~20%)[email protected] (~15%)[email protected] (~10%)[email protected] (~5%)[email protected] (~3%)[email protected] (~2%)Strategy:
"@{domain}" email formatAfter enrichment, provide a summary:
Enrichment Complete: 120 leads processed
├── Emails: 94 found (78%), 26 still missing
├── LinkedIn: 108 matched (90%), 12 not found
├── Titles: 115 updated (96%)
├── Companies: 118 confirmed (98%)
├── Locations: 89 found (74%)
└── Avg confidence: High (82%), Medium (14%), Low (4%)
Top gaps remaining:
- 26 leads missing email (mostly small/stealth companies)
- 12 leads missing LinkedIn (common names, ambiguous matches)
Standard field names for Ironclaw CRM objects:
| Enrichment Data | DuckDB Field | Type | |----------------|--------------|------| | Full name | Name | text | | Email address | Email | email | | LinkedIn URL | LinkedIn URL | url | | Job title | Title | text | | Company name | Company | text / relation | | Location | Location | text | | Education | Education | text | | Phone | Phone | phone | | Company size | Company Size | text | | Industry | Industry | text | | Enrichment date | Enriched At | date | | Confidence | Enrichment Confidence | enum (high/medium/low) |
data-ai
Example TaskFlow authoring pattern for inbox triage. Use when messages need different treatment based on intent, with some routes notifying immediately, some waiting on outside answers, and others rolling into a later summary.
data-ai
Example TaskFlow authoring pattern for inbox triage. Use when messages need different treatment based on intent, with some routes notifying immediately, some waiting on outside answers, and others rolling into a later summary.
data-ai
OpenProse VM skill pack. Activate on any `prose` command, .prose files, or OpenProse mentions; orchestrates multi-agent workflows.
data-ai
OpenProse VM skill pack. Activate on any `prose` command, .prose files, or OpenProse mentions; orchestrates multi-agent workflows.