{ "schemaVersion": "1.0", "item": { "slug": "lead-enrichment", "name": "Lead Enrichment", "source": "tencent", "type": "skill", "category": "开发工具", "sourceUrl": "https://clawhub.ai/audsmith28/lead-enrichment", "canonicalUrl": "https://clawhub.ai/audsmith28/lead-enrichment", "targetPlatform": "OpenClaw" }, "install": { "downloadMode": "redirect", "downloadUrl": "/downloads/lead-enrichment", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=lead-enrichment", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "installMethod": "Manual import", "extraction": "Extract archive", "prerequisites": [ "OpenClaw" ], "packageFormat": "ZIP package", "includedAssets": [ "SKILL.md", "config.example.json", "scripts/batch.sh", "scripts/enrich.sh", "scripts/export.sh", "scripts/setup.sh" ], "primaryDoc": "SKILL.md", "quickSetup": [ "Download the package from Yavira.", "Extract the archive and review SKILL.md first.", "Import or place the package into your OpenClaw setup." ], "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "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." }, { "label": "Upgrade existing", "body": "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." } ] }, "sourceHealth": { "source": "tencent", "slug": "lead-enrichment", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-05-04T22:17:33.339Z", "expiresAt": "2026-05-11T22:17:33.339Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=lead-enrichment", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=lead-enrichment", "contentDisposition": "attachment; filename=\"lead-enrichment-1.1.0.zip\"", "redirectLocation": null, "bodySnippet": null, "slug": "lead-enrichment" }, "scope": "item", "summary": "Item download looks usable.", "detail": "Yavira can redirect you to the upstream package for this item.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/lead-enrichment" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] }, "downloadPageUrl": "https://openagent3.xyz/downloads/lead-enrichment", "agentPageUrl": "https://openagent3.xyz/skills/lead-enrichment/agent", "manifestUrl": "https://openagent3.xyz/skills/lead-enrichment/agent.json", "briefUrl": "https://openagent3.xyz/skills/lead-enrichment/agent.md" }, "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "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." }, { "label": "Upgrade existing", "body": "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." } ] }, "documentation": { "source": "clawhub", "primaryDoc": "SKILL.md", "sections": [ { "title": "Lead Enrichment — Research Prospects in Seconds", "body": "Stop spending hours stalking LinkedIn. Let your agent do it.\n\nSales teams waste 6+ hours per week manually researching prospects. You Google their name, check LinkedIn, scroll their Twitter, hunt for their email, read their company's About page, search for recent news... and then do it all over again for the next lead.\n\nLead Enrichment automates all of it. Give your agent a name and company (or email, or LinkedIn URL), and get back a complete dossier: contact info, social profiles, bio, company intel, recent posts, news mentions, and AI-generated talking points.\n\nThe pain: Generic outreach gets ignored. Personalization takes forever. You're always behind quota.\n\nThe fix: Your agent researches 10 leads while you grab coffee. Rich profiles ready when you need them. Spend your time selling, not searching." }, { "title": "What You Get", "body": "For each lead, the enrichment pulls:\n\nPersonal Profile:\n\nFull name, current title, company\nProfessional bio/summary\nProfile photo URL\nLocation\nSocial media handles (LinkedIn, Twitter, GitHub, personal site)\n\nContact Discovery:\n\nLikely email addresses (pattern-based + verification attempts)\nPublic phone numbers (if available)\nBest channels for outreach\n\nCompany Context:\n\nCompany description, industry, size\nFunding stage, recent news\nTech stack (for technical sales)\nKey decision makers\n\nIntelligence & Timing:\n\nRecent posts/articles (last 30 days)\nJob change signals\nCompany news mentions\nShared connections or interests\nConference/event participation\n\nAI-Generated Talking Points:\n\n3-5 personalized hooks based on their recent activity\nCommon ground opportunities\nRelevant pain points to address\nRecommended opening lines" }, { "title": "Setup", "body": "Run scripts/setup.sh to initialize config\nEdit ~/.config/lead-enrichment/config.json with preferences\nNo API keys required for basic enrichment (uses public sources)\nOptional: Add premium data sources (see config)" }, { "title": "Scripts", "body": "ScriptPurposescripts/setup.shInitialize config and data directoriesscripts/enrich.shEnrich a single lead (main script)scripts/batch.shProcess multiple leads from CSV/JSONscripts/export.shExport enriched leads (JSON/MD/CSV)" }, { "title": "Single Lead", "body": "# By name + company\n./scripts/enrich.sh --name \"Sarah Chen\" --company \"Acme Corp\"\n\n# By email\n./scripts/enrich.sh --email \"sarah@acmecorp.com\"\n\n# By LinkedIn URL\n./scripts/enrich.sh --linkedin \"https://linkedin.com/in/sarahchen\"\n\n# Output to file\n./scripts/enrich.sh --name \"Sarah Chen\" --company \"Acme Corp\" --output sarah-chen.json\n\n# With talking points\n./scripts/enrich.sh --name \"Sarah Chen\" --company \"Acme Corp\" --talking-points" }, { "title": "Batch Processing", "body": "# From CSV (columns: name, company, email, linkedin_url)\n./scripts/batch.sh --input leads.csv --output enriched/\n\n# From JSON array\n./scripts/batch.sh --input leads.json --output enriched/\n\n# Process with concurrency\n./scripts/batch.sh --input leads.csv --parallel 3" }, { "title": "Export Formats", "body": "# Export as JSON (default)\n./scripts/export.sh --format json enriched/*.json > leads.json\n\n# Export as Markdown (readable)\n./scripts/export.sh --format markdown enriched/*.json > leads.md\n\n# Export as CSV (CRM import)\n./scripts/export.sh --format csv enriched/*.json > leads.csv\n\n# Pipe to your CRM\n./scripts/export.sh --format json enriched/*.json | \\\n curl -X POST https://your-crm.com/api/leads -d @-" }, { "title": "Config", "body": "Config lives at ~/.config/lead-enrichment/config.json. See config.example.json for full schema.\n\nKey sections:\n\nenrichment.sources — Which data sources to check (all public by default):\n\nlinkedin — Public profiles via search\ntwitter — Social activity and bio\ngithub — For technical leads\ncompany_website — About pages, team directories\nnews — Recent mentions\ncrunchbase — Company funding (public data)\n\nenrichment.depth — How thorough to be:\n\nquick — Basic profile only (name, title, LinkedIn, company)\nstandard — Above + social profiles + recent activity (default)\ndeep — Above + news mentions + talking points + shared connections\n\noutput.format — Default output format (json/markdown/csv)\n\noutput.include — What to include in output:\n\ncontact_info — Email attempts, phone\nsocial_profiles — All discovered links\nrecent_activity — Posts, articles (last 30 days)\ncompany_intel — Company description, size, funding\ntalking_points — AI-generated personalization hooks\nraw_sources — Source URLs for verification\n\ntalking_points.enabled — Generate AI talking points (requires Claude)\n\ntalking_points.style — Tone for suggestions (professional/friendly/bold)\n\nprivacy.respect_robots — Skip profiles with clear \"no scraping\" signals\n\nprivacy.store_locally — Cache enriched profiles (default: true)" }, { "title": "Data Sources", "body": "All sources are public and free:\n\nLinkedIn — Public profiles via search (no API, respects robots.txt)\nTwitter/X — Bio, recent tweets, follower count\nGitHub — For technical roles (repos, activity, README)\nCompany websites — Team pages, About sections\nGoogle News — Recent mentions\nCrunchbase — Public company data (no API key needed for basic info)\nCommon email patterns — firstname@company.com, f.lastname@company.com, etc.\n\nPremium sources (optional, requires API keys):\n\nHunter.io — Email verification\nClearbit — Enhanced company data\nApollo — Direct contact info\n\nAdd API keys to ~/.clawdbot/secrets.env if you have them. Enrichment works fine without them." }, { "title": "Output Schema", "body": "Each enriched lead is saved as JSON:\n\n{\n \"lead_id\": \"sarah-chen-acme-corp\",\n \"enriched_at\": \"2025-01-29T10:30:00Z\",\n \"input\": {\n \"name\": \"Sarah Chen\",\n \"company\": \"Acme Corp\"\n },\n \"profile\": {\n \"full_name\": \"Sarah Chen\",\n \"title\": \"VP of Engineering\",\n \"company\": \"Acme Corp\",\n \"location\": \"San Francisco, CA\",\n \"bio\": \"Building the future of...\",\n \"photo_url\": \"https://...\",\n \"social_profiles\": {\n \"linkedin\": \"https://linkedin.com/in/sarahchen\",\n \"twitter\": \"https://twitter.com/sarahchen\",\n \"github\": \"https://github.com/sarahchen\",\n \"personal_site\": \"https://sarahchen.com\"\n }\n },\n \"contact\": {\n \"emails\": [\n { \"address\": \"sarah@acmecorp.com\", \"confidence\": 0.85, \"verified\": false },\n { \"address\": \"s.chen@acmecorp.com\", \"confidence\": 0.60, \"verified\": false }\n ],\n \"phones\": [],\n \"preferred_channel\": \"email\"\n },\n \"company\": {\n \"name\": \"Acme Corp\",\n \"domain\": \"acmecorp.com\",\n \"industry\": \"SaaS\",\n \"size\": \"51-200 employees\",\n \"description\": \"AI-powered...\",\n \"funding\": \"Series B ($25M)\",\n \"tech_stack\": [\"React\", \"Node.js\", \"AWS\"],\n \"recent_news\": [\n {\n \"title\": \"Acme Corp raises $25M...\",\n \"url\": \"https://...\",\n \"date\": \"2025-01-15\"\n }\n ]\n },\n \"intelligence\": {\n \"recent_activity\": [\n {\n \"type\": \"twitter_post\",\n \"content\": \"Excited to announce...\",\n \"url\": \"https://...\",\n \"date\": \"2025-01-20\"\n }\n ],\n \"job_change_signal\": false,\n \"shared_connections\": [],\n \"interests\": [\"AI\", \"startups\", \"engineering leadership\"]\n },\n \"talking_points\": [\n \"Reference their recent Series B — congrats and ask about growth plans\",\n \"Mention mutual interest in AI/ML engineering\",\n \"Their tech stack (React/Node) aligns with your solution\"\n ],\n \"sources\": [\n \"https://linkedin.com/in/sarahchen\",\n \"https://twitter.com/sarahchen\",\n \"https://acmecorp.com/about\"\n ],\n \"confidence_score\": 0.88\n}" }, { "title": "Integration with Trawl", "body": "Lead Enrichment pairs perfectly with Trawl (autonomous lead gen):\n\n# Trawl finds leads, enrichment researches them\ntrawl sweep.sh # Discover leads\ntrawl leads.sh list --json | # Export qualified leads\n jq -r '.[] | \"\\(.name)|\\(.company)\"' |\n while IFS='|' read name company; do\n ./enrich.sh --name \"$name\" --company \"$company\"\n done\n\n# Or automate it via config:\n# trawl config: \"post_qualify_action\": \"enrich\"" }, { "title": "Tips", "body": "Email Discovery:\n\nWorks best when you provide company domain\nTries common patterns (first@company, f.last@company, etc.)\nMarks confidence level (high/medium/low)\nDoes NOT spam or verify via email sends (respects privacy)\n\nTalking Points:\n\nMost valuable when enrichment depth = \"deep\"\nRequires recent activity data (posts, news)\nAI analyzes content for personalization hooks\nStyle can be professional, friendly, or bold\n\nBatch Processing:\n\nUse --parallel for speed (3-5 concurrent recommended)\nProgress saved (resume if interrupted)\nFailed leads logged to batch-errors.json\n\nData Freshness:\n\nCached profiles expire after 30 days\nForce refresh with --refresh flag\nSocial activity always fetched fresh" }, { "title": "Use Cases", "body": "Sales Reps:\n\nResearch prospects before calls\nPersonalize cold email sequences\nFind mutual connections or interests\n\nRecruiters:\n\nAssess candidate backgrounds\nFind contact info for passive candidates\nCheck GitHub activity for technical roles\n\nPartnerships:\n\nResearch potential partners\nUnderstand company context\nFind the right contact person\n\nInvestors:\n\nQuick founder background checks\nCompany traction signals\nNetwork mapping" }, { "title": "Privacy & Ethics", "body": "This skill only uses publicly available data. It:\n\nRespects robots.txt and rate limits\nDoes NOT scrape private profiles or paywalled content\nDoes NOT send verification emails (won't spam your leads)\nDoes NOT store data if privacy.store_locally = false\nProvides source URLs for transparency\n\nBe a human: Just because you CAN enrich someone doesn't mean you should spam them. Use this for genuine, personalized outreach." }, { "title": "Data Storage", "body": "Enriched leads are stored at ~/.config/lead-enrichment/data/leads/:\n\n~/.config/lead-enrichment/\n├── config.json # User configuration\n├── data/\n│ ├── leads/ # Enriched profiles (one file per lead)\n│ │ ├── sarah-chen-acme.json\n│ │ └── john-smith-techco.json\n│ ├── cache/ # Temporary data (30-day expiry)\n│ └── batch-runs/ # Batch processing logs\n└── exports/ # Generated exports" }, { "title": "FAQ", "body": "Q: Is this legal?\nA: Yes. All data is publicly available. We respect robots.txt and rate limits.\n\nQ: How accurate are the emails?\nA: Pattern-based = 60-80% accuracy. Verified (if you add Hunter.io key) = 95%+.\n\nQ: Can I enrich 1000 leads?\nA: Yes via batch.sh. Expect ~30 sec per lead (deep mode). That's 8 hours for 1000. Run overnight.\n\nQ: Does this work for non-US leads?\nA: Yes. LinkedIn and Twitter are global. Some data sources are US-biased.\n\nQ: Will this get me blocked by LinkedIn?\nA: No. We use search (public), not scraping. Rate-limited and respectful." }, { "title": "What's Next", "body": "Ideas for future versions:\n\nChrome extension (enrich while browsing LinkedIn)\nCRM integrations (auto-enrich on lead create)\nSlack bot (enrich on-demand from Slack)\nEmail warmup integration (find + verify + warm sequence)\nMutual connection finder (via agent networks)\nReal-time alerts (when a lead changes jobs)\n\nStop researching. Start selling.\n\nFeed your agent a list of names. Get back a stack of dossiers. Personalize every message. Close more deals.\n\nThat's Lead Enrichment." } ], "body": "Lead Enrichment — Research Prospects in Seconds\n\nStop spending hours stalking LinkedIn. Let your agent do it.\n\nSales teams waste 6+ hours per week manually researching prospects. You Google their name, check LinkedIn, scroll their Twitter, hunt for their email, read their company's About page, search for recent news... and then do it all over again for the next lead.\n\nLead Enrichment automates all of it. Give your agent a name and company (or email, or LinkedIn URL), and get back a complete dossier: contact info, social profiles, bio, company intel, recent posts, news mentions, and AI-generated talking points.\n\nThe pain: Generic outreach gets ignored. Personalization takes forever. You're always behind quota.\n\nThe fix: Your agent researches 10 leads while you grab coffee. Rich profiles ready when you need them. Spend your time selling, not searching.\n\nWhat You Get\n\nFor each lead, the enrichment pulls:\n\nPersonal Profile:\n\nFull name, current title, company\nProfessional bio/summary\nProfile photo URL\nLocation\nSocial media handles (LinkedIn, Twitter, GitHub, personal site)\n\nContact Discovery:\n\nLikely email addresses (pattern-based + verification attempts)\nPublic phone numbers (if available)\nBest channels for outreach\n\nCompany Context:\n\nCompany description, industry, size\nFunding stage, recent news\nTech stack (for technical sales)\nKey decision makers\n\nIntelligence & Timing:\n\nRecent posts/articles (last 30 days)\nJob change signals\nCompany news mentions\nShared connections or interests\nConference/event participation\n\nAI-Generated Talking Points:\n\n3-5 personalized hooks based on their recent activity\nCommon ground opportunities\nRelevant pain points to address\nRecommended opening lines\nSetup\nRun scripts/setup.sh to initialize config\nEdit ~/.config/lead-enrichment/config.json with preferences\nNo API keys required for basic enrichment (uses public sources)\nOptional: Add premium data sources (see config)\nScripts\nScript\tPurpose\nscripts/setup.sh\tInitialize config and data directories\nscripts/enrich.sh\tEnrich a single lead (main script)\nscripts/batch.sh\tProcess multiple leads from CSV/JSON\nscripts/export.sh\tExport enriched leads (JSON/MD/CSV)\nUsage\nSingle Lead\n# By name + company\n./scripts/enrich.sh --name \"Sarah Chen\" --company \"Acme Corp\"\n\n# By email\n./scripts/enrich.sh --email \"sarah@acmecorp.com\"\n\n# By LinkedIn URL\n./scripts/enrich.sh --linkedin \"https://linkedin.com/in/sarahchen\"\n\n# Output to file\n./scripts/enrich.sh --name \"Sarah Chen\" --company \"Acme Corp\" --output sarah-chen.json\n\n# With talking points\n./scripts/enrich.sh --name \"Sarah Chen\" --company \"Acme Corp\" --talking-points\n\nBatch Processing\n# From CSV (columns: name, company, email, linkedin_url)\n./scripts/batch.sh --input leads.csv --output enriched/\n\n# From JSON array\n./scripts/batch.sh --input leads.json --output enriched/\n\n# Process with concurrency\n./scripts/batch.sh --input leads.csv --parallel 3\n\nExport Formats\n# Export as JSON (default)\n./scripts/export.sh --format json enriched/*.json > leads.json\n\n# Export as Markdown (readable)\n./scripts/export.sh --format markdown enriched/*.json > leads.md\n\n# Export as CSV (CRM import)\n./scripts/export.sh --format csv enriched/*.json > leads.csv\n\n# Pipe to your CRM\n./scripts/export.sh --format json enriched/*.json | \\\n curl -X POST https://your-crm.com/api/leads -d @-\n\nConfig\n\nConfig lives at ~/.config/lead-enrichment/config.json. See config.example.json for full schema.\n\nKey sections:\n\nenrichment.sources — Which data sources to check (all public by default):\n\nlinkedin — Public profiles via search\ntwitter — Social activity and bio\ngithub — For technical leads\ncompany_website — About pages, team directories\nnews — Recent mentions\ncrunchbase — Company funding (public data)\n\nenrichment.depth — How thorough to be:\n\nquick — Basic profile only (name, title, LinkedIn, company)\nstandard — Above + social profiles + recent activity (default)\ndeep — Above + news mentions + talking points + shared connections\n\noutput.format — Default output format (json/markdown/csv)\n\noutput.include — What to include in output:\n\ncontact_info — Email attempts, phone\nsocial_profiles — All discovered links\nrecent_activity — Posts, articles (last 30 days)\ncompany_intel — Company description, size, funding\ntalking_points — AI-generated personalization hooks\nraw_sources — Source URLs for verification\n\ntalking_points.enabled — Generate AI talking points (requires Claude)\n\ntalking_points.style — Tone for suggestions (professional/friendly/bold)\n\nprivacy.respect_robots — Skip profiles with clear \"no scraping\" signals\n\nprivacy.store_locally — Cache enriched profiles (default: true)\n\nData Sources\n\nAll sources are public and free:\n\nLinkedIn — Public profiles via search (no API, respects robots.txt)\nTwitter/X — Bio, recent tweets, follower count\nGitHub — For technical roles (repos, activity, README)\nCompany websites — Team pages, About sections\nGoogle News — Recent mentions\nCrunchbase — Public company data (no API key needed for basic info)\nCommon email patterns — firstname@company.com, f.lastname@company.com, etc.\n\nPremium sources (optional, requires API keys):\n\nHunter.io — Email verification\nClearbit — Enhanced company data\nApollo — Direct contact info\n\nAdd API keys to ~/.clawdbot/secrets.env if you have them. Enrichment works fine without them.\n\nOutput Schema\n\nEach enriched lead is saved as JSON:\n\n{\n \"lead_id\": \"sarah-chen-acme-corp\",\n \"enriched_at\": \"2025-01-29T10:30:00Z\",\n \"input\": {\n \"name\": \"Sarah Chen\",\n \"company\": \"Acme Corp\"\n },\n \"profile\": {\n \"full_name\": \"Sarah Chen\",\n \"title\": \"VP of Engineering\",\n \"company\": \"Acme Corp\",\n \"location\": \"San Francisco, CA\",\n \"bio\": \"Building the future of...\",\n \"photo_url\": \"https://...\",\n \"social_profiles\": {\n \"linkedin\": \"https://linkedin.com/in/sarahchen\",\n \"twitter\": \"https://twitter.com/sarahchen\",\n \"github\": \"https://github.com/sarahchen\",\n \"personal_site\": \"https://sarahchen.com\"\n }\n },\n \"contact\": {\n \"emails\": [\n { \"address\": \"sarah@acmecorp.com\", \"confidence\": 0.85, \"verified\": false },\n { \"address\": \"s.chen@acmecorp.com\", \"confidence\": 0.60, \"verified\": false }\n ],\n \"phones\": [],\n \"preferred_channel\": \"email\"\n },\n \"company\": {\n \"name\": \"Acme Corp\",\n \"domain\": \"acmecorp.com\",\n \"industry\": \"SaaS\",\n \"size\": \"51-200 employees\",\n \"description\": \"AI-powered...\",\n \"funding\": \"Series B ($25M)\",\n \"tech_stack\": [\"React\", \"Node.js\", \"AWS\"],\n \"recent_news\": [\n {\n \"title\": \"Acme Corp raises $25M...\",\n \"url\": \"https://...\",\n \"date\": \"2025-01-15\"\n }\n ]\n },\n \"intelligence\": {\n \"recent_activity\": [\n {\n \"type\": \"twitter_post\",\n \"content\": \"Excited to announce...\",\n \"url\": \"https://...\",\n \"date\": \"2025-01-20\"\n }\n ],\n \"job_change_signal\": false,\n \"shared_connections\": [],\n \"interests\": [\"AI\", \"startups\", \"engineering leadership\"]\n },\n \"talking_points\": [\n \"Reference their recent Series B — congrats and ask about growth plans\",\n \"Mention mutual interest in AI/ML engineering\",\n \"Their tech stack (React/Node) aligns with your solution\"\n ],\n \"sources\": [\n \"https://linkedin.com/in/sarahchen\",\n \"https://twitter.com/sarahchen\",\n \"https://acmecorp.com/about\"\n ],\n \"confidence_score\": 0.88\n}\n\nIntegration with Trawl\n\nLead Enrichment pairs perfectly with Trawl (autonomous lead gen):\n\n# Trawl finds leads, enrichment researches them\ntrawl sweep.sh # Discover leads\ntrawl leads.sh list --json | # Export qualified leads\n jq -r '.[] | \"\\(.name)|\\(.company)\"' |\n while IFS='|' read name company; do\n ./enrich.sh --name \"$name\" --company \"$company\"\n done\n\n# Or automate it via config:\n# trawl config: \"post_qualify_action\": \"enrich\"\n\nTips\n\nEmail Discovery:\n\nWorks best when you provide company domain\nTries common patterns (first@company, f.last@company, etc.)\nMarks confidence level (high/medium/low)\nDoes NOT spam or verify via email sends (respects privacy)\n\nTalking Points:\n\nMost valuable when enrichment depth = \"deep\"\nRequires recent activity data (posts, news)\nAI analyzes content for personalization hooks\nStyle can be professional, friendly, or bold\n\nBatch Processing:\n\nUse --parallel for speed (3-5 concurrent recommended)\nProgress saved (resume if interrupted)\nFailed leads logged to batch-errors.json\n\nData Freshness:\n\nCached profiles expire after 30 days\nForce refresh with --refresh flag\nSocial activity always fetched fresh\nUse Cases\n\nSales Reps:\n\nResearch prospects before calls\nPersonalize cold email sequences\nFind mutual connections or interests\n\nRecruiters:\n\nAssess candidate backgrounds\nFind contact info for passive candidates\nCheck GitHub activity for technical roles\n\nPartnerships:\n\nResearch potential partners\nUnderstand company context\nFind the right contact person\n\nInvestors:\n\nQuick founder background checks\nCompany traction signals\nNetwork mapping\nPrivacy & Ethics\n\nThis skill only uses publicly available data. It:\n\nRespects robots.txt and rate limits\nDoes NOT scrape private profiles or paywalled content\nDoes NOT send verification emails (won't spam your leads)\nDoes NOT store data if privacy.store_locally = false\nProvides source URLs for transparency\n\nBe a human: Just because you CAN enrich someone doesn't mean you should spam them. Use this for genuine, personalized outreach.\n\nData Storage\n\nEnriched leads are stored at ~/.config/lead-enrichment/data/leads/:\n\n~/.config/lead-enrichment/\n├── config.json # User configuration\n├── data/\n│ ├── leads/ # Enriched profiles (one file per lead)\n│ │ ├── sarah-chen-acme.json\n│ │ └── john-smith-techco.json\n│ ├── cache/ # Temporary data (30-day expiry)\n│ └── batch-runs/ # Batch processing logs\n└── exports/ # Generated exports\n\nFAQ\n\nQ: Is this legal? A: Yes. All data is publicly available. We respect robots.txt and rate limits.\n\nQ: How accurate are the emails? A: Pattern-based = 60-80% accuracy. Verified (if you add Hunter.io key) = 95%+.\n\nQ: Can I enrich 1000 leads? A: Yes via batch.sh. Expect ~30 sec per lead (deep mode). That's 8 hours for 1000. Run overnight.\n\nQ: Does this work for non-US leads? A: Yes. LinkedIn and Twitter are global. Some data sources are US-biased.\n\nQ: Will this get me blocked by LinkedIn? A: No. We use search (public), not scraping. Rate-limited and respectful.\n\nWhat's Next\n\nIdeas for future versions:\n\nChrome extension (enrich while browsing LinkedIn)\nCRM integrations (auto-enrich on lead create)\nSlack bot (enrich on-demand from Slack)\nEmail warmup integration (find + verify + warm sequence)\nMutual connection finder (via agent networks)\nReal-time alerts (when a lead changes jobs)\n\nStop researching. Start selling.\n\nFeed your agent a list of names. Get back a stack of dossiers. Personalize every message. Close more deals.\n\nThat's Lead Enrichment." }, "trust": { "sourceLabel": "tencent", "provenanceUrl": "https://clawhub.ai/audsmith28/lead-enrichment", "publisherUrl": "https://clawhub.ai/audsmith28/lead-enrichment", "owner": "audsmith28", "version": "1.1.0", "license": null, "verificationStatus": "Indexed source record" }, "links": { "detailUrl": "https://openagent3.xyz/skills/lead-enrichment", "downloadUrl": "https://openagent3.xyz/downloads/lead-enrichment", "agentUrl": "https://openagent3.xyz/skills/lead-enrichment/agent", "manifestUrl": "https://openagent3.xyz/skills/lead-enrichment/agent.json", "briefUrl": "https://openagent3.xyz/skills/lead-enrichment/agent.md" } }