mcpbeat

Interview Prep

anthropics/interview-prep

Create structured interview plans with competency-based questions and scorecards. Trigger with "interview plan for", "interview questions for", "how should we interview", "scorecard for", or when the user is preparing to interview candidates.

359 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
23273
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/anthropics/knowledge-work-plugins --skill interview-prep

The instruction itself

8 sections, as written by the author

Interview Prep

Create structured interview plans to evaluate candidates consistently and fairly.

Interview Design Principles

  • Structured: Same questions for all candidates in the role
  • Competency-based: Map questions to specific skills and behaviors
  • Evidence-based: Use behavioral and situational questions
  • Diverse panel: Multiple perspectives reduce bias
  • Scored: Use rubrics, not gut feelings

Interview Plan Components

Role Competencies

Define 4-6 key competencies for the role (e.g., technical skills, communication, leadership, problem-solving).

Question Bank

For each competency, provide:

  • 2-3 behavioral questions ("Tell me about a time...")
  • 1-2 situational questions ("How would you handle...")
  • Follow-up probes

Scorecard

Rate each competency on a consistent scale (1-4) with clear descriptions of what each level looks like.

Debrief Template

Structured format for interviewers to share findings and make a decision.

Output

Produce a complete interview kit: panel assignment (who interviews for what), question bank by competency, scoring rubric, and debrief template.

How to use it

Copy the folder

Take anthropics/interview-prep 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.