agentleFS
Sign inStart free
yih0nkyih0nk/job-hunt-agent/skills/recruit/SKILL.md

recruit

Skill0 starsChanged 56 days agoMITView on GitHub

Run the recruiting pipeline end to end (scout -> match -> apply -> track) and produce the daily report. Use when the user says "check for new roles", "run recruit", or on the daily schedule.

4 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 4

    1. superdesigndev/treg★ 7.7ksame name
    2. zubair-trabzada/ai-recruiter-claude★ 41same name
    3. tal7aouy/RecruitKit★ 3same name
    4. southglory/system-agents-template★ 2same 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 repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 3

    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:

    Never submit an application.

    line 43
  2. Distinctive:

    Never check "Applied" in the tracker without explicit user confirmation.

    line 44
  3. Distinctive:

    Only credit real experience.

    line 45

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

/recruit — recruiting pipeline orchestrator

Coordinates four agents. State lives in state/; personal config in config/*.yaml (gitignored). Nothing is ever submitted automatically — the Applier fills to the submit button and stops for review.

Flow

  1. Scout — agents/scout.md. Poll sources, diff, filter, queue new roles.
  2. Matcher — agents/matcher.md. Score each new role 0-100, pick a resume category, flag ineligible. Bucket by config/scoring.yaml thresholds.
  3. Applier — agents/applier.md. For auto_draft roles: resolve link, tailor resume (via the standing tailoring spec), draft answers, fill to the submit button, screenshot, stage under applications/. Hand off for accounts/CAPTCHAs.
  4. Tracker — agents/tracker.md. Update the board, detect recruiter replies, update pattern stats.

Output — the daily report

Recruiting — <date>
  Scanned N · passed filters M · NEW k
  Auto-drafted (awaiting your review): <company/role @ score> ...
  Review manually (55-69): ...
  Ineligible (gated): <company/role — gate> ...
  Recruiter activity: <replies / OA deadlines>
  Patterns: <most common ATS / question / etc.>
  Action needed from you: <accounts to create / packages to review + submit>

Modes

  • /recruit — full run + report.
  • /recruit scan — Scout + Matcher only (no drafting).
  • /recruit scan past day|week|N days — time-windowed scan via the listing Age column (poll-repo.py --max-age-days N --ignore-seen), then score. Use for ad-hoc "what's new in the last day" requests.
  • /recruit apply <company> — draft a package for one specific queued role.

Invariants

  • Never submit an application. Never create accounts or type passwords. Never solve CAPTCHAs.
  • Never check "Applied" in the tracker without explicit user confirmation.
  • Only credit real experience; delegate all resume tailoring to the spec.

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.

Check your setup, free