Individual skill
evals-start
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.
skills/evals-start/SKILL.md
Source commit 80d5f7b0127c7572ed9e9339937adbfd7240ffeb
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,756
- Repository last updated
- Oct 24, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 1,646 bytesagents/openai.yamlasset · 232 bytes
Read excerpt
# 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` |