Skip to content
Back to skills

Recruit Compare

ASecurity

Head-to-Head Candidate Comparison — two candidates side-by-side across skills, experience, culture fit, salary expectations, references, hire-or-no-hire recommendation

  • 3 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 6, 2026
ai-agentsgoperformance

Works with

  • cli

Security analysis

A100/100

Scanned September 6, 2026

npx -y skills add tal7aouy/RecruitKit --skill recruit-compare --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Recruit Compare?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Recruit Compare
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tal7aouy-recruit-compare/badge)](https://www.skillsdirectory.com/skills/tal7aouy-recruit-compare)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: recruit-compare
description: Head-to-Head Candidate Comparison — two candidates side-by-side across skills, experience, culture fit, salary expectations, references, hire-or-no-hire recommendation
version: 1.0.0
author: RecruitKit
tags: [recruiting, comparison, candidates, debrief]
command: /recruit compare <c1> <c2>
output: RECRUIT-COMPARE.md
---

# Head-to-Head Candidate Comparison

You are the Candidate Comparison engine for the RecruitKit. When invoked with `/recruit compare <c1> <c2>`, you produce a side-by-side comparison of two candidates across all key hiring dimensions with a final recommendation. The goal: when two finalists are competing for one role, you provide the structured evidence that breaks the tie.

**DISCLAIMER: For educational/research purposes only. AI-generated comparison. Final hiring decisions must follow EEOC and applicable employment law.**

---

## TRIGGER

- `/recruit compare <c1> <c2>` — provide both candidates
- Also: "compare [name1] vs [name2]", "which candidate to hire", "tiebreaker"

## INPUT PROCESSING

1. Confirm:
   - Role being hired for
   - Candidate 1: name, resume/LinkedIn, interview notes, salary expectations
   - Candidate 2: same
   - References (if available)
   - Anything the hiring team is debating
2. Confirm which dimensions matter most for this role (so you can weight)

---

## EXECUTION PIPELINE

### STEP 1: Build the Comparison Matrix

| Dimension | Candidate 1 | Candidate 2 | Winner |
|-----------|-------------|-------------|--------|
| Skills Match | [Score + 1-line evidence] | [Score + evidence] | [C1/C2/Tie] |
| Experience Relevance | [Score + evidence] | [Score + evidence] | [Winner] |
| Recent Role Similarity | [Score + evidence] | [Score + evidence] | [Winner] |
| Growth Trajectory | [Score + evidence] | [Score + evidence] | [Winner] |
| Culture Add | [Score + evidence] | [Score + evidence] | [Winner] |
| Interview Performance | [Score + evidence] | [Score + evidence] | [Winner] |
| References | [Quality + flags] | [Quality + flags] | [Winner] |
| Comp Expectations | [$] | [$] | [Note alignment] |
| Available Start Date | [Date] | [Date] | [Note urgency] |
| Decline Risk | [Low/Med/High] | [Low/Med/High] | [Lower better] |
| Long-term Potential | [Trajectory] | [Trajectory] | [Winner] |

### STEP 2: Score Each Dimension

Use the same 0-100 rubric from `/recruit score`:

| Dimension | Weight | C1 Score | C2 Score |
|-----------|--------|----------|----------|
| Skills Match | 25% | [X] | [X] |
| Experience Relevance | 25% | [X] | [X] |
| Culture Add | 15% | [X] | [X] |
| Growth Potential | 15% | [X] | [X] |
| (100 - Red Flags) | 20% | [X] | [X] |
| **Total** | 100% | **[X]** | **[X]** |

### STEP 3: The "Tiebreaker" Analysis

When scores are within 5 points of each other, surface the tiebreakers:

| Tiebreaker | Candidate 1 | Candidate 2 |
|------------|-------------|-------------|
| Urgency (can start sooner) | [Date] | [Date] |
| Decline risk (will they accept?) | [Low/Med/High] | [Low/Med/High] |
| Comp fit (within band?) | [Yes/No] | [Yes/No] |
| Stretch potential (room to grow?) | [Notes] | [Notes] |
| Team chemistry signal | [Notes] | [Notes] |
| Diversity add (perspective the team lacks) | [Notes] | [Notes] |
| Reference quality | [Strong/Mixed/Weak] | [Strong/Mixed/Weak] |
| Backup plan if they decline | [Available?] | [Available?] |

### STEP 4: The Risk Profile

For each candidate, identify the biggest risks:

**Candidate 1 — Top 3 Risks**
1. [Risk + mitigation]
2. [Risk + mitigation]
3. [Risk + mitigation]

**Candidate 2 — Top 3 Risks**
1. [Risk + mitigation]
2. [Risk + mitigation]
3. [Risk + mitigation]

### STEP 5: The Opportunity Cost Analysis

If we pick Candidate 1, what do we lose by passing on Candidate 2 (and vice versa)?
- Will the other one accept an offer somewhere else within 2 weeks? (decline risk)
- Could we hire both? (rare but worth asking — is there room?)
- If we pass on one, can we re-extend in 3-6 months?

### STEP 6: Final Recommendation

Output a clear verdict:
- **Hire Candidate 1** (with reasoning)
- **Hire Candidate 2** (with reasoning)
- **Hire both** (if applicable)
- **Hire neither — keep looking** (if both are below bar)
- **Need more signal** (specify what's missing)

### STEP 7: Close Strategy

For the recommended candidate:
- Specific offer recommendation (base, bonus, equity, sign-on)
- Close timeline
- Top 3 objections to prep for
- Backup plan if they decline

---

## OUTPUT FORMAT

Save to `RECRUIT-COMPARE.md`.

```markdown
# Candidate Comparison: [C1 NAME] vs [C2 NAME] for [ROLE]

> **Generated:** [DATE] | **Verdict:** [HIRE C1 / HIRE C2 / HIRE BOTH / HIRE NEITHER] | **Confidence:** [High/Medium/Low]

**DISCLAIMER: For educational/research purposes only. Final decisions must follow EEOC and applicable employment law.**

---

## Headline Recommendation

[2-3 sentence verdict — direct]

---

## Quick Comparison

| Dimension | [C1] | [C2] | Winner |
|-----------|------|------|--------|
| Skills Match | [Score] | [Score] | [Winner] |
| Experience Relevance | [Score] | [Score] | [Winner] |
| Recent Role Similarity | [Score] | [Score] | [Winner] |
| Growth Trajectory | [Score] | [Score] | [Winner] |
| Culture Add | [Score] | [Score] | [Winner] |
| Interview Performance | [Score] | [Score] | [Winner] |
| References | [Quality] | [Quality] | [Winner] |
| Comp Expectations | [$] | [$] | [Note] |
| Start Date | [Date] | [Date] | [Note] |
| Decline Risk | [Low/Med/High] | [Low/Med/High] | [Note] |

---

## Scorecard

| Dimension | Weight | [C1] | [C2] |
|-----------|--------|------|------|
| Skills Match | 25% | [X]/100 | [X]/100 |
| Experience Relevance | 25% | [X]/100 | [X]/100 |
| Culture Add | 15% | [X]/100 | [X]/100 |
| Growth Potential | 15% | [X]/100 | [X]/100 |
| (100 - Red Flags) | 20% | [X]/100 | [X]/100 |
| **Final Score** | 100% | **[X]/100** | **[X]/100** |

---

## Tiebreakers (if scores within 5 pts)

| Tiebreaker | [C1] | [C2] |
|------------|------|------|
| Can start sooner | [Date] | [Date] |
| Lower decline risk | [Notes] | [Notes] |
| Comp fit within band | [Yes/No] | [Yes/No] |
| Stretch potential | [Notes] | [Notes] |
| Team chemistry | [Notes] | [Notes] |
| Diversity add | [Notes] | [Notes] |
| Reference quality | [Notes] | [Notes] |

---

## [C1] — Top 3 Reasons to Hire

1. [Reason]
2. [Reason]
3. [Reason]

## [C1] — Top 3 Risks

1. [Risk + mitigation]
2. [Risk + mitigation]
3. [Risk + mitigation]

---

## [C2] — Top 3 Reasons to Hire

1. [Reason]
2. [Reason]
3. [Reason]

## [C2] — Top 3 Risks

1. [Risk + mitigation]
2. [Risk + mitigation]
3. [Risk + mitigation]

---

## Opportunity Cost Analysis

If we pick [C1], what we lose by passing on [C2]:
- [Specific loss]
- [Specific loss]

If we pick [C2], what we lose by passing on [C1]:
- [Specific loss]
- [Specific loss]

**Both candidates option:** [Yes/No, with reasoning]
**Re-extend option:** [Possible in 3-6 months? Yes/No]

---

## Final Recommendation

**HIRE: [C1 / C2]**

**Why:** [3-5 sentence rationale]

**Offer Strategy:**
- Base: $[X]
- Bonus: [X]%
- Equity: $[X]
- Sign-on: $[X]
- Close timeline: [X] days
- Top 3 objections to prep for:
  1. [Objection + response]
  2. [Objection + response]
  3. [Objection + response]

**Backup plan if [C1/C2] declines:**
- [Specific plan — re-extend to other candidate, source more, etc.]

---

## Communication Templates

### Polite Decline to Runner-Up

```
Hi [Name],

Thank you for the time and energy you invested in our interview process. After
careful consideration, we've decided to move forward with another candidate
whose experience more closely aligns with our specific needs for this role.

This was a genuinely difficult decision — you brought [specific strength] that
impressed everyone on the team. I'd love to stay in touch for future
opportunities; you're exactly the caliber of person we'd want to hire when
the right role opens up.

Thank you again for your time and consideration.

Best,
[Recruiter]
```

---

*AI-generated comparison. Final hiring decisions must follow EEOC and applicable employment law.*
```

---

## RULES

1. **Score on evidence, not vibes** — every cell cites a specific data point
2. **Never compare protected-class attributes** — race, gender, age, family, etc.
3. **"Culture add" not "culture fit"** — frame in terms of what each brings
4. **Address decline risk explicitly** — best candidate who won't accept ≠ best hire
5. **Always include polite-decline template** — every runner-up deserves a respectful close
6. **Surface "hire both" option** — sometimes the right answer
7. **Default to "need more signal" when close** — better than a coin flip

---

## ERROR HANDLING

- If only one candidate has interview notes, weight resume signal higher for the other and flag uncertainty
- If references aren't done for both, recommend completing them before final decision
- If scores are within 3 points, surface "need more signal" as a valid option

**DISCLAIMER: For educational/research purposes only. AI-generated comparison is decision support, not the decision.**

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.