evals-start — Claude Code skill: what it does, how to install
Routes an evaluation request to the right specialised skill. Use it when you are unsure where to begin or which evaluation workflow fits the task.
npx skills add ai-evals-course/evals-skills --skill evals-start -a claude-codeWhat evals-start does
evals-start inspects the starting situation and loads a targeted skill rather than running its own evaluation process. It routes trace-based failure analysis to error-discovery, an existing evaluation pipeline review to eval-audit, and RAG pipeline work to evaluate-rag.
A known failure mode that code can check goes to write-code-eval; a failure mode needing an LLM judge goes to write-judge-prompt. With no traces available, the route starts with generate-synthetic-data and then moves to error-discovery. This is a router, not an evaluation workflow itself. When no route fits, it asks for clarification instead of guessing.
What it helps with
- find failure modes in available traces
- audit an existing evaluation pipeline
- write a code-based check for a known failure
- create data before trace review
- evaluate a RAG pipeline
Example prompts for the agent
- Help me get started with evaluations. I have traces and want to find failure modes.
- I do not have traces for an evaluation yet. Where should I start?
- I need to evaluate a RAG pipeline.
How to install evals-start
1Skills CLI (Vercel)
npx skills add ai-evals-course/evals-skills --skill evals-start -a claude-code2Manually: put the files in place
~/.claude/skills/evals-start/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/evals-start/
1Skills CLI (Vercel)
npx skills add ai-evals-course/evals-skills --skill evals-start -a codex2Manually: put the files in place
.agents/skills/evals-start/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ai-evals-course/evals-skills --skill evals-start -a cursor2Manually: put the files in place
.cursor/skills/evals-start/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ai-evals-course/evals-skills evals-start2Manually: put the files in place
.github/skills/evals-start/SKILL.md1Skills CLI (Vercel)
npx skills add ai-evals-course/evals-skills --skill evals-start -a gemini-cli2Platform CLI
gemini skills install https://github.com/ai-evals-course/evals-skills --path skills/evals-startManually: put the files in place
.devin/skills/evals-start/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add ai-evals-course/evals-skills --skill evals-start -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about evals-start
How do I install evals-start in Claude Code?
Run npx skills add ai-evals-course/evals-skills --skill evals-start -a claude-code, then run npx skills add ai-evals-course/evals-skills --skill evals-start -a claude-code again. The skill file is at ~/.claude/skills/evals-start/SKILL.md.
What does evals-start do?
It matches an evaluation request to a targeted skill and loads that skill's process. evals-start itself contains routing rules.
What happens when no route matches my task?
The skill asks for clarification. It does not choose a route by guesswork.
Source text
SKILL.md · Apache-2.0
--- name: evals-start description: > Entry point for evals. Use when the user asks for help with evals, does not know where to begin, or asks for something no other skill in this plugin matches. Do NOT use when a more specific skill in this plugin already matches; load that skill directly. --- # Evals Start This plugin splits eval work into targeted skills. Your job here is small: find the row below that matches the user's situation, tell the user which skill you are loading and why, then load that skill and follow its workflow from start to finish instead of improvising your own version of it. | Situation | Skill to load | |---|---| | Has traces, wants to find failure modes, no established taxonomy yet | `error-discovery` | | Has an existing eval pipeline and wants to know if it can be trusted | `eval-audit` | | Has a known failure mode that code can check (e.g., format, schema, regex, execution) | `write-code-eval` | | Has a known failure mode and wants an LLM judge for it | `write-judge-prompt` | | Has an LLM judge or evaluator and wants to check its quality | `validate-evaluator` | | Has no traces to review yet | `generate-synthetic-data`, then `error-discovery` | | Wants a custom annotation interface for some other labeling task | `build-review-interface` | | Wants to evaluate a RAG pipeline | `evaluate-rag` | Most requests that mention error analysis with traces in hand mean `error-discovery`. New users with an existing pipeline usually need `eval-audit` first. This file holds only routing. When in doubt about which row fits, ask the user instead of guessing. The workflow lives in the targeted skill.
© ai-evals-course · Apache-2.0 · ai-evals-course/evals-skills