Interview prep
A forkable job-search operating system for Claude — cover letters, interview prep, transcript Q&A, thank-you notes, and daily pipeline briefings, all in your own voice.
npx -y skills add ldenson1120/job-search-os --skill interview-prepAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
This skill should be used when the user says "help me prep for my interview", "I have an interview with [company or person]", "prep me for [company]", "interview prep for [role]", "I'm interviewing at [company] on [date]", or any variation that signals an upcoming interview they want to prepare for.
SKILL.md
3.2 KB, as published. Nobody here has run it
Interview Prep
Generate a focused prep brief for an upcoming interview. The output should arm the user to walk in knowing their angle, their stories, and their questions — not overwhelm them with everything they could possibly know.
What to do
-
Identify what you know. Extract company name, role, interviewer name/role, and interview date from the user's message. Ask for anything missing that would meaningfully change the prep.
-
Read the context files. Load
context/MY_POSITIONING.mdandcontext/STORY_BANK.md. If a filled-out role research file exists for this company (e.g.,context/role-research-[company].md), load that too. If it doesn't exist, ask if they've done any research or note that the role research template is available for them to fill in. -
Generate the prep brief. Structure it as follows:
Your angle for this role 1-2 sentences on why this company/role is a genuine fit, drawn from their positioning doc. This is what they say when asked "why us" or "why this role."
Likely focus areas Based on the role and interviewer's function, flag 3-4 themes the interview is likely to probe (e.g., leadership, cross-functional influence, technical depth, scale, failure). If you have the interviewer's role, calibrate to what they'd care about.
Stories to lead with Pull 3-4 stories from the story bank that best map to the likely focus areas. For each: the story name, the one-line summary, and the competency it covers. Don't write out the full STAR — they should know these already.
Stories to have in reserve 1-2 additional stories worth having ready if the conversation goes long or goes somewhere unexpected.
Questions to ask 5 sharp questions — mix of role-scoped (what does success look like, what's the hardest part of this job), company-scoped (what's the biggest strategic bet right now, how does this team make decisions), and interviewer-scoped (what's been your experience here). Don't use generic questions.
Watch-outs Any gaps, awkward transitions, or things about their background/resume that might come up as concerns. Flag them plainly so they can prepare, not so they panic.
-
Offer to go deeper. After delivering the brief, offer to (a) drill into any specific story, (b) do a mock Q&A, or (c) help fill out the role research template if they haven't already.
Style rules
- Be direct and specific. "Lead with the Ascend pipeline story" is more useful than "consider talking about pipeline."
- Don't pad the brief with things they already know. If their story bank is strong, trust it.
- If context files are thin or missing sections, say so plainly and work with what's there. Don't refuse to help just because the files aren't complete.
- Write for someone who's done this before and wants to sharpen, not someone who needs the basics explained.