Designs and runs hiring — role definition, sourcing, interview loop design, structured evaluation, and the decision itself. Use this to open a role, write a job description or scorecard, design an interview process, prepare interview questions, calibrate a hiring decision, or diagnose why a hiring process produces poor outcomes.
npx skills add https://github.com/cbrock84/headcount --skill hiring-and-interviewing
Write, before posting anything:
reliable way to shrink and homogenize a candidate pool, and most of the list is never used in the
decision.
Undefined roles produce interview loops where each interviewer evaluates against a private
definition, and the decision goes to whoever argues hardest.
Each interview assesses different competencies, stated in advance. Overlapping interviews produce
four opinions on the same thing and none on the rest.
same rubric. Unstructured interviews mostly measure similarity to the interviewer.
discussion about it. Keep it time-boxed and pay for anything substantial.
what did *you* do, what happened, what would you change. Hypotheticals measure articulacy.
conversation.
Interviewers write their assessment against the rubric before any discussion. Group discussion
first produces convergence on the first confident opinion rather than an aggregation of independent
ones.
Debrief on evidence: what did they say or do that supports this rating? "Culture fit" without
behavioral evidence is where bias enters, and it should be challenged every time it appears.
A yes needs evidence on every required competency, not a strong overall impression. Where evidence
is missing, get it — an extra conversation is cheap compared to a mis-hire.
Ambiguity means no. The cost of a bad hire is far larger and lasts far longer than the cost of a
longer search, and it is borne by the team, not the hiring manager.
worst.
Take cbrock84/hiring-and-interviewing from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.