agentleFS
sami2919sami2919/SignalForce/skills/contact-finder/SKILL.md

contact-finder

Skill9 starsChanged 3 months agoMITView on GitHub

Use when needing to find verified email addresses and LinkedIn profiles for decision-makers at target accounts, or when performing waterfall enrichment across multiple data providers

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

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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 no verified email found after full waterfall: output LinkedIn URL and flag for manual connection request.

    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

Contact Finder

Input

Company name + domain. Target title(s) — default to priority order from config/gtm-context.md:

  1. Head of ML / Director of ML / VP ML
  2. Head of AI / VP AI
  3. Principal / Staff ML Engineer
  4. VP Engineering / CTO (companies ≤100 employees)
  5. Domain-specific senior IC roles (see config/gtm-context.md for ICP-specific titles)

Waterfall Enrichment

Work top-to-bottom. Stop at first verified result per contact.

Step 1: Apollo.io

  • API: POST https://api.apollo.io/v1/people/search with person_titles + organization_domains
  • Manual: apollo.io → Search → People → filter by domain + title

Step 2: Hunter.io

  • API: GET https://api.hunter.io/v2/domain-search?domain={domain}&type=personal
  • Manual: hunter.io → Domain Search

Step 3: Prospeo

  • API: POST https://api.prospeo.io/linkedin-email-finder with LinkedIn URL
  • Manual: prospeo.io → LinkedIn Email Finder → paste profile URL

Step 4: PeopleDataLabs

  • API: GET https://api.peopledatalabs.com/v5/person/enrich?work_email={email}
  • Manual: pdl.com → Enrichment

Step 5: ZeroBounce Validation (always run on final email)

  • API: GET https://api.zerobounce.net/v2/validate?email={email}
  • Statuses to accept: valid. Reject: invalid, catch-all, unknown.

Output

## Contacts — [Company Name]

| Name | Title | Email | Source | Status |
|------|-------|-------|--------|--------|
| ...  | ...   | ...   | Apollo | valid  |

**LinkedIn Profiles:**
- [Name]: [URL]

**Enrichment gaps:** [any titles not found, note for manual outreach via LinkedIn]

If no verified email found after full waterfall: output LinkedIn URL and flag for manual connection request.

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.