find-email skill

The looot plugin's find-email command finds and verifies the work email of one person, or every person in a lead list.

find-email only loads when you run its command, /looot:find-email in Claude Code, with an argument: a name and a domain, a LinkedIn URL, or a file of leads.

What it does

1. If the looot tools are missing or answer 401, it follows the setup skill first.
2. It reads the input. For one person it needs first_name and last_name (or name) plus domain, or a linkedin_url. For a file, it reads every row and maps its columns to those names, asking the user only for what’s missing.
3. It follows “Enrich a lead list” in the recipes skill: quote the total, check balance, run job:people.email.find with fallback, then job:people.email.verify on each address found.
4. It answers with a table: person, email, verification status (valid, invalid, catch_all, risky or unknown), the provider that answered (servedProviderId), and the cost (actualCost). Pattern guesses (verdict: "guessed") are marked. It ends with the total spent.

Worked example

Command: /looot:find-email Jane Doe example.com

{
  "tool": "run",
  "input": {
    "endpointId": "job:people.email.find",
    "input": {"first_name": "Jane", "last_name": "Doe", "domain": "example.com"},
    "idempotencyKey": "find-email-jane-doe-example",
    "fallback": {"maxAttempts": 3, "maxCostUsd": 0.1}
  }
}

{
  "tool": "run",
  "input": {
    "endpointId": "job:people.email.verify",
    "input": {"email": "jane.doe@example.com"},
    "idempotencyKey": "verify-jane-doe-example",
    "fallback": true
  }
}

Agent’s answer:

“Total spent: $0.0245.”

For a list of people, the same flow runs once per row and the table gets one row each. See recipes for the full lead-enrichment steps and troubleshooting if a row comes back needs_input or miss.