agentleFS
superagntsuperagnt/leverage/skills/core/email-finder/SKILL.md

email-finder

Skill6 starsChanged 2 months agoMITView on GitHub

Find and verify work emails for prospects from a name and company — one call per lookup, and it never reads your inbox.

  • Reads credentials
  • Sends data out

1 other project uses 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. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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 Email Finder 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-email-finder-key.

    line 56

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Email Finder

Find a person’s work email from their name and company, verify any address before sending, or list the known addresses on a domain — three endpoints, one key. Lookups run as an orchestrated waterfall across multiple email data providers server-side: the agent makes one call and gets the best verified answer, with deliverability status attached. Built for outbound agents that need send-ready addresses, list-cleaning jobs that verify before a campaign, and enrichment flows that finish a lead record with a working email.

Alternative install: the scoped MCP server

If this client speaks MCP, you can connect the Email Finder 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/email-finder

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=email-finder

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-email-finder-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/email-finderFind a person's professional email
POST/people/email-verifierVerify a professional email
POST/companies/domain-emailsList a domain's emails

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_email_finder",
    "description": "Find a person's professional email",
    "method": "POST",
    "path": "/people/email-finder",
    "parameters": {
      "$ref": "#/components/schemas/PeopleEmailFinderRequest"
    }
  },
  {
    "name": "superagnt_agnt_people_email_verifier",
    "description": "Verify a professional email",
    "method": "POST",
    "path": "/people/email-verifier",
    "parameters": {
      "$ref": "#/components/schemas/PeopleEmailVerifierRequest"
    }
  },
  {
    "name": "superagnt_agnt_companies_domain_emails",
    "description": "List a domain's emails",
    "method": "POST",
    "path": "/companies/domain-emails",
    "parameters": {
      "$ref": "#/components/schemas/CompaniesDomainEmailsRequest"
    }
  }
]

Example

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

Use Cases

Scope

This skill covers Email Finder 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.