mock-interview
Skill4 starsChanged 32 days agoMITView on GitHub
Runs a timed mock interview (behavioral, coding, or system design) with a realistic interviewer persona, then scores it and logs a practice session in ScoutJobs. Use when the user says "mock interview", "practice", "quiz me", "drill", or after interview-prep.
17 other projects use a version of this.
Adopted by
Most recently taken up by
- mtibebu/technical-learning-labtheir own version, first seen Nov 8, 2026
- georgesmomo/mock-interviewtheir own version, first seen Nov 8, 2026
- nishant-Tiwari24/crackedtheir own version, first seen Nov 8, 2026
- seonwooj0810/careerlooptheir own version, first seen Oct 20, 2026
- alexyc9381/mock-interview-skilltheir own version, first seen Oct 20, 2026
- ClarvAI/job-search-hqtheir own version, first seen Oct 15, 2026
Used with
Projects with it also use follow-up and cover-letter.
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.
n24q02mSkillfollow-up
Find emails needing follow-up -- unanswered sent emails, flagged unreplied, draft contextual responses
Also in 3 projects that use this
claude-office-skillsSkillcover-letter
>
Also in 3 projects that use this
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- thesun4sky/jobstack★ 50same name
- TrainWithShubham/skills★ 43same name
- nishant-Tiwari24/cracked★ 5same name
- kevinaimonster/skill-hub★ 4same name
- alexyc9381/mock-interview-skill★ 3same name
- marco-souza/skills★ 3same name
- FFForeverCode/Skills-For-Me★ 2same name
- georgesmomo/mock-interview★ 2same name
- palashjain95/jobhunter★ 2same name
- smyrick/skills★ 2same name
7 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.
In this repository33 other files it gives its agents.
- application-trackerSkill
- apply-by-emailSkill
- behavioral-frameworksSkill
- behavioral-interviewSkill
- behavioral-storiesSkill
- calendar-syncSkill
- coding-frameworksSkill
- coding-interviewSkill
- cover-letter-generatorSkill
- cv-checkSkill
- daily-briefingSkill
- draft-reviewSkill
- fit-reviewSkill
- fit-scoreSkill
- google-driveSkill
- inbox-triageSkill
- interview-debriefSkill
- interview-prep-generatorSkill
- interview-prepSkill
- job-description-analyzerSkill
- job-fitSkill
- job-searchSkill
- learn-preferencesSkill
- linkedin-profile-optimizerSkill
- offer-comparison-analyzerSkill
- resume-ats-optimizerSkill
- resume-tailorSkill
- salary-negotiation-prepSkill
- scoutjobs-setupSkill
- sysdesign-interviewSkill
- system-design-frameworksSkill
- upskillSkill
- weekly-reviewSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 13 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 31
Carry forward: if a story was weak, edit stories/<slug>.md with the fix.
“Common” is measured: kept by at least 6 in 10 of the 13 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.
Files
Mock interview
Three kinds. Pick from the user's words or ask once: behavioral, coding, system_design. Optional target: a job id (loads that application's interview-prep.md and stories.md) or a topic from the library.
Personas live in the plugin's agents/ directory: behavioral-interviewer.md, coding-interviewer.md, sysdesign-interviewer.md. Where the platform can spawn subagents (Claude Code), spawn the persona with the inputs it lists. Elsewhere, read the file and embody it in the main session.
Problem library: references/library/coding/*.md (14 problems with hint ladders and reference solutions) and references/library/sysdesign/*.md (8 prompts). Never reveal a reference solution before the candidate yields.
Flow
- Set up (one message): kind, target company or topic, time box (behavioral 30 min, coding 35 min, system design 45 min), and for coding the language and a scratch file path under
$(scoutjobs path)/applications/<key>/scratch/or the scratchpad. - Interview: the persona runs it. Stay in character. The candidate ends it by saying "done" or "yield".
- Debrief (you, not the persona). Score 0-100 with the rubric below. Three strengths, three fixes, each tied to a moment in the transcript. For behavioral, name which STAR part was weak per answer. For coding, state complexity reached vs optimal and whether tests passed. For system design, list requirements missed and tradeoffs never mentioned.
- Log:
scoutjobs session log --kind mock_behavioral --topic "<company or theme>" --score 72 --notes "strong on conflict story; results vague; rambled on Q3"Kinds: mock_behavioral, mock_coding, mock_sysdesign. Add --notes that a future you can act on.
- Carry forward: if a story was weak, edit
stories/<slug>.mdwith the fix. If a coding pattern failed,scoutjobs learn add --skill "<pattern>" --priority 1 --notes "failed in mock <date>".
Rubric
| Kind | 40 | 30 | 30 |
| behavioral | STAR completeness and specificity | results with numbers, ownership clear | concision, handled follow-ups |
| coding | correctness (ran and passed) | approach: clarified, planned, complexity | communication under pressure |
| system_design | requirements and estimation | design coherence and tradeoffs | depth on the deep-dive, curveball handling |
Short drills are fine: "quiz me on 5 behavioral questions" uses the same log kind with --topic drill.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
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.