- name
SKILL.md
스킬 파일은 게시자의 저장소에 그대로 있습니다.
복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add nishant-Tiwari24/cracked --skill mock-interview -a cursor -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add nishant-Tiwari24/cracked --skill mock-interview -a claude-code -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add nishant-Tiwari24/cracked --skill mock-interview -a codex -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add nishant-Tiwari24/cracked --skill mock-interview -a grok -y복사한 메시지를 Grok Bot 채팅에 보냅니다. Bot이 GitHub에서 이 SKILL.md를 가져와 모든 Bot이 공유하는 스킬에 추가합니다.
Install this skill: https://github.com/nishant-Tiwari24/cracked/tree/HEAD/skills/interview/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.
date +%s (or the fallback in ../oa-sim/RUNNER.md § Clock) as the session start, and compute the deadline.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 .
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.dsa_level (beginner → easy/easy-medium; intermediate → medium; strong → medium-hard/hard).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.
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:
Record each hint, its rung and its timestamp. Never give code.
edge cases 11/12 · random 2,000 inputs, 3 mismatches · max-size 0.4 s (limit 6 s, Python). For failures, show the first failing input only and let them find the bug.Real interviewers judge process, not just output. Keep a private timeline. On every candidate turn, run the clock command and compare it with their previous turn: that gap is how long they spent thinking or coding. Note:
In file mode, read the file whenever they report progress, or every few turns, and notice how it evolves: steady growth vs. a sudden finished solution (§7).
Don't comment on these signals during the interview. They go into the debrief.
Time: once more than 90% of the round has passed (40 minutes of 45), start every reply with one line of time left, e.g. ⏱ 4 min left. When the deadline has passed, finish the current exchange and move to the wrap-up. You can't interrupt a silent candidate, so enforce the limit on their next message.
Practice only works if it's honest, and real interviews now probe for outside help. Follow INTEGRITY.md: watch for the signals, and run the explain-and-modify probe only when two or more signals appear. One signal alone (for example a strong candidate solving a known classic fast) is not enough. Report an Integrity line in the debrief. Be fair. Signals aren't proof, so never accuse. State what you observed and what the probe showed.
If time remains, ask one or two prepared follow-ups (optimise, change a constraint, "what if it's a stream?"), as discussion only.
clarify 2m · approach 9m · code 18m · test 6m.problem: line, so later sessions can avoid repeats and prep-plan can count patterns. Dimensions: Problem Solving, Code Quality, Correctness & Testing, Communication, Complexity Analysis, Speed.Clean, or Signals observed: <what> · probe result: <what>.Skill calls: if your agent has no Skill tool, open the named skill's SKILL.md in the cracked skills folder (core/, interview/, profile/, strategy/) and follow it instead.
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) o
---name: mock-interviewdescription: Run a realistic, timed DSA coding interview where the agent is the interviewer. Company-wise questions…---# skills/interview/mock-interview/SKILL.md개요
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.
FAQ
게시자에게서 skills/interview/mock-interview/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/nishant-Tiwari24/cracked에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.