etanhey/interview-practice
skills/golem-powers/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).
$ install --global
skillsauthnpx skillsauth add etanhey/golems interview-practiceInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 17, 2026, 12:15 PM15.3s3 files scanned
SKILL.md
- name:
- interview-practice
- description:
- 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).
Interview Practice Skill
7 interview modes for technical interview preparation. Source: Hebrew LinkedIn post on AI-assisted interview prep.
Usage
/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)
Mode 1: Leetcode Interview
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:
- Ask targeted questions
- Probe my thought process
- Expect me to consider edge cases before writing code
- Respond step by step - ask one question or give one prompt at a time, then wait for my response
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.
Mode 2: System Design
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.
Mode 3: Debugging Simulator
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.
Mode 4: Code Review Challenge
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.
Mode 5: Behavioral-Technical Hybrid
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.
Mode 6: Optimization Mentor
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.
Mode 7: Complexity Drills
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.
Tips for Best Results
- Specify company + level for realistic difficulty calibration
- Stay in character - treat it like a real interview
- Ask clarifying questions - don't jump to solutions
- Think out loud - interviewers want to see your process
- Request harder/easier if calibration is off
Quick Reference
| 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 |
Related Skills
etanhey/phoenix-human-view
tools
VerifiedTrustedCommunity
The human-eval UX contract for Phoenix views: turn-by-turn scrollable replay (not a scorecard), hide-but-copyable IDs, collapsed thinking, identity chips, tool filters, tiny frozen starter datasets, mark-wrong-in-thread, mobile-first. Use when: building or reviewing ANY Phoenix/eval view, annotation UI, session replay, or human-grading surface. Triggers: phoenix view, eval UI, annotation view, session replay, human eval UX, grading interface. NOT for: Phoenix data pipelines/ingest (capture scripts have their own specs).
3SKILL.mdUpdated Jun 7, 2026
etanhey/mac-systems
tools
VerifiedTrustedCommunity
macOS systems specialist — AppKit NSPanel architecture, launchd services, socket activation, MCP bridge resilience, syspolicyd, and high-frequency SwiftUI dashboards. Use when building menu-bar apps, LaunchAgents, debugging syspolicyd/Gatekeeper/TCC, resilient UDS/MCP bridges, or SwiftUI dashboards at 10Hz+.
3SKILL.mdUpdated Jun 7, 2026
etanhey/judge-fleet
development
VerifiedTrustedCommunity
Bulk LLM-judging protocol for fleet-dispatched verdict runs (KG cluster, eval harness). Use when: dispatching or running judge workers (J1/J2/RT), planning bulk-apply from verdict JSONL, or triaging evidence_degraded outputs. Triggers: judge fleet, bulk judge, R3 verdicts, kg-judge, RT gate, evidence_degraded. NOT for: single-item code review, Phoenix view UX (use phoenix-human-view), or non-judge eval pipelines.
3SKILL.mdUpdated Jun 7, 2026
etanhey/fleet-wrap
development
VerifiedTrustedCommunity
Quiet-down protocol for sprint close: when the fleet wraps, delete ALL polling crons and monitors, send ONE final dashboard + ONE message, then go SILENT. Use when: fleet wraps, all workers done, overnight queue exhausted, sprint close, Etan asleep/away with nothing approved left. Triggers: fleet wrap, wrap the fleet, stand down, going quiet, sprint close. NOT for: mid-sprint monitoring (keep your loops), spawning a successor (use /session-handoff first).
3SKILL.mdUpdated Jun 7, 2026