Interview prep
Curated, auditable, benchmark-ready Agent Skills library for Claude Code, Codex, OpenCode, Cursor, and more.
npx -y skills add shinzoxD/knackbox --skill interview-prepAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 27 days oldThe repository was created 27 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 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
Prepare for technical and behavioral interviews with structured practice. Use whenever the user asks for interview prep, practice questions, STAR stories, system design drills, coding interview help, or how to answer common interview questions — for candidates or interviewers.
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.9 KB, as published. Nobody here has run it
Interview Prep
Prep is deliberate practice with feedback loops. Tailor to role, level, and company signals — not generic TED-talk answers.
Workflow
- Role, level, company, interview format, date constraints.
- Build a topic map (coding, system design, behavioral, domain).
- For behavioral: draft STAR stories mapped to competencies.
- For technical: drills with timeboxes and debriefs.
- Mock answer → critique → improved answer.
- Day-of checklist and questions to ask them.
Output formats
STAR story
**Competency:** …
**S/T:** …
**A:** (your actions, first person)
**R:** measurable result + lesson
**30-sec version:** …
System design drill
Requirements → API/data → design → trade-offs → scale → failures → summary
Rules
- Prefer the user's real experience; mark placeholders instead of inventing jobs.
- Coaching tone: specific feedback, not empty praise.
- Calibrate difficulty to stated level (junior vs staff).
- For coding: emphasize communication and tests, not only final code.
- Interviewer mode: rubrics and fair questions; avoid trivia traps.
- Never help with take-home fraud or live-interview cheating policies; practice is fine.
Edge cases
- Career switchers: translate adjacent experience honestly.
- Anxiety: shorter mocks, structure first.
- Staff+: emphasize leadership scope, ambiguity, and org impact.