agentleFS
galiprandigaliprandi/job-seeker/.agents/skills/referrals/SKILL.md

referrals

Skill136 starsChanged 3 days agoMITView on GitHub

Discovers internal contacts (1st/2nd degree connections, university alumni, ex-colleagues) and recruiters at target companies, stages personalized referral requests or outreach DMs in DB, and applies dynamic ATS micro-alignment (JD-to-CV tailoring).

25 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use marketing-council, marketing-loops and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • coreyhaines31Skill

    marketing-council

    When the user wants several expert takes on a marketing decision, or asks what a famous marketer would say about it: a simulated board (Seth Godin, David Ogilvy, April Dunford, Byron Sharp, and more), each grounded in their documented frameworks, where they disagree, and a recommendation. To execute, hand off to the relevant skill.

    Also in 12 projects that use this

  • martinbattaglia-commitsSkill

    marketing-loops

    When the user wants to set up a recurring, self-running marketing workflow — a repeatable loop an AI agent runs on a cadence (weekly, daily, on a trigger) rather than a one-off task. Also use when the user mentions 'marketing loop,' 'recurring marketing workflow,' 'automate my marketing,' 'marketing on autopilot,' 'weekly marketing review,' 'ad fatigue check,' 'content refresh loop,' 'churn watch,' 'ranking drop alert,' 'always-on marketing,' 'marketing automation workflow,' or 'run this every week.' Use this to pick, adapt, and schedule an ongoing marketing loop that orchestrates the other marketing skills. For one-off marketing ideas, see marketing-ideas. For the experimentation loop specifically, see ab-testing.

    Also in 9 projects that use this

  • aiunlocked1412Skill

    influencer-marketing

    Influencer marketing AI — brief, pitch, rate evaluation, performance review แบบ data-driven

    Also in 5 projects that use this

  • agenkinSkill

    events

    Schema discovery — list every event name firing for the current TelemetryDeck app with 7-day and 30-day counts side by side.

    Also in 6 projects that use this

  • riggyzSkill

    attribution

    Attribution rules for issues, pull requests, work items, reviews, and comments created or edited by the agent in GitHub, Linear, Azure DevOps, or similar collaboration systems. Use when creating, commenting on, reviewing, or modifying external tracker content.

    Also in 4 projects that use this

  • VercelSkill

    remotion-best-practices

    Best practices for Remotion - Video creation in React

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 22 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If an internal contact, alumni, or ex-colleague is found:

    line 50
  2. Very specific:

    Must pass Gold Rule 7 (Anti-LLM Checklist): no em-dashes, no bullet points, conversational tone, max 2 short paragraphs, natural mention of …

    line 54
  3. Distinctive:

    If NO internal referral path exists:

    line 67
  4. Very specific:

    Gate: if strategy.cold_outreach = false → skip this step.

    line 69
  5. Distinctive:

    Before submitting an application via ATS or email:

    line 77

“Common” is measured: kept by at least 6 in 10 of the 22 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

Warm Sourcing & Referrals

Trigger

Keyword: referrals (or variants: "warm sourcing", "buscar contactos", "solicitar referido")

The user says referrals or launches warm sourcing for a target company/role. Also executed as step 0 of the apply and targets flows to maximize conversion.

Flow

0. Pre-flight

  • Verify active browser session (see AGENTS.md "Browser session"): node .agents/skills/browser-automation/scripts/browser.js open <url> --headed (Gold Rule 5) if session closed
  • Load profile, university background, past companies, and job preferences from Postgres DB:
    node scripts/db.js "SELECT data->'profile' AS profile, data->'job_preferences' AS prefs, data->'style_profile' AS style FROM users WHERE id = <user_id>"
  • Load strategy (see AGENTS.md "Strategy levels"):
    node scripts/db.js "SELECT data->'strategy' AS strategy FROM users WHERE id = <user_id>"
    Respect: cold_outreach (gates the recruiter-outreach branch in step 3). If referrals is not in sources_active, the flow should not run standalone — when invoked as step 0 of apply/targets, those flows handle the gate.
  • Load active preferences (see memory skill):
    node scripts/db.js "SELECT category, key, value, confidence, source FROM preferences WHERE user_id = <user_id> AND status = 'active' ORDER BY category, key"

1. Warm Contact & Recruiter Discovery

For a target company and role:

# Automated discovery script
node scripts/linkedin-warm-sourcing.js --company "<Company>" --role "<Role>" --json

The script searches for:

  1. 1st & 2nd degree connections currently working at <Company>
  2. University alumni (matching institutions from users.data.profile.education)
  3. Ex-colleagues (matching past employers from users.data.profile.experience)
  4. Recruiters & Hiring Managers assigned to the role/company

2. Referral Request Staging (Highest Conversion — Strategy #1)

If an internal contact, alumni, or ex-colleague is found:

  1. Do NOT submit a cold application immediately. A referral yields a 40% hire rate vs 2-3% for cold Easy Apply.
  2. Draft a personalized referral request message:
    • Must pass Gold Rule 7 (Anti-LLM Checklist): no em-dashes, no bullet points, conversational tone, max 2 short paragraphs, natural mention of shared background (alumni/ex-colleague/interest).
    • Tone: polite, non-demanding, asking for team insights or guidance on applying.
  3. Stage the draft in DB:
    node scripts/db.js "INSERT INTO messages (user_id, channel, direction, sender, subject, body, draft, status, received_at, data) VALUES (<user_id>, 'linkedin', 'outbound', '<contact_name>', 'Solicitud de referido / consulta sobre equipo', '', '<draft_text>', 'draft', NOW(), '{\"category\": \"referral_request\", \"company\": \"<Company>\", \"vanity\": \"<vanity>\"}'::jsonb)" --write
  4. Register or update pipeline card in stage discovered:
    node scripts/pipeline.js --move <id> discovered

3. Recruiter Outreach Staging (Multi-channel Combo — Strategy #4)

If NO internal referral path exists:

  1. Gate: if strategy.cold_outreach = false → skip this step. Proceed to step 4 (ATS micro-alignment) and cold apply only.
  2. Extract the Recruiter / Hiring Manager profile vanity or email.
  3. Prepare a personalized recruiter DM outreach draft (3-4 lines: trigger + credibility anchor + clear ask).
  4. Stage the draft in DB (messages table with category: recruiter_outreach).
  5. Proceed to cold postulation via apply or targets while keeping the recruiter outreach staged for user approval (surfaced by news flow).

4. Dynamic ATS Micro-Alignment (JD-to-CV Tailoring)

Before submitting an application via ATS or email:

  1. Extract top 5 technical & domain keywords from the target Job Description (e.g., LangChain, System Architecture, PyTorch, Technical Leadership).
  2. Compare against users.data.profile.skills and users.data.cv_markdown.
  3. Highlight matching achievements in the top summary/highlights of the CV markdown.
  4. Generate the micro-aligned PDF CV using scripts/generate-cv.js before submitting:
    node scripts/generate-cv.js --output assets/cv_tailored_<company>.pdf

5. Presentation & Summary

Present the warm sourcing results to the user:

  • Internal contacts / Alumni found: list with profile URLs and proposed referral draft.
  • Recruiters found: list with proposed DM outreach draft.
  • Tailored CV generated: link to tailored PDF.

Dependencies

  • Depends on onboarding (DB to register)
  • Depends on profile (education & past experience data for alumni/ex-colleague matching)
  • Integrated into apply and targets flows

Script reference

scripts/linkedin-invite.js -- Send connection requests

Navigates to /preload/custom-invite/?vanityName=<vanity>, clicks "Send without a note". Anti-ban delay of 3s between invites.

# Invite one or more vanities
node scripts/linkedin-invite.js <vanity-name>

# Invite multiple
node scripts/linkedin-invite.js vanity1 vanity2 vanity3

# Search + invite in one command (pipe search -> invite)
node scripts/linkedin-invite.js --from-search '"<Role>" "hiring" <Region>'

Flags: --from-search "<keywords>" (searches and invites all found) Exit codes: 0 = at least one sent, 1 = all failed, 2 = error

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.