distributions/codex/skills/interview-preparation/SKILL.md
Prepare for job interviews across formats—behavioral, technical, portfolio reviews, and negotiations. STAR/CAR frameworks for stories, common question patterns, research strategies, and follow-up templates. Triggers on interview prep, job interviews, behavioral questions, or salary negotiation requests.
npx skillsauth add organvm-iv-taxis/a-i--skills interview-preparationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Turn experience into compelling interview performance.
| Type | Focus | Preparation | |------|-------|-------------| | Behavioral | Past experiences, soft skills | Story bank, STAR method | | Technical | Skills assessment, problem-solving | Practice problems, fundamentals | | Portfolio/Case | Work samples, process | Presentation prep, talking points | | Culture Fit | Values alignment, team dynamics | Company research, questions | | Executive | Leadership, vision | Strategic narratives |
Situation: Set the context (brief)
Task: Your specific responsibility
Action: What YOU did (detailed)
Result: Quantified outcome + learning
Challenge: Problem faced
Action: Steps taken
Result: Outcome achieved
Build 8-12 stories covering:
| Category | Example Prompts | |----------|-----------------| | Leadership | Led team, made tough call, influenced without authority | | Conflict | Disagreement with colleague, difficult stakeholder | | Failure | Mistake made, project that failed, lesson learned | | Achievement | Proudest accomplishment, exceeded expectations | | Initiative | Self-started project, identified opportunity | | Collaboration | Cross-functional work, built relationships | | Problem-solving | Ambiguous situation, creative solution | | Growth | Learned new skill, received feedback, adapted |
## [Story Title]
**Tags**: #leadership #conflict #technical
**STAR**:
- **Situation**: [2-3 sentences of context]
- **Task**: [Your specific role/responsibility]
- **Action**: [Detailed steps YOU took—use "I" not "we"]
- **Result**: [Quantified outcome + what you learned]
**Variations**: Can adapt for questions about [X], [Y], [Z]
**Duration**: ~2 minutes when told aloud
| Question | What They Want | Strategy | |----------|----------------|----------| | "Tell me about yourself" | Relevant narrative | Present → Past → Future (2 min) | | "Walk me through your resume" | Career logic | Transitions + growth + why here | | "Why this role/company?" | Genuine interest | Specific research + fit |
| Pattern | Example | Story Category | |---------|---------|----------------| | "Tell me about a time when..." | ...you led a team | Leadership | | "Describe a situation where..." | ...you faced conflict | Conflict | | "Give an example of..." | ...a difficult decision | Problem-solving | | "What would you do if..." | ...deadline was impossible | Hypothetical (use real example) |
| Question | Strategy | |----------|----------| | "What's your greatest weakness?" | Real weakness + mitigation steps | | "Why did you leave X?" | Positive framing, growth focus | | "Why the gap in employment?" | Honest + productive use of time | | "Where do you see yourself in 5 years?" | Ambitious but realistic, aligned with role |
Role Understanding:
Team/Culture:
Growth:
Closer:
1. Clarify the problem (ask questions)
2. Work through examples
3. Explain your approach before coding
4. Write clean code, talk through it
5. Test with edge cases
6. Analyze complexity (time/space)
1. Clarify requirements (functional + non-functional)
2. Estimate scale (users, data, QPS)
3. High-level design (components, data flow)
4. Deep dive on key components
5. Address bottlenecks, trade-offs
6. Discuss monitoring, failure modes
1. Brief intro (30 sec)
2. Project 1: Deep dive (5-7 min)
- Context + challenge
- Your role + process
- Key decisions + rationale
- Results + learnings
3. Project 2: Medium depth (3-5 min)
4. Project 3: Overview (2-3 min)
5. Q&A (remaining time)
| Research | Where to Find | |----------|---------------| | Company mission/values | About page, annual report | | Recent news | Google News, press releases | | Products/services | Website, product pages | | Competitors | Industry analysis | | Interviewer background | LinkedIn | | Glassdoor reviews | Interview questions, culture | | Company challenges | News, earnings calls |
When asked for expectations early:
"I'm focused on finding the right fit. I'm confident we can find something that works if we're aligned on the role. What's the range budgeted for this position?"
Responding to an offer:
"Thank you, I'm excited about this opportunity. I'd like to take some time to review the full package. When do you need a response?"
Counter-offering:
"I'm very excited about joining [Company]. Based on my research and the value I'll bring, I was hoping for [X]. Is there flexibility there?"
If they can't move on salary:
"I understand the constraints. Are there other elements we could discuss—signing bonus, equity, PTO, start date, or title?"
references/story-bank-template.md - Full story bank formatreferences/question-bank.md - 100+ common questionsreferences/follow-up-templates.md - Thank you and follow-up emailsdevelopment
Dry-run audit + targeted cleanup for shell command history. Currently wraps atuin (stats today, prune, dedup with dated preview artifacts); extensible to zsh/bash/mcfly backends. Always previews before applying — apply commands are echoed for the human to run, never auto-executed. Triggers on "/shell-history-hygiene", "audit atuin", "audit shell history", "clean shell history", "atuin prune", "atuin dedup", "shell history hygiene", "history cleanup". Replaces ad-hoc one-liners (e.g. `... | tee cmd > file.txt` which wrote two files, swallowed dedup output, and left a junk `cmd` file).
tools
Guided Cowork setup — install role-matched plugins, connect your tools, try a skill.
development
Manage AI agent session lifecycles with structured phases (FRAME, SHAPE, BUILD, PROVE), context preservation across sessions, handoff protocols, and session metadata tracking. Triggers on session management, agent lifecycle, or multi-session workflow requests.
tools
Parse a session transcript into a structured Session Governance Index — an annotated bibliography of every file modified and commit made, internal-energy accounting (tool uses, estimated tokens), shipped-vs-tasked atom tally, and classification of missing items as Gaps or Vacuums. Triggers on "visibility-schema-substrate-sweep", "session cascade audit", "session governance audit", or any request to summarize what a session actually produced versus what it was asked to produce.