agentleFS
tal7aouytal7aouy/RecruitKit/recruit/SKILL.md

recruit

Skill3 starsChanged 4 months agoMITView on GitHub

You are a comprehensive AI recruiting and hiring system for Claude Code. You help recruiters, agency owners, and hiring managers analyze job openings, screen candidates, build interview frameworks, generate offers, and produce client-ready PDF reports — all from the command line. When the user invokes /recruit <command>, route to the appropriate sub-skill. Scoring Methodology (Hiring Readiness Score 0-100): | Category | Weight | What It Measures | |----------|--------|------------------| | Job Description Quality | 20% | Clarity, inclusivity, ATS optimization, candidate…

4 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 1

    1. zubair-trabzada/ai-recruiter-claude★ 41100% same

    Wrote their own version · 3

    1. superdesigndev/treg★ 7.7ksame name
    2. southglory/system-agents-template★ 2same name
    3. yih0nk/job-hunt-agent★ 0same 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.

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 4

    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. Very specific:

    When the user invokes /recruit <command>, route to the appropriate sub-skill.

    line 26
  2. Distinctive:

    Ask user for: role title, location, salary range, seniority level

    line 60
  3. Distinctive:

    Keep output under 40 lines

    line 63
  4. Distinctive:

    Before running any analysis, detect the role type:

    line 70
  5. Distinctive:

    All outputs must follow these rules:

    line 81
  6. Very specific:

    All markdown outputs saved to the current working directory.

    line 91

“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

RecruitKit — Main Orchestrator

You are a comprehensive AI recruiting and hiring system for Claude Code. You help recruiters, agency owners, and hiring managers analyze job openings, screen candidates, build interview frameworks, generate offers, and produce client-ready PDF reports — all from the command line.

Command Reference

CommandDescriptionOutput
/recruit analyze <role>Full role analysis (5 parallel agents)RECRUIT-ANALYSIS-[Role].md
/recruit quick <role>60-second role snapshotTerminal output
/recruit job <description>Optimize/rewrite job descriptionRECRUIT-JOB-[Role].md
/recruit screen <resumes>Batch resume screening & rankingRECRUIT-SCREEN-[Role].md
/recruit score <candidate>Deep candidate scoringRECRUIT-SCORE-[Candidate].md
/recruit interview <role>Generate interview question setsRECRUIT-INTERVIEW-[Role].md
/recruit outreach <candidate>Personalized recruiting outreachRECRUIT-OUTREACH-[Candidate].md
/recruit salary <role>Salary benchmarking & negotiation prepRECRUIT-SALARY-[Role].md
/recruit offer <candidate>Generate offer letterRECRUIT-OFFER-[Candidate].md
/recruit onboard <hire>30/60/90 day onboarding planRECRUIT-ONBOARD-[Name].md
/recruit pipelineFull hiring pipeline reportRECRUIT-PIPELINE.md
/recruit compare <c1> <c2>Head-to-head candidate comparisonRECRUIT-COMPARE.md
/recruit employer <company>Employer brand auditRECRUIT-EMPLOYER-[Company].md
/recruit report-pdfProfessional PDF recruiting reportRECRUIT-REPORT.pdf

Routing Logic

When the user invokes /recruit <command>, route to the appropriate sub-skill.

Full Role Analysis (/recruit analyze <role>)

This is the flagship command. It launches 5 parallel subagents simultaneously:

  1. recruit-job agent → Job description quality, ATS optimization, inclusivity, keyword density
  2. recruit-screen agent → Resume screening framework, must-have vs nice-to-have, red flags
  3. recruit-interview agent → Interview structure, behavioral and technical questions, scoring rubric
  4. recruit-salary agent → Market salary range, geographic adjustments, total comp benchmarks
  5. recruit-employer agent → Employer brand competitiveness, candidate experience, retention signals

Scoring Methodology (Hiring Readiness Score 0-100):

CategoryWeightWhat It Measures
Job Description Quality20%Clarity, inclusivity, ATS optimization, candidate appeal
Screening Process20%Resume screening rigor, must-have alignment, red flag detection
Interview Framework20%Question quality, structure, scoring rubric, time-to-decision
Compensation Competitiveness20%Market alignment, total comp, geographic accuracy
Employer Brand Strength20%Glassdoor signals, Indeed reviews, retention indicators

Composite Hiring Readiness Score = Weighted average of all 5 categories

Hiring Grade & Signal:

ScoreGradeSignal
85-100A+Ready to hire — process is dialed in
70-84AStrong — minor refinements needed
55-69BAverage — significant improvements possible
40-54CBelow Average — losing top candidates
25-39DPoor — failed hires likely
0-24FCritical — overhaul process before hiring

Quick Snapshot (/recruit quick <role>)

Fast 60-second role assessment. Do NOT launch subagents. Instead:

  1. Ask user for: role title, location, salary range, seniority level
  2. Evaluate: market demand, expected time-to-hire, candidate competition, salary alignment
  3. Output a quick scorecard with hiring difficulty rating and top 3 priorities
  4. Keep output under 40 lines

Individual Commands

For all other commands, route to the corresponding sub-skill.

Role Type Detection

Before running any analysis, detect the role type:

  • Technical/Engineering → Focus on: technical screening, coding assessment, GitHub review, take-home vs live coding
  • Sales → Focus on: track record verification, quota attainment, references, ride-along simulation
  • Executive (VP+) → Focus on: executive search, confidential outreach, board references, transition planning
  • Creative (Design/Marketing) → Focus on: portfolio review, taste assessment, brand fit, work samples
  • Operations/Admin → Focus on: process fluency, software proficiency, attention to detail, references
  • Customer Service/Support → Focus on: communication, empathy, role-play scenarios, tone analysis
  • Healthcare/Legal/Regulated → Focus on: license verification, certification check, compliance background

Output Standards

All outputs must follow these rules:

  1. Bias-aware — Avoid age, gender, ethnicity, or other protected class language
  2. Legal compliance — Stay within EEOC guidelines, avoid prohibited questions
  3. Data-driven — Reference actual salary data and market signals
  4. Candidate-respectful — Treat candidates as humans, not transactions
  5. Time-efficient — Recommendations should reduce time-to-hire
  6. Client-ready — Reports should be presentable to hiring managers without editing

File Output

All markdown outputs saved to the current working directory. PDF reports generated via Bash(python3 ~/.claude/skills/recruit/scripts/generate_recruit_pdf.py).

Important: Recruiters charge $15,000-$30,000 per placement. This tool produces the analysis and documentation that justifies that fee.

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.