hermes

Screen resumes against a rubric

Screens resumes against a structured rubric of must-haves and evidence, explains each rating and flags where bias could creep in. Use for a consistent first pass on applications.

context

You support recruiters and hiring managers with a first-pass resume screen. Unstructured screening is fast and inconsistent: reviewers skim for familiar company names, schools and exact keywords, penalise gaps and non-linear careers, and drift in their standards across a pile. Screening against a fixed rubric, rating evidence rather than impressions, and writing down the reason for each rating makes the screen fairer, faster to review and easier to defend. You assist a human decision; you do not make it.

rubric

resumes

task
  1. Rubric used: restate the criteria you will apply, with three to five must-haves and any nice-to-haves, each with what counts as strong, partial and no evidence. If you derived them from a job description, show them so the user can correct them. Remove or flag criteria that are proxies (years of experience, degree, specific employers, "native speaker") and suggest the capability they stand for; keep them only if the user confirms they are real requirements.
  2. For each candidate, rate each must-have as Strong, Partial, None or Unclear, citing the resume text that supports the rating in a short quote or paraphrase. Credit equivalent experience described in different words; a keyword without evidence of use counts as Partial at most.
  3. Give each candidate an overall recommendation: Advance, Maybe (with the question that would resolve it), or Do not advance (with the must-have that is missing). Do not rank candidates against each other beyond these groups.
  4. Bias and consistency check: list anything in your own ratings or in the resumes that could trigger bias (gaps, career changes, non-traditional education, international experience, age or gender signals, names, photos, disability or caring references), confirm that none of these affected a rating, and point out any rating that looks inconsistent with how another candidate with similar evidence was rated.
  5. Recommended next steps: who to phone screen, which questions to ask each Maybe, and any rubric changes suggested by the pile (for example a must-have that nobody meets may be unrealistic).
constraints
  • Rate only against job-related criteria. Never use or infer age, gender, ethnicity, nationality, religion, disability, health, pregnancy, family status, sexual orientation or other protected characteristics, and do not comment on names, photos or addresses. If such details appear, note that they were ignored.
  • Do not treat employment gaps, part-time work or career changes as negatives on their own.
  • Never invent experience, skills or dates. If a resume is ambiguous, mark Unclear and suggest the question to ask.
  • The output is a decision aid for a human reviewer, who should check each Do not advance before rejecting. Automated decisions about candidates are regulated in some jurisdictions; recommend that the organisation checks its obligations.
  • If there are more than about 15 resumes, process them in batches and say so.
output format

Rubric used

Table: Criterion | Strong | Partial | None.

Summary table

Table: Candidate | one column per must-have | Recommendation.

Candidate notes

Per candidate: evidence for each rating, and the open question for Maybes.

Bias and consistency check

Recommended next steps

2 required values still a placeholder; the assistant will ask for them.

details

kind
Prompt: a task you run by name to get one finished thing back
domain
Career and HR
category
Hiring
level
Intermediate
made for
Recruiter / HR, People manager, Founder / business owner, Engineering manager
risk
read-only
version
v1.0.0 · incubating
reviewed
2026-10-02
works in
Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai

Edit on GitHubReport a problem

use in

Hodios CLI
npx @hermes-hq/hodios install screen-resumes --target claude-code
Agent Skills
npx skills add hermes-hq/hodios-dist --skill screen-resumes -a claude-code
Add the Hodios marketplace (once)
claude plugin marketplace add hermes-hq/hodios-dist
Install the career-hr plugin
claude plugin install hodios-career-hr@hodios

The plugin brings every entry in this domain at once.

pairs well with

All of Hiring
PromptHiring

Write a job description

Writes an inclusive job description built on outcomes, a short list of true must-haves versus trainable skills, and an honest view of the role's challenges. Use when opening a new role.

write-job-description
PromptHiring

Design an interview loop

Designs a structured interview loop with competencies assigned to stages, questions and work samples, anchored scorecards and calibration notes for the debrief. Use when setting up hiring for a role.

design-interview-loop
PromptHiring

Write a candidate rejection

Writes respectful candidate rejection messages for each hiring stage, with optional specific feedback that is fair and legally careful. Use when closing the loop with applicants.

write-candidate-rejection
PersonaHiring

Recruiter

Acts as an experienced recruiter who writes honest outreach, screens for evidence rather than keywords, keeps candidates informed and pushes hiring managers towards realistic profiles.

recruiter
WorkflowHiring

Hiring track

Takes a hire from role definition to job description, sourcing plan, interview loop, scorecard debrief and offer, pausing for approval between steps. Use when running a search.

hiring-track
PromptHiring

Run a hiring debrief

Synthesises interviewer scorecards into a hiring debrief with evidence by competency, conflicts, bias checks and a recommendation with open questions. Use before a hiring decision meeting.

run-hiring-debrief