Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- 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 miss...
Enrich contact and lead records with LinkedIn profiles, email addresses, company data, and education info. Use when asked to "enrich contacts", "fill in miss...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Enrich CRM contact records by filling missing fields from multiple sources. Works with DuckDB workspace entries or standalone JSON data.
LinkedIn (via linkedin-scraper skill) β name, title, company, education, connections Web Search (via web_search tool) β email patterns, company info, social profiles Company Website (via web_fetch) β team pages, about pages, contact info Email Pattern Discovery β derive email from name + company domain
-- 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;
High priority: Missing email (needed for outreach) Medium priority: Missing title/company (needed for personalization) Low priority: Missing education, connections count, about text
For each record with gaps: If LinkedIn URL is known but other fields missing: Use linkedin-scraper to visit profile Extract: title, company, location, education, about Update DuckDB record If LinkedIn URL is missing: Search LinkedIn: {name} {company} or {name} {title} Verify match (name + company alignment) Store LinkedIn URL, then scrape full profile If Email is missing: Find company domain (web search or LinkedIn company page) Try common patterns: first@domain.com first.last@domain.com flast@domain.com firstl@domain.com Optionally verify with web search: "email" "{name}" site:{domain} Check company team/about page for email format clues If Company info is missing: Web search: "{name}" "{title}" or check LinkedIn Fetch company website for: industry, size, description, funding
-- Update via DuckDB pivot view UPDATE v_leads SET "Email" = ?, "LinkedIn URL" = ?, "Title" = ?, "Company" = ?, "Location" = ? WHERE id = ?;
For enriching many records at once: Query all incomplete records from DuckDB Group by company (scrape company once, apply to all employees) Process in batches of 10-20 records Report progress after each batch: 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 Save checkpoint after each batch (in case of interruption)
Confidence scoring: Mark each enriched field with confidence (high/medium/low) High: Direct match from LinkedIn profile or company website Medium: Inferred from patterns (email format) or partial match Low: Best guess from web search results Never overwrite existing data unless explicitly asked Flag conflicts: If enriched data contradicts existing data, flag for review Dedup check: Before inserting LinkedIn URL, check it's not already assigned to another contact
Common corporate email formats by frequency: first.last@domain.com (most common, ~45%) first@domain.com (~20%) flast@domain.com (~15%) firstl@domain.com (~10%) first_last@domain.com (~5%) last.first@domain.com (~3%) first.l@domain.com (~2%) Strategy: If you know one person's email at the company, derive the pattern Search web for "@{domain}" email format Check company team page source code for mailto: links Use the most common pattern as fallback
Standard field names for Ironclaw CRM objects: Enrichment DataDuckDB FieldTypeFull nameNametextEmail addressEmailemailLinkedIn URLLinkedIn URLurlJob titleTitletextCompany nameCompanytext / relationLocationLocationtextEducationEducationtextPhonePhonephoneCompany sizeCompany SizetextIndustryIndustrytextEnrichment dateEnriched AtdateConfidenceEnrichment Confidenceenum (high/medium/low)
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.