agentleFS
delmarstudiosdelmarstudios/job-search-skills/skills/job-outreach/SKILL.md

job-outreach

Skill0 starsChanged 19 days agoMITView on GitHub

Draft short recruiter and hiring-manager outreach (LinkedIn connection note, LinkedIn message or email, follow-up) for a job application, to raise response rates. Use for top-fit roles once materials are ready, when the candidate asks for outreach or a follow-up, or when a posting names a recruiter or hiring manager.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. AkbarDevop/ai-job-agent★ 61same name
    2. wexxwuther/job-hunter★ 4same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write in the language the contact or company works in.

    line 29
  2. Very specific:

    Run job-fact-check on the drafts.

    line 32

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

Recruiter and hiring-manager outreach

Goal: turn an application into a conversation. Produce drafts only. The candidate sends every message personally; never sign in, connect, send or message anyone.

1. Inputs

  • The role's tracker row (company, role, URL, fit, gaps) and its saved JD.
  • The candidate's facts file and config (config/candidate.json).

2. Find who to contact (public information only)

In order: the person named in the posting; the hiring manager implied by the reporting line, found on the company site or a public web search; the regional recruiting lead. Record name, title and the public URL where you found them. If nobody can be identified with confidence, address "the hiring team" and say so. Never guess a name or an email address.

3. Write

Plain and specific: no flattery, no clichés, no emoji. Lead with the role and one concrete overlap from the candidate's real experience, state that the application is in and when they can start, and end with one small ask.

  • Connection note (≤ 300 characters including spaces): Hi {Name}, I've applied for the {Role} role at {Company}. I spent {N} years in {field} at {employers}, including {one overlap}. Would be glad to connect.
  • Message or email (≤ 120 words; email subject {Role} application – {Candidate name}):
    1. One line: applied for {Role}; the JD need it matches.
    2. Two lines: the single most relevant result from the facts file, with its real number.
    3. One line: availability and location from the config.
    4. "Happy to share more if useful." Name and LinkedIn from the config.
  • Follow-up (7–10 days after applying with no reply, ≤ 70 words): role and application date, one new relevant fact not used before, one-line ask.

Write in the language the contact or company works in; offer a second language version when unsure.

4. Check and save

Run job-fact-check on the drafts. Save them to the role's output folder as outreach.md, with the contact's name, title and source URL at the top. If the tracker has a follow-up date column, set it to 7 days after the applied date when empty.

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.