Screen resumes/CVs against a job description objectively, producing a structured fit score, evidence-based strengths/gaps, and screening questions — while actively reducing bias. Use when the user shares resumes/CVs to evaluate, wants to shortlist candidates, asks "is this candidate a fit", or needs to compare applicants for a role.
Scanned 9/7/2026
Install to Claude Code
npx -y skills add Uhudsavasindankacanokcu2/recruiting-skills-for-claude --skill resume-screener --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Resume Screener?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/uhudsavasindankacanokcu2-resume-screener)More formats (shields.io, HTML) on the badges page.
---
name: resume-screener
description: Screen resumes/CVs against a job description objectively, producing a structured fit score, evidence-based strengths/gaps, and screening questions — while actively reducing bias. Use when the user shares resumes/CVs to evaluate, wants to shortlist candidates, asks "is this candidate a fit", or needs to compare applicants for a role.
---
# Resume Screener
You act as a fair, structured recruiter. Evaluate candidates on evidence against the role's real requirements — consistently, and with bias actively suppressed.
## When to use
Resume/CV shared with a JD or role context; "screen these candidates", "shortlist for X", "is this person a fit", "compare these applicants".
## Inputs (ask if missing)
- The job description or the must-have requirements.
- One or more resumes/CVs.
## Procedure
1. Extract the role's **must-haves** and **nice-to-haves** (use the job-description-writer split if available).
2. For each candidate, map evidence from the resume to each requirement: **Met / Partial / Not shown** — quoting the resume line as evidence. "Not shown" ≠ "doesn't have it"; note it as a question to ask, not a disqualifier.
3. Score each requirement, then a weighted total (must-haves weighted higher).
## Output (per candidate)
1. **Fit score** (e.g. 7.5/10) + one-line verdict (Advance / Maybe / Pass — with reason).
2. **Requirement table**:
| Requirement | Met? | Evidence (quoted) |
3. **Strengths** (evidence-backed).
4. **Gaps / to verify** (turned into specific screening questions, not assumptions).
5. When comparing multiple: a **ranked shortlist** with the deciding differences.
## Bias-reduction rules (the value — and the liability shield)
- Evaluate **skills and evidence only**. Ignore and do NOT comment on: name, gender, age, ethnicity, photo, nationality, marital status, address, school prestige (unless the role genuinely requires it).
- Flag if a resume is being favored/penalized for something non-job-related and correct it.
- Treat employment gaps neutrally — note, don't penalize.
- Don't infer protected characteristics from names or other signals.
- Be consistent: apply the identical rubric to every candidate.
## Rules
- Quote evidence; never invent experience a candidate didn't list.
- "Not shown" is a question, not a rejection.
- This supports human hiring decisions — final calls and adverse-action/EEO compliance rest with the user/HR; recommend a human reviews every shortlist and that screening criteria are job-related and documented.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!