mcpbeat Sign in

Hiring And Interviewing Agent Skill

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.

740 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
220
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/cbrock84/headcount --skill hiring-and-interviewing

The instruction itself

6 sections, as written by the author

Hiring and interviewing

Define before sourcing

Write, before posting anything:

  • What this person will accomplish in their first year — outcomes, not responsibilities.
  • The three or four competencies that actually predict those outcomes.
  • What is genuinely required versus what is preferred. Long requirement lists are the most

reliable way to shrink and homogenize a candidate pool, and most of the list is never used in the

decision.

  • The bar, agreed by everyone on the loop, before the first interview.

Undefined roles produce interview loops where each interviewer evaluates against a private

definition, and the decision goes to whoever argues hardest.

Design the loop

Each interview assesses different competencies, stated in advance. Overlapping interviews produce

four opinions on the same thing and none on the rest.

  • Structured beats unstructured, consistently and by a wide margin. Same questions, same order,

same rubric. Unstructured interviews mostly measure similarity to the interviewer.

  • Work samples predict best. A realistic exercise close to the actual job beats any amount of

discussion about it. Keep it time-boxed and pay for anything substantial.

  • Behavioral questions about the past, with follow-ups for specifics: what was the situation,

what did *you* do, what happened, what would you change. Hypotheticals measure articulacy.

  • Fewer, better interviews. Long loops lose good candidates and add little signal after the fourth

conversation.

Evaluating

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.

Deciding

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.

Never

  • Lower the bar because the search has been long. Reopen the role definition instead.
  • Let one interviewer's strong view override written independent assessments.
  • Skip reference checks on judgment and collaboration, which are exactly what interviews measure

worst.

How to use it

Copy the folder

Take cbrock84/hiring-and-interviewing from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

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.