/find-contact, find a real human
Usage: /find-contact Space42
The most useful output of this skill is sometimes "no verifiable address exists, here is the better route instead". A guessed address bounces, and a bounce from a personal Gmail damages every future email to that domain.
Steps
Read the dossier at shared/companies/<slug>.md. It already names the team worth targeting.
Delegate to the contact_finder agent. Its seniority ladder, source list and rating rules are the method.
Target the right level. An engineering manager or team lead on the relevant team, first. A senior engineer on that team, second — they cannot hire but they forward, and internal forwards work. A head of engineering only at small companies. careers@ last, and expect nothing from it.
Verify the address against a published source. Papers with correspondence addresses, conference speaker pages, the company's own team page, GitHub, personal sites. Record the URL.
Rate it, and do not upgrade the rating hopefully. verified means seen published. pattern means guessed from a company convention. unverified means guessed. Only verified may be sent to.
Check the person still works there, and record the date of the evidence.
When nothing verifies, name the best alternative — LinkedIn message, contact form, or an introduction through a mutual connection — and say why the direct route failed.
Append to the dossier in the format in agents/contact_finder.md, and update the person's tracker.md row.
Output format
## Contact found: <company>
**Primary**
<name> · <title> (as of YYYY-MM) · <email>
Verification: verified | pattern | unverified
Source: <URL>
Still there: <evidence, date>
Why them: <one line>
**Backup:** <name and details, or none found>
**If unverified**
Best route: <alternative>
Why the direct route failed: <one line>
**Sendable?** yes | no — <reason>
**Next:** /cold-email <person> <company>
Rules
- Never fabricate a name, a title or an address.
- Never present a pattern-guess as found.
- One primary contact per company. A list of five people is a spray plan, not a contact.
- No scraping, no bulk enrichment tools, no paid address databases. Individually found, publicly published sources only.
- Addresses stay in this repo. Never into the Hermes vault, never into a public remote.
- If the only reachable route is
careers@, say so — that is a signal to use the company's formal process and write the email differently.
1---2name: find-contact3description: Find a named human to email at a target company plus a verifiable address, and rate the confidence honestly. Use after a company dossier exists and before any draft is written. Also use when a first contact went nowhere and a different person is being considered.4---56# /find-contact, find a real human78Usage: `/find-contact Space42`910The most useful output of this skill is sometimes "no verifiable address exists, here is the better route instead". A guessed address bounces, and a bounce from a personal Gmail damages every future email to that domain.1112## Steps13141. **Read the dossier** at `shared/companies/<slug>.md`. It already names the team worth targeting.15162. **Delegate to the `contact_finder` agent.** Its seniority ladder, source list and rating rules are the method.17183. **Target the right level.** An engineering manager or team lead on the relevant team, first. A senior engineer on that team, second — they cannot hire but they forward, and internal forwards work. A head of engineering only at small companies. `careers@` last, and expect nothing from it.19204. **Verify the address against a published source.** Papers with correspondence addresses, conference speaker pages, the company's own team page, GitHub, personal sites. Record the URL.21225. **Rate it, and do not upgrade the rating hopefully.** `verified` means seen published. `pattern` means guessed from a company convention. `unverified` means guessed. Only `verified` may be sent to.23246. **Check the person still works there,** and record the date of the evidence.25267. **When nothing verifies, name the best alternative** — LinkedIn message, contact form, or an introduction through a mutual connection — and say why the direct route failed.27288. **Append to the dossier** in the format in `agents/contact_finder.md`, and update the person's `tracker.md` row.2930## Output format3132```33## Contact found: <company>3435**Primary**36<name> · <title> (as of YYYY-MM) · <email>37Verification: verified | pattern | unverified38Source: <URL>39Still there: <evidence, date>40Why them: <one line>4142**Backup:** <name and details, or none found>4344**If unverified**45Best route: <alternative>46Why the direct route failed: <one line>4748**Sendable?** yes | no — <reason>49**Next:** /cold-email <person> <company>50```5152## Rules5354- Never fabricate a name, a title or an address.55- Never present a pattern-guess as found.56- One primary contact per company. A list of five people is a spray plan, not a contact.57- No scraping, no bulk enrichment tools, no paid address databases. Individually found, publicly published sources only.58- Addresses stay in this repo. Never into the Hermes vault, never into a public remote.59- If the only reachable route is `careers@`, say so — that is a signal to use the company's formal process and write the email differently.
Faaz17