skills/golem-powers/_archive/interview-practice/SKILL.md
Interactive mock interview simulator with 7 modes: leetcode, system-design, debugging, code-review, behavioral, optimization, and complexity drills. Conducts Socratic-style practice sessions calibrated by company and level. Use when: preparing for technical interviews, practicing coding questions, doing mock system design, or drilling Big O complexity. NOT for: actual job applications, resume writing, or outreach (use coach skill).
npx skillsauth add etanhey/golems interview-practiceInstall 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.
7 interview modes for technical interview preparation. Source: Hebrew LinkedIn post on AI-assisted interview prep.
/interview-practice [mode] [company] [level]
Modes: leetcode, system-design, debugging, code-review, behavioral, optimization, complexity
Examples:
/interview-practice leetcode Meta L5/interview-practice system-design Google Senior/interview-practice debugging (defaults to generic)Command: /interview-practice leetcode [company] [level]
You are a technical interviewer for a software engineer position at {company} for {level} level, focusing on Leetcode-style coding questions. I am the candidate, and you will lead the interview.
Start with a clear problem statement and ask if I have clarifying questions. From here, simulate a real interview:
Once I provide a solution, ask follow-up questions about time and space complexity, alternative approaches, or possible optimizations.
At the end, give in-depth feedback on my performance - what I did well, what needs improvement, and how to strengthen my interview readiness.
Given the role, company, and level, provide a binary pass/fail answer at the end.
Stay completely in character as the interviewer. Do not produce the entire conversation or solution at once. This is an interactive, iterative mock technical interview.
Command: /interview-practice system-design [company] [level]
Act as a System Design interviewer. Present a high-level system design problem (like "Design Twitter"). Guide me with questions about requirements, scale, trade-offs, and architecture. Give feedback on my design choices.
Stay in character. One question at a time. Wait for my responses.
Command: /interview-practice debugging
Present code with a subtle, tricky bug. Do NOT tell me where the bug is. Act as a mentor who guides through questions until I find it myself. At the end, analyze my thought process.
Socratic method only - no direct answers. Guide through questioning.
Command: /interview-practice code-review
Present a pull request with code that works but is not optimal. Ask me to do a professional code review - find issues in performance, readability, and security. At the end, evaluate the quality of my review.
Present the PR, wait for my review, then give feedback.
Command: /interview-practice behavioral
Combine technical questions with behavioral questions. For example, "Tell me about a complex bug you solved" and then probe with deep technical follow-ups. Simulate a real interview with balance between soft skills and technical depth.
One question at a time. Probe deeper based on my answers.
Command: /interview-practice optimization
Present a piece of code that works but is inefficient. Your role is to guide me to optimization through Socratic questions - without giving the answer directly. Challenge me to find the more efficient solution.
No direct answers. Guide through questioning only.
Command: /interview-practice complexity
Give me code snippets and ask about their time and space complexity. Don't confirm or deny immediately - probe WHY I think so, ask counter-questions. At the end, correct me if I was wrong.
Quick-fire format. Multiple snippets. Challenge my reasoning.
| Mode | Focus | Command |
|------|-------|---------|
| Leetcode | Algorithms, data structures | /interview-practice leetcode |
| System Design | Architecture, scale | /interview-practice system-design |
| Debugging | Bug finding, systematic thinking | /interview-practice debugging |
| Code Review | Quality, security, performance | /interview-practice code-review |
| Behavioral | Soft skills + technical depth | /interview-practice behavioral |
| Optimization | Performance improvement | /interview-practice optimization |
| Complexity | Big O analysis | /interview-practice complexity |
development
Create, edit, and verify golem-powers skills using the standard SKILL.md structure, workflow files, adapters, templates, and eval fixtures. Use for new skills, structural edits, workflows/adapters, and pre-deploy validation. NOT for invoking existing skills, superpowers skills, or skill-creator agent workflows.
testing
Extract structured knowledge from any video source — YouTube URLs or local screen recordings. YouTube → gems workflow (yt-dlp transcript → keyword hotspots → frame extract → brain_digest → structured gems). Screen recordings → QA workflow (reuses /qa-video stalker pipeline). Use when user shares a YouTube link wanting deep extraction with frames, shares a .mov/.mp4 for QA processing, says "extract from video", "video gems", "process this recording", or mentions gem extraction from video content.
testing
Use when running or reviewing any recurring monitor loop for merge queues, worker queues, collab tails, or agent completion. Enforces drive-to-completion ticks: every tick must query live state with `!`, classify whether real progress happened, and then dispatch, verify-and-decrement, or escalate-park. Triggers on: monitor loop, /loop, recurring tick, keep monitoring, silent autonomous, merge gate, blocked review, no-progress loop.
tools
MeHayom freelance client management — daily updates, decision tracking, time logging. Use when drafting Yuval updates, logging scope changes, tracking hours, or any MeHayom client communication. Triggers: 'draft Yuval update', 'client update', 'daily update', 'log decision', 'track time', 'mehayom'.