contact-sourcer
Skill16 starsChanged 49 days agoApache-2.0View on GitHub
Source people at target companies (capability people_search) and write them to storage at stage 'sourced'. Runs the configured people_search waterfall, backfills domains, dedups, and cross-references the master DB. Use when the user wants to "source contacts", "find people at these companies", or run only the sourcing stage.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- activateSkill
- company-discoverySkill
- company-enricherSkill
- contact-qualifierSkill
- email-finderSkill
- gtm-setupSkill
- gtmSkill
- phone-finderSkill
The file
Files
Input (companies + persona/titles + geography, and optionally an existing list_id): $ARGUMENTS
Execute the contact sourcer: read agents/contact-sourcer/agent.md and follow it
exactly — bootstrap (config + context + resolve the people_search waterfall from keyed
providers), source per provider via their manifests, backfill domains, dedup +
crossref_master, then write via storage/cli.py (create_list if needed, upsert_contacts).
Report the waterfall table and the resulting list_id.
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
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.

