interview-prep
Skill2 starsChanged 8 months agoMITView on GitHub
This skill should be used when the user asks to "prep me for [company] interview", "interview prep", "I have an interview", or "help me prepare for [company]". Full interview preparation: likely questions with STAR frameworks, power stories, company-specific format, follow-up questions, and questions to ask.
60 other projects use a version of this.
Adopted by
Most recently taken up by
- MarvinLi0216/claude-skillstheir own version, first seen Nov 16, 2026
- carriegale2710/resume-tailortheir own version, first seen Nov 16, 2026
- lengrufeng2008/dsh-skill-librarytheir own version, first seen Nov 15, 2026
- rhowardstone/AI-Job-Coachtheir own version, first seen Nov 15, 2026
- ong6/skillstheir own version, first seen Nov 13, 2026
- sebagarciar/claude-skillstheir own version, first seen Nov 9, 2026
Used with
Projects with it also use application-tracker, job-search and 7 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.
xiding-codeSkillapplication-tracker
Automatically log and track all job applications submitted. Use this skill after every application submission to record the details in a tracking spreadsheet and save relevant documents. Also trigger when the user asks "application status", "what have I applied to", "tracking", or wants to review their application history. Maintains a single source of truth for all job search activity.
Also in 4 projects that use this
rhowardstoneSkilljob-search
Search for jobs across multiple boards and company career pages. Use when looking for new positions to apply to.
Also in 10 projects that use this
claude-office-skillsSkillcover-letter
>
Also in 8 projects that use this
xiding-codeSkillcover-letter-writer
Write and iteratively refine cover letters using a 3-agent debate team (2 Opus critics + 1 Sonnet judge). Use this skill whenever a job application allows cover letter upload, whenever the user asks to write or improve a cover letter, or whenever the job-screener skill returns APPLY for a position. The must-write rule (if enabled in config) applies: if the application system has a cover letter upload field, a cover letter MUST be written. Trigger on: "write cover letter", "cover letter", any application form with a cover letter upload option, or after a job-screener APPLY decision.
Also in 3 projects that use this
rhowardstoneSkillapply
Research-backed job application workflow emphasizing relationship-building over mass applications
Also in 5 projects that use this
QaliAISkillfind-jobs
Discover fresh job postings straight from public employer ATS feeds (Greenhouse, Lever, Ashby, SmartRecruiters, etc.) and deduplicate against the history ledger.
Also in 3 projects that use this
Other versions60 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 60
- rohitg00/ai-engineering-from-scratch★ 79ksame name
- anthropics/knowledge-work-plugins★ 36ksame name
- tinyfish-io/tinyfish-cookbook★ 2.3ksame name
- ShenSeanChen/waku-agent★ 2.2ksame name
- fancyboi999/ai-engineering-from-scratch-zh★ 1.3ksame name
- jerry-ai-dev/MODULAR-RAG-MCP-SERVER★ 1.2ksame name
- lan1177/interview-prep★ 92same name
- matyasstoch/david-skills★ 59same name
- muggl3mind/career-manager★ 24same name
- jaskirat1616/grok-skills★ 22same name
50 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 repository13 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- coffee-chatSkill
- company-researchSkill
- discoverSkill
- fit-analysisSkill
- follow-upSkill
- interview-debriefSkill
- mock-interviewSkill
- negotiateSkill
- offer-analysisSkill
- personalizeSkill
- pipeline-statusSkill
- write-applicationSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 51 edited versions we read keep these.
2
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
- Distinctive: line 55
If available: output/[company]/company-brief.md — use company intel to tailor
- Distinctive: line 151
No company framework found: Use general.md as fallback.
- Very specific: line 153
No knowledge base at all: Stop and say: "Run /personalize first — I need your profile and stories to prep effectively."
“Common” is measured: kept by at least 6 in 10 of the 51 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
/interview-prep
Usage
/interview-prep <company name + role>
/interview-prep <company name + role> recruiter-screenHow It Works
┌─────────────────────────────────────────────────────────┐
│ INTERVIEW PREP │
├─────────────────────────────────────────────────────────┤
│ Step 1: CONTEXT │
│ - Read JD + candidate profile + stories │
│ - Detect company → load matching framework │
│ (e.g., amazon.md for LPs, mckinsey-bain-bcg.md) │
│ │
│ Step 2: PREP PACKAGE │
│ - Likely questions with STAR frameworks │
│ - Power stories mapped to question types │
│ - Smart questions to ask │
│ - Red flags + compensation notes │
│ │
│ Step 3: FOLLOW-UP QUESTIONS │
│ - Scenario questions from JD responsibilities │
│ - Deep-dive follow-ups for later rounds │
│ - Culture + motivation probes │
└─────────────────────────────────────────────────────────┘Inputs
- Job description (provided by user)
- knowledge/profile.md — candidate context
- knowledge/stories/ — STAR story bank
- knowledge/frameworks/writing-framework.md — for structuring verbal answers
- knowledge/values/personal.md — for culture fit and motivation questions
- If available: output/[company]/company-brief.md — use company intel to tailor
- interview-type (if specified): recruiter-screen / technical / hiring-manager / final
- ${CLAUDE_PLUGIN_ROOT}/.claude/resources/ — detect the company or career path and load the matching framework. Search companies/ first (e.g. amazon.md, google.md), then paths/ (e.g. consulting.md, pe.md, marketplace.md), then fall back to general.md.
Produce
1. Interview Format Prediction
Based on role and company: likely stages, who you'll meet, what each round focuses on.
2. Likely Questions (8-12)
For each:
Q: [question] Why they ask it: [what they're really evaluating] STAR Framework:
- Situation: [what context to set]
- Task: [your responsibility]
- Action: [specific steps you took]
- Result: [quantified outcome] Best story: [which story from knowledge/stories/ and why]
3. Power Stories (3)
From knowledge/stories/, identify the 3 that answer the widest range:
- The story in ~2 minutes
- What it proves about you
- Which questions it can answer
4. Questions to Ask the Interviewer (8-10)
Smart questions that signal deep research, strategic thinking, and genuine curiosity.
5. Red Flags to Prepare For
Based on profile gaps — how to address proactively.
6. Anticipated Follow-Up Questions
First-Round Follow-Ups: Q: [question] What they're really testing: [underlying concern] What a strong answer looks like: [framework, not script]
Scenario Questions: Scenario: "Imagine you're 3 months in and..." What they want to see: [decision framework] Candidate's best angle: [which story to draw from]
Culture + Motivation Probes: Why this company, why now, why you — specific to this JD.
7. Compensation Notes
Expected range for role/level, when to bring it up, how to phrase it.
Output Format
## Interview Format: [Company] — [Role]
**Likely stages:** [stages]
**This round focuses on:** [focus]
---
## Top Questions
### Q1: [question]
**Why they ask:** [evaluation target]
**STAR:**
- **S:** [situation]
- **T:** [task]
- **A:** [action]
- **R:** [result — with numbers]
**Use story:** [story name]
...
## Power Stories
| Story | Proves | Answers |
|-------|--------|---------|
| [name] | [trait] | [question types] |
## Questions to Ask
1. [question] — *signals [what]*
## Red Flags
| Gap | How to Address |
|-----|----------------|
| [gap] | [proactive framing] |
## Follow-Up Questions to Prepare
...
## Compensation
Range: $X-Y | Bring up: [when] | Phrasing: [how]If Something Goes Wrong
- No company framework found: Use general.md as fallback. Note: "Using general behavioral framework — tell me the company for more specific prep."
- No stories match a likely question: Flag it: "You don't have a prepared story for [topic]. Run
/personalize storiesto add one." - No knowledge base at all: Stop and say: "Run
/personalizefirst — I need your profile and stories to prep effectively." - Candidate appears underqualified: Say so directly. Focus on reframing strengths, not hiding gaps.
After Output
- "Want to practice?
/mock-interviewfor a simulated interview" - "Track this in your pipeline?
/pipeline-status add [company] [role]"
Rules
- Ground every story in actual stories from knowledge/stories/
- Be specific to THIS role and company
- Flag if candidate is underqualified and needs to reframe
- Note where founder experience helps vs needs framing
- Note where education/MBA angle is an asset
- Structure verbal answers using the candidate's writing framework
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.

