agentleFS
sameergdoggsameergdogg/job-search-skills/network-finder/SKILL.md

network-finder

Skill14 starsChanged 9 months agoMITView on GitHub

**Network & Referral Finder**: Searches the user's LinkedIn connections and a referral spreadsheet to find potential contacts at a target company. Use this skill whenever the user wants to find connections at a company, look for referrals, check if they know anyone at a company, or find a warm intro path. Trigger on mentions of "referral", "connection", "know anyone at", "warm intro", "network", "who do I know at", or any company name combined with intent to find contacts there.

The file

Show its rules and text

We split this skill into the rules it gives an agent

24 rules. About 0 are common, 19 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈19

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Before starting the workflow, check if config.yaml exists in the parent directory (one level up from this skill folder).

    line 13
  2. Distinctive:

    Ask for the required fields using AskUserQuestion:

    line 17
  3. Very specific:

    Write the responses to config.yaml in the parent directory

    line 22
  4. Distinctive:

    Read it silently and proceed.

    line 26
  5. Very specific:

    Read the URL from config.yaml → network.referral_sheet_url.

    line 32
  6. Distinctive:

    Use browser tools to open the spreadsheet, then search for the target company.

    line 37
  7. Distinctive:

    If the dialog says "no entries matching," the company isn't in the sheet

    line 41
  8. Distinctive:

    If found, close the dialog and read the matching row for referrer contact info and details

    line 42
  9. Very specific:

    Caching: If a local CSV copy exists at the workspace path and is less than 7 days old, search that first.

    line 44
  10. Distinctive:

    Search the user's LinkedIn network for people currently at the target company.

    line 48
  11. Very specific:

    Profile: Read from config.yaml → network.linkedin_profile_url

    line 50
  12. Distinctive:

    Read the search results to find connections at the target company

    line 56
  13. Distinctive:

    If no results with the exact company name, try common variations (e.g., "Block" vs "Block, Inc." vs "Square")

    line 58
  14. Distinctive:

    If a referral sheet is configured, search it first — these are the highest-value contacts because they're explicitly offering referrals.

    line 70
  15. Distinctive:

    If the company isn't found, note that clearly — "No referral found for [company] in your spreadsheet."

    line 78
  16. Distinctive:

    If no referral sheet is configured, skip this step and note: "No referral spreadsheet configured — searching LinkedIn only."

    line 80
  17. Distinctive:

    If there are results, present the top matches (up to 5).

    line 88
  18. Distinctive:

    If found: Referrer name, contact info, any special instructions, date posted

    line 98
  19. Distinctive:

    If referral found: "Reach out to [name] via [channel] — they're actively offering referrals"

    line 106
  20. Distinctive:

    If LinkedIn connection only: "You're connected to [name] — consider reaching out for an intro"

    line 107
  21. Distinctive:

    If neither: "No warm path found.

    line 108
  22. Distinctive:

    Privacy: Don't screenshot or save LinkedIn profile data beyond names and titles.

    line 112
  23. Distinctive:

    Referral sheet etiquette: If the spreadsheet has notes about referral conditions (e.g., can't refer if you already applied independently), …

    line 113
  24. Distinctive:

    Freshness matters: If a referral sheet entry is months old, flag that the referrer may have moved on.

    line 115

≈ “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

Network & Referral Finder

You help the user find warm intro paths to target companies by searching two sources: their LinkedIn connections and an optional referral/alumni spreadsheet.

First-Run Setup

Before starting the workflow, check if config.yaml exists in the parent directory (one level up from this skill folder). Read the user and network sections.

If config.yaml does NOT exist or the network.linkedin_profile_url field is empty:

  1. Tell the user: "This is your first time using network-finder. I need to set up your profile — this only happens once."
  2. Ask for the required fields using AskUserQuestion:
    • Their LinkedIn profile URL (required — this is the core data source)
    • Whether they have a referral/alumni spreadsheet (Google Sheet or other). If yes:
      • The spreadsheet URL
      • The column structure (e.g., "Column A = Name, Column B = Company, Column C = Notes")
  3. Write the responses to config.yaml in the parent directory
  4. Confirm setup is complete, then proceed

If config.yaml exists and has the required fields: Read it silently and proceed.

Data Sources

1. Referral Spreadsheet (Optional)

Read the URL from config.yaml → network.referral_sheet_url. If this field is blank, skip this source entirely.

The spreadsheet contains contacts who have offered referrals at their companies. Read the column structure from config.yaml → network.referral_sheet_structure.

Accessing the sheet: Use browser tools to open the spreadsheet, then search for the target company. The most reliable approach:

  1. Navigate to the spreadsheet URL
  2. Open Find and Replace via Edit menu > Find and replace (do NOT use Ctrl+F — it can get intercepted by cell edit mode in Google Sheets)
  3. Type the company name in the Find field and click "Find"
  4. If the dialog says "no entries matching," the company isn't in the sheet
  5. If found, close the dialog and read the matching row for referrer contact info and details

Caching: If a local CSV copy exists at the workspace path and is less than 7 days old, search that first. Otherwise, access the live sheet via browser. To create a cache, export via File > Download > CSV in the browser.

2. LinkedIn Connections

Search the user's LinkedIn network for people currently at the target company.

  • Profile: Read from config.yaml → network.linkedin_profile_url
  • Requires: The user must be logged into LinkedIn in the browser

Searching LinkedIn connections:

  1. Navigate to: https://www.linkedin.com/search/results/people/?keywords=COMPANY_NAME&network=%5B%22F%22%5D
    • The network=["F"] filter restricts results to 1st-degree connections only
  2. Read the search results to find connections at the target company
  3. For each match, note: name, current title, and LinkedIn profile URL
  4. If no results with the exact company name, try common variations (e.g., "Block" vs "Block, Inc." vs "Square")

Important: LinkedIn may show a login wall or rate-limit searches. If the page doesn't load properly, let the user know they may need to log in or try again later. Don't repeatedly retry — one attempt is enough.

Workflow

Step 1: Identify the Target Company

The user will mention a company name (e.g., "Do I know anyone at Airbnb?" or "Find me a referral at Stripe"). Extract the company name and any common aliases (e.g., "Google" / "Alphabet", "Meta" / "Facebook").

Step 2: Search Referral Spreadsheet

If a referral sheet is configured, search it first — these are the highest-value contacts because they're explicitly offering referrals.

Open the sheet in the browser, use Find to search for the company name. If found, read:

  • Who the referrer is
  • Their contact info
  • Any special instructions or notes
  • How recently the entry was updated

If the company isn't found, note that clearly — "No referral found for [company] in your spreadsheet."

If no referral sheet is configured, skip this step and note: "No referral spreadsheet configured — searching LinkedIn only."

Step 3: Search LinkedIn Connections

Navigate to the LinkedIn people search with the 1st-connection filter. Read the results:

  • Names and current titles of connections at the target company
  • How many 1st-degree connections are there

If there are results, present the top matches (up to 5). If no results, try one alternate name for the company before reporting no matches.

Step 4: Present Results

Format the output as a quick-reference card in the chat:

[Company Name] — Network Check

Referral Spreadsheet:

  • [Found/Not found/Not configured]
  • If found: Referrer name, contact info, any special instructions, date posted

LinkedIn 1st Connections:

  • [N] connections found
  • List each: Name — Title
  • Or: No 1st-degree connections found

Suggested Next Step:

  • If referral found: "Reach out to [name] via [channel] — they're actively offering referrals"
  • If LinkedIn connection only: "You're connected to [name] — consider reaching out for an intro"
  • If neither: "No warm path found. Consider a cold application or searching for 2nd-degree connections"

Important Notes

  • Privacy: Don't screenshot or save LinkedIn profile data beyond names and titles. This is just for the user's personal reference.
  • Referral sheet etiquette: If the spreadsheet has notes about referral conditions (e.g., can't refer if you already applied independently), include this context when relevant.
  • Speed over completeness: A quick answer ("yes, you have a referral path" or "no warm connections") is more valuable than an exhaustive search.
  • Freshness matters: If a referral sheet entry is months old, flag that the referrer may have moved on. Suggest verifying before reaching out.

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.