mock-interview

Installation
SKILL.md

/mock-interview

The user gives you a job post after /mock-interview. You will run a practice interview for that exact job with a panel of five Claudes, then grade it and rewrite the weakest answers. The point is practice that feels like the real one, so never go easy and never grade during the interview.

The panel

  1. The recruiter. First call. Checks the basics: why this job, why this company, your background in two minutes, what you want next.
  2. The hiring manager. Owns the role. Asks about results: what you did, how you did it, what changed because of you, and what you would do in your first 90 days.
  3. The team lead. Would work with you every day. Asks about the craft of the job (a real problem from the post to talk through) and how you work with others when things go wrong.
  4. The coach. Never asks questions. After the interview, rewrites your three weakest answers.
  5. The grader. Never asks questions. After the interview, scores every answer and writes the report.

1. Get the job post

Everything after /mock-interview is the job post: a file path (read it; PDF is fine), a URL (fetch it) or pasted text. If the user also gives a resume, read it too. If there is no job post at all, ask ONE question first: what job are you interviewing for? Paste the post or a link. Then continue. If a URL cannot be read, say so and ask the user to paste the text.

From the post, note: the company (or "the company" if it is not named), the job title, the level, the five skills or duties it stresses most, and anything unusual (location, travel, on-call, a tool it names). Use only what is in the post, the resume and what the user tells you. When you assume something, label it "assumed".

2. Prepare the questions

Start three sub-agents at once (one message, three calls): the recruiter, the hiring manager and the team lead. Give each ONLY the job post notes (and the resume, if any) and its own role from "The panel". Each writes exactly three questions it would really ask for this job, in the order it would ask them, plus one follow-up to use if an answer is vague. Questions must be specific to this job post, not generic lists. Keep the questions to yourself; never show them to the user before you ask them.

Installs
1
GitHub Stars
1
First Seen
Oct 18, 2026