agentleFS
sree-datasree-data/job-search-agent/.claude/skills/find-contacts/SKILL.md

find-contacts

Skill0 starsChanged 2 months agoMITView on GitHub

Identify the recruiter, hiring manager, team engineers, and any alumni or shared connections for a target company or job. Usage /find-contacts <company or job id>

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 you can't find anyone with confidence, say so.

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Find contacts

Argument: company name or job id.

Goal: 3 to 5 named people worth contacting for this role, with a reason for each. Save them to pipeline/contacts.csv.

How to find them (web search and web fetch only; do not use any browser tool on linkedin.com):

  • Recruiters: search "<company> technical recruiter" or "<company> talent acquisition data". Job postings sometimes name the recruiter. Company career pages sometimes list them.
  • Hiring managers: search "<company> data engineering manager", "<company> director data platform". Engineering blog authors and conference speakers are often the manager or a senior on the team.
  • Team engineers: authors of the company's data engineering blog posts, speakers at Snowflake/Databricks/Azure events, maintainers of the company's public repos.
  • Alumni: search "<company>" together with "Example State University", "ESU", "Fabrikam Motors", "Contoso Analytics", "Northwind Health". Shared employer or school is the hook. If Alex has told you about other shared things (hometown, undergrad school), use those too.

For each person record: name, title, type, LinkedIn URL if a public search result shows one, work email only if it is published somewhere (never guess an email pattern), where you found them, and the shared_hook — the one specific reason this person is worth writing to.

Priority order for who to write first: alumni or referral with a real shared hook > hiring manager for the exact team > engineer on the team > recruiter. Say which one you'd start with and why.

If you can't find anyone with confidence, say so. Alex can look them up on LinkedIn himself and paste the details into contacts.csv.

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.