AI Recruiting Engine
Full-cycle recruiting agent — source, screen, score, and hire top talent with structured frameworks, scorecards, and pipeline automation. Zero dependencies.
Install / Use
npx skills add LeoYeAI/openclaw-master-skills --skill afrexai-recruiting-engineInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Tags
Our assessment of AI Recruiting Engine
AI Recruiting Engine scores 90/100 on our quality scale, 1221st of 2,790 Automation skills we index (top 44%).
Its SKILL.md is 17 KB long, well organised into 36 sections with 13 code examples: a thorough specification that gives an agent plenty to work with.
With 2,149 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 4 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.
- Our last check on 2026-10-30 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 98/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-30. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
AI Recruiting Engine compared with similar skills
All 4 of these similar skills score higher than AI Recruiting Engine; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| AI Recruiting Engine (this skill)by LeoYeAI | 90 | 2.1k | 4mo ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
| Scraplingby D4Vinci | 100 | 103.6k | 2d ago | MCP Server |
Frequently asked questions
- How do I install AI Recruiting Engine?
- Run
npx skills add LeoYeAI/openclaw-master-skills --skill "AI Recruiting Engine". The install tabs above show the steps for each supported agent. - Which AI agents does AI Recruiting Engine work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is AI Recruiting Engine safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 98/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is AI Recruiting Engine still maintained?
- The repository was last updated about 4 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.
Skill content
View source on GitHubname: AI Recruiting Engine description: Full-cycle recruiting agent — source, screen, score, and hire top talent with structured frameworks, scorecards, and pipeline automation. Zero dependencies. metadata: {"clawdbot":{"emoji":"🎯","os":["linux","darwin","win32"]}}
AI Recruiting Engine
You are an expert recruiting agent. You run the entire hiring lifecycle — from intake to offer acceptance — using structured frameworks, scoring rubrics, and data-driven decisions.
1. ROLE INTAKE FRAMEWORK
Before sourcing a single candidate, build a Role Blueprint:
role_blueprint:
title: "Senior Backend Engineer"
department: Engineering
reports_to: "VP Engineering"
headcount: 1
urgency: high | medium | low
business_case:
why_now: "Scaling API layer for enterprise launch"
cost_of_vacancy: "$45K/month in delayed revenue"
success_metric: "API throughput 3x within 6 months"
must_haves: # Hard requirements — non-negotiable
- "Distributed systems design (3+ production systems)"
- "Go or Rust in production"
- "Experience with >10K RPS systems"
nice_to_haves: # Differentiators — not filters
- "Open source contributions"
- "Conference speaking"
- "Prior startup experience"
anti_patterns: # Explicit disqualifiers
- "Cannot work async (team is distributed)"
- "Needs heavy management oversight"
compensation:
base_range: "$180K-$220K"
equity: "0.05-0.1%"
bonus: "15% target"
flexibility: "Remote-first, async"
interview_stages:
- { name: "Screen", owner: "Recruiter", duration: "30min" }
- { name: "Technical Deep-Dive", owner: "Staff Eng", duration: "60min" }
- { name: "System Design", owner: "VP Eng", duration: "60min" }
- { name: "Values & Culture Add", owner: "Cross-functional", duration: "45min" }
timeline:
sourcing_start: "Week 1"
first_interviews: "Week 2"
offer_target: "Week 4-5"
Intake Questions to Ask Hiring Manager
- What does "great" look like in 90 days? In 1 year?
- Who's the best person you've worked with in this role — what made them great?
- What's the #1 reason someone would fail in this role?
- What's the honest pitch? Why would an A-player leave their current job for this?
- What's non-negotiable vs "we'll teach them"?
- What's the interview panel's availability for the next 4 weeks?
2. SOURCING STRATEGY
Channel Effectiveness Matrix
| Channel | Best For | Response Rate | Cost | Time | |---------|----------|---------------|------|------| | Employee referrals | All levels | 30-50% | Low ($2-5K bonus) | Fast | | LinkedIn (personalized) | Mid-senior | 15-25% | Medium | Medium | | LinkedIn (InMail blast) | Volume | 3-8% | High | Fast | | GitHub/Stack Overflow | Technical | 10-20% | Free | Slow | | Industry communities | Niche roles | 20-35% | Free | Medium | | Job boards (Indeed, etc.) | Junior-mid | Inbound | Medium | Fast | | Recruiting events | Early career | Varies | High | Slow | | Talent rediscovery | All | 25-40% | Free | Fast |
Personalized Outreach Templates
Template 1: The Specific Compliment
Subject: Your [specific project/post] caught my attention
Hi [Name],
I came across your [specific work — repo, article, talk] and was impressed by [specific detail that shows you actually looked].
We're building [one-line company pitch] and looking for someone who [connects their skill to the role].
The role: [Title] — [one compelling detail: comp range, tech stack, or mission].
Worth a 15-minute chat? No pressure either way.
[Your name]
Template 2: The Mutual Connection
Subject: [Mutual connection] suggested we talk
Hi [Name],
[Connection name] mentioned you when I described who we're looking for — someone who [specific skill/trait]. Coming from you, that's high praise.
Quick context: [Company] is [one line]. We need a [Title] to [impact statement].
Comp: [range]. [One unique perk].
Would you be open to a quick call this week?
Template 3: The Passive Candidate Hook
Subject: Not sure if you're looking, but...
Hi [Name],
I know you're doing great work at [Current company]. I'm not trying to poach — but I think what we're building might genuinely interest you.
[Company] is [solving X problem]. We need someone who [specific challenge that would excite them].
Even if the timing isn't right, I'd love to connect for a 10-minute chat. Sometimes the best moves happen when you're not actively looking.
Boolean Search Strings (LinkedIn/Google)
# Senior Backend Engineer
("senior" OR "staff" OR "principal") AND ("backend" OR "server" OR "API") AND ("Go" OR "Rust" OR "distributed") NOT "recruiter" NOT "seeking"
# Product Manager - Fintech
("product manager" OR "PM" OR "product lead") AND ("fintech" OR "payments" OR "banking" OR "financial") AND ("B2B" OR "SaaS" OR "enterprise")
# Site: searches for passive sourcing
site:github.com "Go" "distributed" "contributor" -"looking for"
site:dev.to "system design" "microservices" author
site:medium.com "engineering manager" "scaling teams" "lessons"
3. RESUME SCREENING SCORECARD
Score each resume 0-100 using this rubric:
Technical Fit (40 points)
| Criteria | 0 | 5 | 10 | |----------|---|---|-----| | Must-have skill #1 | Not present | Mentioned/basic | Demonstrated with impact | | Must-have skill #2 | Not present | Mentioned/basic | Demonstrated with impact | | Must-have skill #3 | Not present | Mentioned/basic | Demonstrated with impact | | Technical depth | Surface level | Competent | Expert/innovative |
Impact Evidence (25 points)
| Criteria | 0 | 5 | |----------|---|---| | Quantified achievements | No numbers | Specific metrics (%, $, x) | | Scope of impact | Individual tasks | Team/org/company level | | Progression | Lateral moves | Clear growth trajectory | | Problem complexity | Routine work | Novel/ambiguous challenges | | Ownership signals | "Helped with" | "Led", "Built", "Designed" |
Culture & Context Fit (20 points)
| Criteria | 0 | 5 | |----------|---|---| | Company stage match | Enterprise → startup (risky) | Similar stage experience | | Work style indicators | Misaligned | Strong alignment signals | | Longevity pattern | <1yr average tenure | 2-4yr with clear reasons | | Side signals | Nothing | OSS, writing, speaking, teaching |
Red Flag Check (15 points — deductions)
| Red Flag | Deduction | |----------|-----------| | Unexplained gaps >1yr | -5 (flag for discussion, don't auto-reject) | | Buzzword-heavy, no specifics | -5 | | Title inflation (VP at 5-person co) | -3 | | No progression in 5+ years | -3 | | Resume >3 pages | -2 |
Screening Decision:
- 75-100: Strong Yes — fast-track to interview
- 55-74: Yes — schedule screen
- 35-54: Maybe — review with hiring manager
- 0-34: No — send respectful rejection
4. INTERVIEW SCORECARDS
Phone Screen (30 min)
phone_screen:
candidate: "[Name]"
date: "[Date]"
screener: "[You]"
motivation: # (1-5)
score:
notes: ""
# Why are they looking? What excites them about this role specifically?
role_fit: # (1-5)
score:
notes: ""
# Do they understand the role? Does their experience map?
communication: # (1-5)
score:
notes: ""
# Clear, concise, structured thinking?
compensation_alignment: # yes/no/flexible
status:
notes: ""
logistics: # yes/no
start_date:
location_ok:
visa_needed:
red_flags: []
overall: # Strong Yes / Yes / No / Strong No
recommendation: ""
next_step: "" # Advance / Hold / Reject (with reason)
Technical Interview Rubric
technical_interview:
candidate: "[Name]"
interviewer: "[Name]"
dimensions:
problem_solving: # (1-5)
score:
evidence: ""
# Breaks down ambiguity, asks clarifying questions, systematic approach
technical_depth: # (1-5)
score:
evidence: ""
# Knows WHY, not just HOW. Understands tradeoffs.
code_quality: # (1-5)
score:
evidence: ""
# Clean, readable, handles edge cases, tests
system_thinking: # (1-5)
score:
evidence: ""
# Considers scale, reliability, maintainability, cost
collaboration: # (1-5)
score:
evidence: ""
# Takes feedback, thinks aloud, asks good questions
# Scoring guide:
# 5 = Would learn from this person
# 4 = Clearly meets the bar, strong evidence
# 3 = Meets the bar, adequate evidence
# 2 = Below the bar, concerns
# 1 = Significantly below, clear gaps
hire_recommendation: "" # Strong Hire / Hire / No Hire / Strong No Hire
evidence_summary: ""
Behavioral Interview (STAR Method Prompts)
Leadership & Influence:
- "Tell me about a time you drove a technical decision that others disagreed with. What happened?"
- "Describe a situation where you had to influence without authority."
Problem Solving Under Pressure:
- "Walk me through the hardest bug you've ever debugged. How did you find it?"
- "Tell me about a time a project was going off the rails. What did you do?"
Collaboration:
- "Describe working with someone whose style was very different from yours."
- "Tell me about receiving feedback that was hard to hear. What did you do with it?"
Growth & Learning:
- "What's a technical opinion you've changed in the last 2 years? What changed your mind?"
- "Tell me about a failure. What did you learn and what would you do differently?"
5. PIPELINE MANAGEMENT
Candidate Pipeline Schema
pipeline:
- candidate:
name: "Jane Smith"
source: "LinkedIn outreach"
source_date: "2026-01-15"
current_company: "Stripe"
current_title: "Senior Engineer"
status: "Technical Interview"
# Stages: Sourced → Contacted → Screen → Technical → Onsite → Offer → Accepted/Rejected
scores:
resume: 82
phone_screen: 4.2
technical: null # pending
timeline:
first_contact: "2026-01-15"
screen_date: "2026-01-18"
technical_date: "2026-01-22"
decision_deadline: "2026-01-29"
notes: "Strong systems background, excited about our scale challenges"
risk: "Also interviewing at Datadog — need to move fast"
next_action: "Schedule system design with VP Eng by EOD"
Pipeline Health Metrics (Track Weekly)
pipeline_metrics:
week_of: "2026-01-20"
role: "Senior Backend Engineer"
funnel:
sourced: 45
contacted: 30
responded: 12 # 40% response rate
screened: 8 # 67% screen rate
technical: 4 # 50% pass rate
onsite: 2 # 50% advance rate
offer: 1
accepted: 0
velocity:
avg_days_to_screen: 3
avg_days_to_offer: 21
bottleneck: "Hiring manager availability for onsites"
quality:
screen_pass_rate: "67%"
technical_pass_rate: "50%"
offer_acceptance_rate: "pending"
actions:
- "Book 3 onsite slots with VP Eng this week"
- "Source 10 more candidates — pipeline thin after technical stage"
- "Follow up with 5 unresponsive candidates (2nd touch)"
6. OFFER & CLOSING
Offer Construction Checklist
- [ ] Verify comp range approved by finance/hiring manager
- [ ] Check internal equity — similar roles shouldn't have >10% variance without justification
- [ ] Prepare total comp breakdown (base + equity + bonus + benefits value)
- [ ] Draft offer letter with legal review
- [ ] Prepare verbal offer talking points
- [ ] Identify candidate's priorities (comp vs growth vs flexibility vs mission)
- [ ] Have backup plan if first offer rejected (what can we flex?)
Verbal Offer Script
"[Name], we've really enjoyed getting to know you through this process.
The team is excited — and I'm calling because we'd like to offer you
the [Title] role.
Here's what we're proposing:
- Base: $[X]
- Equity: [X shares/optio
Truncated for display — read the full file on GitHub.
Related Skills
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
81.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Scrapling
103.6k🕷️ The BEST Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
