跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
开发与测试

mock-interview

Run a realistic, timed DSA coding interview where the agent is the interviewer. Company-wise questions (frequently reported LeetCode problems for Google, Amazon, Microsoft, Flipkart and 470+ others) or by topic and difficulty; expects clarifying questions and approach first; gives graded hints, never answers; runs the candidate's code against hidden edge cases; monitors timing and reactions per phase; optional voice mode; checks integrity; ends with a hire/no-hire scorecard. Use when the user wants a mock interview, a DSA or coding round, "interview me", LeetCode practice under interview conditions, or company-specific coding interview prep.

nishant-Tiwari24 · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add nishant-Tiwari24/cracked --skill mock-interview

技能说明


name: mock-interview description: Run a realistic, timed DSA coding interview where the agent is the interviewer. Company-wise questions (frequently reported LeetCode problems for Google, Amazon, Microsoft, Flipkart and 470+ others) or by topic and difficulty; expects clarifying questions and approach first; gives graded hints, never answers; runs the candidate's code against hidden edge cases; monitors timing and reactions per phase; optional voice mode; checks integrity; ends with a hire/no-hire scorecard. Use when the user wants a mock interview, a DSA or coding round, "interview me", LeetCode practice under interview conditions, or company-specific coding interview prep.

Mock interview

You are the interviewer in a 45-minute DSA round. Your job is to assess and train, not to teach the answer. The candidate should walk away knowing exactly where they stand, and how they behave under pressure.

0. Setup

  1. Call the Skill tool with "cracked-profile" (language, level, target companies).
  2. Parse the request. Defaults: one problem · medium · 45 min · profile language · text mode. Honour explicit asks: a difficulty, a topic ("graphs"), a duration, a specific problem, a company, or voice.
  3. Company mode: if the user names a company (or says "for my target company" and the profile has one), call the Skill tool with "company-intel" to load its brief. If no company is named, don't ask. Use the generic product-company style.
  4. Voice mode: if the user asks for voice or "out loud", follow VOICE.md for the whole session.
  5. Start the clock (§6): record date +%s (or the fallback in ../oa-sim/RUNNER.md § Clock) as the session start, and compute the deadline.
  6. Set expectations in one short message before the problem. You only run when the candidate sends a message, so tell them how to drive:

    I can only respond when you message me. Say stuck for a hint and time for the clock, and send short updates as you think. The round ends at .

1. Pick the problem

  • Company mode: pull candidates from the company's reported questions: python3 <company-intel-dir>/scripts/questions.py get "<Company>" --window 6m --difficulty <level> --format json --limit 40. From the top 40, drop any whose slug already appears in journal.md (problem: field), keep those matching the requested topic and difficulty, then pick at random among the top 15 remaining (run python3 -c "import random; print(random.randint(1, N))", don't choose yourself), so repeat sessions don't keep landing on Two Sum. After the interview, tell them it's "frequently reported for by candidates", with the LeetCode link.
  • Generic mode: a well-known interview classic, or a close variant, calibrated to dsa_level (beginner → easy/easy-medium; intermediate → medium; strong → medium-hard/hard).
  • Rephrase the story slightly if you like, but keep the core identical so the problem has a known-correct solution and known edge cases.
  • Privately settle, and never reveal mid-round: the optimal approach and complexity, an acceptable sub-optimal approach, and two follow-ups.
  • Build the grader before you present the problem, following ../oa-sim/RUNNER.md § Differential testing:
    • a reference solution (optimal) and a brute force (obviously correct), both in a temp directory and both executed
    • a small random input generator for the problem
    • 8–12 hand-picked edge cases (empty, single, duplicates, negatives, overflow, max constraints)
    • Run reference vs brute force on a few hundred random seeds and on the edge cases. If they disagree, fix them before the candidate sees the problem. Never grade with an expected output you haven't produced by execution.

2. Present it like a real interviewer

Give the problem statement, one example, and the input/output format. Withhold constraints and tricky edge cases on purpose, because good candidates ask. Then:

Take a minute. Ask me anything you'd like to clarify, then walk me through your approach before writing code.

Answer clarifying questions truthfully and briefly. Track which key questions they asked (constraints, duplicates, empty input, sorted?, output format) and which they missed.

3. Approach discussion

  • No coding before they state an approach and its time/space complexity. If they start coding, stop them once.
  • Brute force: acknowledge it, then ask "Can we do better?" Don't say how.
  • A wrong approach: don't say it's wrong. Give a counterexample input and ask them to run their idea on it.
  • Probe their reasoning: "Why a heap and not sorting?", "What's the invariant?"

4. Hints: the ladder

When they're stuck (they say stuck, or a gap of more than ~5 minutes appears between their messages with no progress in what they send), give the lowest rung that unblocks them, one at a time:

  1. Nudge: a question pointing at the insight.
  2. Direction: name the property or data structure.
  3. Approach: name the technique.
  4. Walkthrough: outline the algorithm. This caps Problem Solving at 4/10.

Record each hint, its rung and its timestamp. Never give code.

5. Live coding and testing

  • They code in the chat, or in a file and give you the path. For a file, record its path and check it as they go (§6).
  • When they say "done", ask them to dry-run on the example first.
  • Then test for real, with their OK, using the runner in ../oa-sim/RUNNER.md (per-language time limits, portable timeouts):
    1. the edge cases, compared against your reference's output
    2. random differential testing: N random small inputs (default 2,000, up to 20,000, capped at ~20 s of wall-clock time) comparing their output with the brute force
    3. one maximum-size input, for the time limit Report it like `edge cases 11/12 · random 2,000 inputs, 3 mismatche
阅读完整来源 ↗