Referrals logo

Referrals

Community
galiprandi
referrals

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).

Overview

Publishergaliprandi
Repositoryjob-seeker
Skill namereferrals
Stars
68
Forks
11
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by galiprandi on GitHub. Read the source before you install it.

Installation

Install the Referrals AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/galiprandi/job-seeker/tree/main/.agents/skills/referrals
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/galiprandi/job-seeker.git /tmp/job-seeker
mkdir -p .claude/skills
cp -r /tmp/job-seeker/.agents/skills/referrals .claude/skills/referrals
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Referrals in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Referrals on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Referrals is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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:
    bash
    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"):
    bash
    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):
    bash
    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:

bash
# 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:
    bash
    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:
    bash
    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:
    bash
    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.

bash
# 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

Frequently asked questions

What does the Referrals AI skill do?

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).

Why use Referrals on TypingMind?

Because you install it once and use it with any model. Referrals is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Referrals in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/galiprandi/job-seeker/tree/main/.agents/skills/referrals. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Referrals?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Referrals?

As many as you like. As long as a model supports skills, you can use Referrals with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Referrals AI skill free?

Yes. It is published on GitHub by galiprandi under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇