interview-solver
Executes a multi-agent pipeline to solve and verify coding interview problems.
Install
mkdir -p .claude/skills/interview-solver && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13249" && unzip -o skill.zip -d .claude/skills/interview-solver && rm skill.zipInstalls to .claude/skills/interview-solver
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Solve a coding interview exercise (Coderbyte / LeetCode style) end-to-end. Triggers when the user pastes an interview problem, references one in `examples/`, or asks to "solve" or "resolve" an exercise — especially when they specify a target language like JavaScript, TypeScript, or Java. Runs the same 5-agent pipeline (analyzer → architect → coder → tester → run → evaluator with up to 3 retry iterations) as the `/solve` slash command, calling each worker subagent directly via the Agent tool. Persists the final passing solution to `outputs/<FunctionName>.<ext>`.Key capabilities
- →Analyze coding interview problems
- →Architect solutions for coding exercises
- →Code solutions in specified languages
- →Test and evaluate coded solutions
- →Persist passing solutions to local files
How it works
The skill follows a 5-agent pipeline (analyzer, architect, coder, tester, evaluator) to process the problem, generate a solution, test it, and persist the passing result.
Inputs & outputs
When to use interview-solver
- →Solving LeetCode problems
- →Practicing algorithmic coding
- →Generating clean solution files
About this skill
Interview Solver — Skill entry point
When this skill triggers, you are running the same pipeline as the /solve slash command. The full step-by-step orchestration is the canonical version in .claude/commands/solve.md.
What you do here
- Use
Readto load.claude/commands/solve.md. - Follow its instructions exactly, treating the user's natural-language request (the message that triggered this skill) as the equivalent of
$ARGUMENTS. - The slash command body covers everything: parsing the input (language + problem), invoking each of the 5 worker subagents via the
Agenttool one at a time, running the sandbox, looping on FAIL up to 3 times, persisting the passing solution tooutputs/, cleaning uptmp/, and returning the final markdown report.
Rules
- Do not run any orchestration logic before reading
.claude/commands/solve.md. The slash command is the single source of truth. - Do not call the
interview-orchestratorsubagent — there is no longer one. Each of the 5 workers (interview-analyzer,interview-architect,interview-coder,interview-tester,interview-evaluator) is invoked directly by you via theAgenttool, exactly as the slash command describes. - Do not summarize or trim the final report. Relay it verbatim to the user.
- If the user explicitly typed
/solve <args>instead of triggering this skill via natural language, the slash command runs directly and this skill is not involved.
When not to use it
- →When not solving a coding interview exercise
- →When not referencing a problem in 'examples/'
- →When not asking to 'solve' or 'resolve' an exercise
Limitations
- →The full step-by-step orchestration is in .claude/commands/solve.md
- →Do not call the interview-orchestrator subagent
- →Do not summarize or trim the final report
How it compares
This skill automates the entire end-to-end process of solving a coding interview problem, including analysis, coding, and testing, unlike manual problem-solving.
Compared to similar skills
interview-solver side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| interview-solver (this skill) | 0 | 3mo | No flags | Advanced |
| vitest | 41 | 6mo | No flags | Intermediate |
| write-unit-tests | 5 | 3mo | Review | Intermediate |
| javascript-testing-patterns | 3 | 4mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
vitest
antfu
Vitest fast unit testing framework powered by Vite with Jest-compatible API. Use when writing tests, mocking, configuring coverage, or working with test filtering and fixtures.
write-unit-tests
tldraw
Writing unit and integration tests for the tldraw SDK. Use when creating new tests, adding test coverage, or fixing failing tests in packages/editor or packages/tldraw. Covers Vitest patterns, TestEditor usage, and test file organization.
javascript-testing-patterns
wshobson
Implement comprehensive testing strategies using Jest, Vitest, and Testing Library for unit tests, integration tests, and end-to-end testing with mocking, fixtures, and test-driven development. Use when writing JavaScript/TypeScript tests, setting up test infrastructure, or implementing TDD/BDD workflows.
testing-patterns
davila7
Jest testing patterns, factory functions, mocking strategies, and TDD workflow. Use when writing unit tests, creating test factories, or following TDD red-green-refactor cycle.
unit-testing-test-generate
sickn33
Generate comprehensive, maintainable unit tests across languages with strong coverage and edge case focus.
designing-tests
CloudAI-X
Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.