agentleFS
Hrutin-Suriya-KotniHrutin-Suriya-Kotni/until-hired/skills/networking/SKILL.md

networking

Skill2 starsChanged 3 days agoMITView on GitHub

Optional, off by default. Conversation-first networking on professional networks: find the people who hire for a role the candidate wants, read their recent post, and draft a short note that reacts to it, adds one line of real experience and asks one genuine question. Drafts only; the candidate sends them. No cold email, no lead lists, no bulk messaging. Use only when config.networking.enabled is true and the candidate asks for networking, referrals or 'who should I talk to at <company>'.

10 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 2

    Distinctive

    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:

    No cold email, no scraped email addresses, no lead lists, no bulk or automated sending.

    line 44
  2. Distinctive:

    No message that repeats across people.

    line 45

“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “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

Networking (optional, drafts only)

People answer curiosity about their own work. They ignore "can you refer me?" and "open to roles?". This skill writes a few good notes a day for the candidate to send by hand. It never sends anything and never builds lead lists.

When to use

  • config.networking.enabled is true, and
  • the candidate names a company or role they care about, or a company where they applied and heard nothing for 10+ days. At most config.networking.notes_per_day drafts a day (default 5).

1. Choose the person

  • The hiring manager for the role, the head of the team, or a senior engineer on it. A recruiter only if no one else is visible. At most 2 people per company, one at a time.
  • tracker.py contact-add --json <path> first ({"name", "company", "title", "channel", "url", "hook"}): exit 3 means already contacted; stop. Never the same person twice in 30 days.
  • Skip companies where the candidate is in an active interview process (they already have a channel).
  • Finding people: the candidate can look themselves (on LinkedIn: the company page → People → search "hiring", "engineering", the team name), or paste profile links. Don't automate searches or profile visits on networks whose terms forbid it.

2. Find a real hook

  • Their most recent substantive post (last 30 days), a talk, an interview, a blog post or a release they led. Open it and save the URL, the date and a one-line summary in your own words.
  • Nothing real → skip the person. Never invent or stretch what they said.

3. Draft the note (connection notes are often limited to about 200 characters)

Three parts, nothing else:

  1. Their point, specific, in your words.
  2. One line of the candidate's experience from FACTS.md that relates to it.
  3. One genuine question about their work. No "would love to connect", no "open to roles?", no praise words, no links. Check the length.

After they accept (only if they do): up to ~900 characters: thanks; respond to their answer if any; 2–3 related facts from FACTS.md; the specific open role and link if there is one; ask for 15 minutes or a pointer to the hiring manager.

4. Hand to the candidate

Show each draft with the hook link. They edit and send it themselves. Then: tracker.py contact-update --id N --status sent --next-on <date + 7 days>; on accept/reply update the status (accepted, replied, call, referral, no-reply). One follow-up at most.

5. Measure

In the weekly review: notes sent, accepted, replied, calls, referrals. If fewer than 1 in 10 replies after 20 notes, change the hooks or stop; the candidate decides.

Never

  • No cold email, no scraped email addresses, no lead lists, no bulk or automated sending.
  • No message that repeats across people.
  • Nothing about a person that isn't public and relevant to their work.

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.