interview-prep-coach
Skill0 starsChanged 17 days agoMITView on GitHub
Prepare a candidate for an interview using their real experience. Builds STAR stories mapped to the role, likely questions including the awkward ones about their gaps with how to answer each, and sharp questions to ask, with an optional mock-interview mode. Use when the user has an interview, screening call or assessment coming up.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- mnbresearch/mnb-claude-skillstheir own version, first seen Jul 2, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- mnbresearch/mnb-claude-skills★ 1same name
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 repository7 other files it gives its agents.
- ats-scoreSkill
- cover-letter-writerSkill
- cv-tailorSkill
- finance-transformation-cvSkill
- job-match-analyzerSkill
- regional-cv-formatsSkill
- resume-genieSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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
- Distinctive: line 12
Read the CV and the job advert.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Interview prep coach
Follow references/interview-prep.md.
Workflow
- Read the CV and the job advert. Also read any notes about the stage (screening, panel, case study) or the interviewers.
- Build the pack:
- 5 STAR stories covering delivery, influence, problem solving, a setback and the core domain skill. Situation (with scale), Task (what they owned), Action (2–4 steps, saying "I" not "we"), Result (CV numbers or an
[Outcome: …]placeholder), Best for (question types). - 10 likely questions across behavioural, technical, situational and motivation, plus at least one per significant gap. For each: which story to use and what to stress or avoid.
- 3–5 sharp questions to ask them about success measures, team setup and the biggest problem in the first 90 days.
- 5 STAR stories covering delivery, influence, problem solving, a setback and the core domain skill. Situation (with scale), Task (what they owned), Action (2–4 steps, saying "I" not "we"), Result (CV numbers or an
- Offer a mock interview: ask one question at a time, wait for the answer, then give brief feedback (structure, specificity, result) before the next question.
Rules
- Stories use only real experience from the CV or the user. Never invent outcomes; use placeholders and ask.
- Prepare the candidate to answer gap questions honestly. Don't help them hide gaps.
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.

