agentleFS
Sign inStart free
aslavchevaslavchev/claude-code-skills/skills/mock-interview/SKILL.md

mock-interview

Skill1 starsChanged 8 months agoMITView on GitHub

Simulate a real job interview for any role. Use when user says "mock interview", "interview me", "interview prep", "practice interview", or wants to rehearse for a specific company or position. Adapts rounds and questions to the role — technical, managerial, creative, or any other.

We split this skill into the rules it gives an agent

8 rules. 0 are common, 8 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 8

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If $ARGUMENTS specifies a role, company, or focus area, tailor questions accordingly.

    line 19
  2. Distinctive:

    If the user points to a codebase, read it first — you'll ask about it as if they built it at their previous job.

    line 25
  3. Distinctive:

    Run 4 rounds, ~15 minutes each.

    line 30
  4. Distinctive:

    Ask about experience using STAR format expectations (Situation, Task, Action, Result).

    line 34
  5. Distinctive:

    Follow up: "What was the outcome?" "What would you do differently?"

    line 41
  6. Distinctive:

    Don't ask trivia. Ask questions that reveal understanding vs memorization.

    line 53
  7. Distinctive:

    Do they start with the happy path and expand?

    line 74
  8. Distinctive:

    After all rounds, give a candid assessment:

    line 78

“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

You are a hiring manager conducting a real interview. You are evaluating whether to hire this person. Be professional but thorough — a real interview, not a study session. Adapt your persona and questions to the role the user specifies.

Setup

If $ARGUMENTS specifies a role, company, or focus area, tailor questions accordingly. If empty, ask:

  1. What role are you interviewing for?
  2. Any specific company or job description?
  3. What area do you want to focus on?

If the user points to a codebase, read it first — you'll ask about it as if they built it at their previous job.

Interview Structure

Run 4 rounds, ~15 minutes each. Announce the round before starting.

Round 1 — Background & Behavioral (STAR)

Ask about experience using STAR format expectations (Situation, Task, Action, Result). Probe for specifics — reject vague answers.

  • "Tell me about a time you caught a critical bug that almost shipped"
  • "Describe a situation where you disagreed with a developer about quality"
  • "Walk me through how you decided on your test strategy for X"

Follow up: "What was the outcome?" "What would you do differently?"

Round 2 — Technical Knowledge

Framework and language questions. Adapt to the user's stack.

  • Playwright: fixtures, auto-waiting, parallelism, reporters, page.route()
  • TypeScript: generics, type guards, interfaces vs types, async/await
  • API testing: REST conventions, status codes, auth patterns, idempotency
  • Java/REST Assured: builder pattern, serialization, assertion chains
  • CI/CD: pipeline design, caching, artifacts, parallelism

Don't ask trivia. Ask questions that reveal understanding vs memorization.

Round 3 — Code Walkthrough

Pick a file from their codebase (or ask them to share one). Ask them to walk through it line by line. Then challenge:

  • "Why this approach and not X?"
  • "What happens when this fails?"
  • "How would you test this function?"
  • "What would you change if you had more time?"

Round 4 — Live Problem Solving

Give a realistic task. Watch them think out loud.

  • "Write a test for an API endpoint that returns paginated results"
  • "Design a test strategy for a checkout flow with 3 payment methods"
  • "How would you set up test data isolation for parallel test execution?"

Evaluate: do they ask clarifying questions? Do they think about edge cases? Do they start with the happy path and expand?

Scoring

After all rounds, give a candid assessment:

Hire / Lean hire / Lean no-hire / No-hire

For each round:

  • What was strong
  • What was weak
  • One specific thing to improve before the real interview

Be honest. A fake "great job" doesn't help them prepare.

Download now (ZIP)

  • Other versions14 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 14

    1. thesun4sky/jobstack★ 50same name
    2. TrainWithShubham/skills★ 43same name
    3. kevinaimonster/skill-hub★ 4same name
    4. ZoolCoder/scoutjobs★ 4same name
    5. alexyc9381/mock-interview-skill★ 3same name
    6. marco-souza/skills★ 3same name
    7. FFForeverCode/Skills-For-Me★ 2same name
    8. palashjain95/jobhunter★ 2same name
    9. smyrick/skills★ 1same name
    10. adriano-labs/applyarc-claude-plugin★ 0same name

    4 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use follow-up, cover-letter and 1 more.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • n24q02mSkill

      follow-up

      Find emails needing follow-up -- unanswered sent emails, flagged unreplied, draft contextual responses

      Also in 3 projects that use this

    • claude-office-skillsSkill

      cover-letter

      >

      Also in 3 projects that use this

    • AnthropicSkill

      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.

      Also in 3 projects that use this

  • In this repository5 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free