agentleFS
superagntsuperagnt/leverage/skills/core/lead-enrichment/SKILL.md

lead-enrichment

Skill6 starsChanged 2 months agoMITView on GitHub

Enrich people and companies from a name, domain, or LinkedIn URL — emails, titles, firmographics, and mobile numbers for agents.

  • Reads credentials
  • Sends data out

12 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If this client speaks MCP, you can connect the Lead Enrichment facet server instead of using this skill's curl calls — the same endpoints …

    line 30
  2. Distinctive:

    If the variable is not set, ask the user for their key or point them at https://superagnt.com/r/ch-lead-enrichment-key.

    line 56

“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Lead Enrichment

Turn a name, a domain, or a LinkedIn URL into a complete lead record in one call. The people endpoints resolve work emails, titles, seniority, location, and mobile numbers; the company endpoints add firmographics and context, and bulk variants process whole lists at once. Lookups run as an orchestrated waterfall across multiple data providers server-side, so the agent makes one call and gets the best available answer — no per-vendor accounts, no fallback logic to write. Built for sales agents that research before outreach, CRM-hygiene agents that fill gaps automatically, and prospecting pipelines that need reliable person-level data at scale.

Alternative install: the scoped MCP server

If this client speaks MCP, you can connect the Lead Enrichment facet server instead of using this skill's curl calls — the same endpoints below as native MCP tools with structured parameters and OAuth sign-in, scoped to this capability:

https://mcp.superagnt.com/mcp/lead-enrichment

That URL publishes full OAuth discovery: an MCP-capable client needs the URL and nothing else (approve once in the browser). On clients that hold a bearer instead, add it as an Authorization: Bearer header. Per-client setup lines: https://www.superagnt.com/install?facet=lead-enrichment

This skill document stays fully usable on curl-only environments — everything below works with just the API key.

Authentication

Get an API key from the superagnt app and export it as SUPERAGNT_API_KEY. Every request sends it as a Bearer token:

Authorization: Bearer $SUPERAGNT_API_KEY

If the variable is not set, ask the user for their key or point them at https://superagnt.com/r/ch-lead-enrichment-key.

Verify the install (do this first)

One call proves the key, the credit balance, and this source end to end:

curl -s https://api.superagnt.com/v1/credits \
  -H 'Authorization: Bearer $SUPERAGNT_API_KEY'

A JSON result means you are live. A 401 means the key is wrong or missing; a 402 means the workspace is out of credits — the superagnt app shows both.

Base URL

https://api.superagnt.com/v1/data/agnt

Available Endpoints

MethodPathSummary
POST/people/enrichEnrich a person
POST/people/bulk-enrichBulk enrich people
POST/people/searchSearch people
POST/people/find-mobileFind a mobile phone number
POST/people/email-finderFind a person's professional email
POST/companies/enrichEnrich a company

Tool Schemas

The following JSON defines every operation with its parameters. Each tool maps to an API endpoint under the base URL.

[
  {
    "name": "superagnt_agnt_people_enrich",
    "description": "Enrich a person",
    "method": "POST",
    "path": "/people/enrich",
    "parameters": {
      "$ref": "#/components/schemas/PeopleEnrichRequest"
    }
  },
  {
    "name": "superagnt_agnt_people_bulk_enrich",
    "description": "Bulk enrich people",
    "method": "POST",
    "path": "/people/bulk-enrich",
    "parameters": {
      "$ref": "#/components/schemas/PeopleBulkEnrichRequest"
    }
  },
  {
    "name": "superagnt_agnt_people_search",
    "description": "Search people",
    "method": "POST",
    "path": "/people/search",
    "parameters": {
      "$ref": "#/components/schemas/PeopleSearchRequest"
    }
  },
  {
    "name": "superagnt_agnt_people_find_mobile",
    "description": "Find a mobile phone number",
    "method": "POST",
    "path": "/people/find-mobile",
    "parameters": {
      "$ref": "#/components/schemas/PeopleFindMobileRequest"
    }
  },
  {
    "name": "superagnt_agnt_people_email_finder",
    "description": "Find a person's professional email",
    "method": "POST",
    "path": "/people/email-finder",
    "parameters": {
      "$ref": "#/components/schemas/PeopleEmailFinderRequest"
    }
  },
  {
    "name": "superagnt_agnt_companies_enrich",
    "description": "Enrich a company",
    "method": "POST",
    "path": "/companies/enrich",
    "parameters": {
      "$ref": "#/components/schemas/CompaniesEnrichRequest"
    }
  }
]

Example

curl -X POST 'https://api.superagnt.com/v1/data/agnt/people/enrich' \
  -H 'Authorization: Bearer $SUPERAGNT_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"...": "see tool schemas below"}'

Use Cases

Scope

This skill covers Lead Enrichment only — the endpoints listed above, nothing else. The same API key also works with superagnt's other data sources and platform tools, but those are separate listings that the user installs or enables themselves; this skill does not add or enable anything beyond what is documented here. The public catalog is at https://api.superagnt.com/v1/platforms.

Links

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.