From get-me-a-job
Use this skill when the user is preparing for a job interview or wants to practice answering interview questions. Triggers on phrases like "help me prep for an interview", "I have an interview at [company]", "what questions will they ask", "practice interview questions", "interview prep for [role]", "how do I answer [question type]", "behavioral questions", "what should I say about my background", or any mention of an upcoming interview. Also invoke when the user asks "how do I talk about my experience at [company]" or "what's my story for [role type]". If the user mentions they have an interview coming up, invoke this skill immediately.
How this skill is triggered — by the user, by Claude, or both
Slash command
/get-me-a-job:interview-prepThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill prepares the user for a specific interview with a specific company — not generic prep, but a targeted plan for the exact conversation they're about to have.
This skill prepares the user for a specific interview with a specific company — not generic prep, but a targeted plan for the exact conversation they're about to have.
First step every time: Read ~/.claude/get-me-a-job/references/stories.md for the user's key interview stories and how to map them to question types. Also read ~/.claude/get-me-a-job/references/resume.md for their full background.
If stories.md is missing or empty, tell the user: "You don't have behavioral stories set up yet. These are the most important part of interview prep. Want to build them now?" Then walk them through creating 3-5 STAR stories and save to ~/.claude/get-me-a-job/references/stories.md. If they want to skip, proceed with resume-based prep but flag that their answers will be weaker without structured stories.
Ask (if not already provided):
If the user doesn't know the format, help them look up what that company typically does — many companies have well-documented interview processes on Glassdoor, Blind, or their own careers pages.
Do a quick web search to understand:
Bring this to the prep — "they just launched X, so they may ask about Y" is far more valuable than generic prep.
Generate 15-20 questions organized by type. For each question, provide:
Behavioral questions (5-8): Use the STAR format (Situation, Task, Action, Result), but push the user to be specific and concrete. Vague STAR answers fail. The best behavioral answers have a crisp context setup (2 sentences max), a clear decision point, and a specific result with a number or observable outcome.
Product sense questions (4-6): "Design a product for X", "What metric would you improve for Y", "How would you prioritize this roadmap?" Tailor these to the company's domain and the role's focus area.
Resume / fit questions (3-4): "Walk me through your background", "Why do you want to leave your current role?", "Why this role?", "Why now?" These need sharp, rehearsed answers that don't sound rehearsed.
Technical questions (2-3, if relevant): API design, data modeling, trade-off questions. More relevant for TPM or infrastructure roles.
Role-specific questions: Add questions specific to the role type (e.g., VC roles get "What's your investment thesis?"; consulting gets case questions; banking gets "walk me through a DCF").
Every interview needs a tight answer to: "Tell me about yourself" and "Why this role?"
These should be different for every company. Help the user craft a 2-minute opening that:
Read their resume and stories to build a narrative arc. The arc should connect their past roles into a coherent thread that leads to this company. Help them find the thread — most people's career stories have one, they just haven't articulated it.
Tailor these to the company and role type. Generic advice is useless here.
Format:
### DOs for [Company] [Role]
- [Specific thing to emphasize and why]
- [Thing to do]
### DON'Ts for [Company] [Role]
- [Specific thing to avoid and why]
- [Thing to avoid]
Common patterns by company type:
If the user wants to practice, run a mock interview:
Before delivering any written prep document (the question list, the "tell me about yourself" script, the dos/don'ts), run it through the humanizer skill. Interview prep docs often get shared with career coaches, friends, or practiced aloud — if the language sounds AI-generated, it undermines confidence instead of building it. The humanizer catches inflated language, em dashes, and robotic patterns. This is not optional.
The goal is not to help the user memorize answers. It's to help them understand their own stories so well that they can adapt them naturally to any question. The best interview performance comes from deep confidence in your material, not perfect recall of scripts.
Push them to go specific. The difference between a good answer and a great answer is almost always a specific detail — a number, a person, a decision, a moment.
npx claudepluginhub kope-kope/haas-job-plugins --plugin get-me-a-jobCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.