← Back to Skills Marketplace
zhyswan

LeadContact

by zhyswan · GitHub ↗ · v1.0.5 · MIT-0
linuxdarwinwin32 ⚠ suspicious
331
Downloads
0
Stars
0
Active Installs
6
Versions
Install in OpenClaw
/install leadcontact
Description
Query verified phone numbers and email addresses from LinkedIn profile URLs using LeadContact API. Find any contact's information with 98% accuracy.
README (SKILL.md)

When to Use

User needs to find phone numbers or email addresses from LinkedIn profiles. Agent uses LeadContact API to query contact information with 98% accuracy.

Quick Reference

Capability Description
Phone Lookup Find phone numbers from LinkedIn profile
Email Lookup Find verified emails from LinkedIn profile
Data Sources Cross-validated from multiple providers
Accuracy 98% verified accuracy

Authentication

All LeadContact API requests require an authentication token.

To get an API token:

Rate Limits: 500 requests per minute (can be increased on request)

API Endpoints

1. Find Phone Number

Query phone number information based on LinkedIn profile URL.

Endpoint: POST /api/v1/phone

Request Headers:

Authorization: Bearer YOUR_ACCESS_TOKEN
Content-Type: application/json

Request Body:

{
  "profileUrl": "https://www.linkedin.com/in/janedow/"
}

Response:

{
  "data": {
    "sources": [
      {
        "name": "leadcontact",
        "phone": "+12063994962",
        "valid": true
      }
    ]
  },
  "msg": "success",
  "code": 200
}

2. Find Email

Query email address information based on LinkedIn profile URL.

Endpoint: POST /api/v1/email

Request Headers:

Authorization: Bearer YOUR_ACCESS_TOKEN
Content-Type: application/json

Request Body:

{
  "profileUrl": "https://www.linkedin.com/in/janedow/"
}

Response:

{
  "data": {
    "sources": [
      {
        "name": "leadcontact",
        "email": "[email protected]",
        "valid": true
      }
    ]
  },
  "msg": "success",
  "code": 200
}

Error Codes

HTTP Status Error Code Description
400 40001 Invalid request parameters
401 40101 Missing token
401 40102 Invalid token
401 40103 Token expired
401 40104 Token disabled
404 - Endpoint not found

Usage Examples

Example 1: Find Phone Number

const response = await fetch('https://leadcontact.ai/api/v1/phone', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer YOUR_TOKEN',
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    profileUrl: 'https://www.linkedin.com/in/johndoe/'
  })
});
const data = await response.json();
console.log(data.data.sources[0].phone);

Example 2: Find Email

import requests

url = "https://leadcontact.ai/api/v1/email"
headers = {
    "Authorization": "Bearer YOUR_TOKEN",
    "Content-Type": "application/json"
}
data = {
    "profileUrl": "https://www.linkedin.com/in/johndoe/"
}

response = requests.post(url, json=data, headers=headers)
result = response.json()
email = result['data']['sources'][0]['email']
print(f"Found email: {email}")

Example 3: cURL

# Find phone number
curl -X POST https://leadcontact.ai/api/v1/phone \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"profileUrl": "https://www.linkedin.com/in/janedow/"}'

# Find email
curl -X POST https://leadcontact.ai/api/v1/email \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"profileUrl": "https://www.linkedin.com/in/janedow/"}'

Best Practices

  1. Always validate the profile URL - Ensure it's a valid LinkedIn profile URL
  2. Handle multiple sources - API may return multiple phone/email sources
  3. Check validation status - valid: true means verified contact info
  4. Respect rate limits - Max 500 requests/minute
  5. Store tokens securely - Never expose tokens in client-side code

Integration Tips

  • Use this skill with LinkedIn automation tools
  • Combine with CRM systems for automated contact enrichment
  • Integrate into sales outreach workflows
  • Use for recruitment lead generation

Product Info

Item Details
Website https://leadcontact.ai
Support Email [email protected]
WeChat Julia_LeadContact
WhatsApp +44 7962881367
Telegram @julia_gotleads
Data Coverage 120M+ emails, 60M+ phones, 270M+ decision makers
Usage Guidance
Before installing: (1) Confirm the skill really requires and will use a LEADCONTACT_API_TOKEN — the skill's internal files declare this but the top-level registry metadata you provided does not. That mismatch should be fixed by the publisher. (2) Verify the vendor (https://leadcontact.ai) and the recommended contact methods; prefer obtaining tokens through official vendor console or verified channels rather than messaging a phone/Telegram. (3) Consider privacy and legal issues: this skill queries personal contact info derived from LinkedIn profiles — ensure your use complies with LinkedIn's terms and local data protection laws. (4) Only provide an API token with least privilege, store it securely (not in client-side code), and monitor usage and billing. (5) If in doubt, run initial tests in a sandbox account and ask the publisher to publish repository/source or correct registry metadata before granting credentials.
Capability Analysis
Type: OpenClaw Skill Name: leadcontact Version: 1.0.5 The LeadContact skill is a standard API integration for a lead generation service (leadcontact.ai) designed to retrieve contact information from LinkedIn profiles. The bundle contains only metadata and documentation (SKILL.md) that instructs the AI agent on how to use the service's REST API; it lacks any executable code, suspicious dependencies, or instructions that would lead to data exfiltration or unauthorized behavior.
Capability Assessment
Purpose & Capability
The skill's stated purpose (look up phones/emails from LinkedIn profile URLs) matches the API endpoints and examples in SKILL.md. However, the top-level registry summary you provided lists no required credentials, while the included _meta.json and SKILL.md declare a required LEADCONTACT_API_TOKEN — an incoherence between the registry metadata and the skill's own manifest.
Instruction Scope
SKILL.md contains explicit instructions for calling leadcontact.ai endpoints with a bearer token and does not instruct the agent to read local files, config paths, or other system secrets. It does recommend using LinkedIn automation/CRM integrations (business/ethical implication), but functionally the runtime instructions stay within the claimed purpose (HTTP POST to an external API).
Install Mechanism
This is an instruction-only skill with no install spec and no bundled code, so nothing is written to disk and there are no package downloads. That reduces installation risk.
Credentials
The skill requires a single API credential (LEADCONTACT_API_TOKEN) according to _meta.json and SKILL.md, which is proportionate to the purpose. The concern is the mismatch between that requirement and the registry metadata you supplied (which lists no required env vars). Confirming which metadata is authoritative is important — you should not provide an API token unless you trust the vendor and the platform metadata is corrected. No other credentials are requested.
Persistence & Privilege
always:false and no special system paths or modifications are requested. The skill can be invoked autonomously (platform default) but it does not request persistent or elevated agent privileges beyond normal invocation.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install leadcontact
  3. After installation, invoke the skill by name or use /leadcontact
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.5
- No user-visible changes in this release. - Version bumped from 1.0.0 to 1.0.5 with no updates to documentation or code.
v1.0.4
- No changes detected from the previous version. - This version retains all existing features and documentation. - No updates to functionality, documentation, or configuration.
v1.0.3
- Added publisher, homepage, and privacy policy details to skill metadata. - No changes to API endpoints, usage, or functionality. - Documentation and usage instructions remain the same.
v1.0.2
- Added a required credential field for the LeadContact API authentication token (LEADCONTACT_API_TOKEN). - Improved contact details section for requesting an API token, now formatted in a clear, bulleted list. - Updated product info section to use a table format for easier readability. - No changes to core features or API usage.
v1.0.1
- Added additional contact methods for API token requests: WeChat (Julia_LeadContact), WhatsApp (+44 7962881367), and Telegram (@julia_gotleads). - Updated product info and support section to include WeChat, WhatsApp, and Telegram details.
v1.0.0
Initial release of LeadContact skill. - Query verified phone numbers and email addresses from LinkedIn profile URLs with 98% accuracy. - Supports endpoints to find phones and emails, cross-validated from multiple providers. - Includes sample requests in JavaScript, Python, and cURL. - Requires API token authentication, with clear error codes and usage guidelines. - Provides integration tips for sales, CRM, and lead generation workflows.
Metadata
Slug leadcontact
Version 1.0.5
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 6
Frequently Asked Questions

What is LeadContact?

Query verified phone numbers and email addresses from LinkedIn profile URLs using LeadContact API. Find any contact's information with 98% accuracy. It is an AI Agent Skill for Claude Code / OpenClaw, with 331 downloads so far.

How do I install LeadContact?

Run "/install leadcontact" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is LeadContact free?

Yes, LeadContact is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does LeadContact support?

LeadContact is cross-platform and runs anywhere OpenClaw / Claude Code is available (linux, darwin, win32).

Who created LeadContact?

It is built and maintained by zhyswan (@zhyswan); the current version is v1.0.5.

💬 Comments