9 added, 0 removed. Audit A to A.
---
name: eval-setup
description: Use when the user asks to set up Eval Engineer, check .galileo readiness, create workspace scaffolding, or configure editable files, verification commands, app type, or evidence paths.
---
# Eval Setup
Use this skill to make a repo ready for Eval Engineer without pretending it is
ready for RCA. Setup is operational: create or review workspace files, identify
missing configuration, and tell the user what evidence is still needed.
## Do
- Ensure `.galileo/config.yml`, `.galileo/current/`, `.galileo/eval-dataset/`,
`.galileo/sessions/`, and `.galileo/learnings.md` exist.
- Preserve existing files. Do not overwrite user configuration or evidence.
- Help fill in app type, editable files, blocked files, and verification
commands when the user knows them.
- Explain which evidence is needed next: trace, session, log stream,
experiment, metric profile, or verification packet.
- For live Galileo work, load
`skills/eval-engineer/references/galileo-live-readiness.md` and report the
project, evidence source, traces, metrics, scorer/recompute job, and queryable
metric status before saying setup is ready.
+ - Before creating or accepting local eval evidence, use
+ `skills/eval-engineer/references/galileo-integration-intake.md` to ask for
+ the required Galileo project, log stream, experiment, session, trace,
+ metric/scorer, time window, or credential confirmation.
+ - If the user wants local-only evaluation, record explicit local-only
+ confirmation before creating local packets, scripts, or score reports.
## Do Not
- Do not guess metrics, providers, app type, or production safety requirements.
- Do not fetch Galileo evidence unless the user provides a URL/ID or asks for
`/eval-fetch`.
+ - Do not create `.galileo/current/debug-packet.json`, verification packets,
+ `scripts/evaluate_*`, synthetic traces, or local score reports as a substitute
+ for missing Galileo integration inputs.
- Do not diagnose or fix application behavior during setup.
- Do not call a Galileo project ready when only the project exists. A ready
Galileo source needs a log stream, experiment, session, or trace with records,
enabled metrics, completed scoring/recompute, and queryable metric values.
## Validation Loop
Before reporting ready, confirm `.galileo/config.yml`, `.galileo/current/`,
`.galileo/eval-dataset/`, `.galileo/sessions/`, and `.galileo/learnings.md`
exist, then list missing config values without guessing them. If a Galileo live
source is in scope, also produce:
```text
Galileo readiness:
- project: ready/missing
- evidence source: log stream/experiment/session/trace/missing
- traces or spans: ready/missing
- metrics enabled: ready/missing
- scoring jobs: completed/running/failed/missing
- queryable metric values: ready/missing
```
## Output
End with:
```text
Workspace: ready/needs changes
Missing before RCA:
- ...
Next command: /eval-fetch, /eval-measure, /eval-diagnose, /eval-cost, or /eval-engineer
```
If `.galileo/current/debug-packet.json` and `.galileo/config.yml` are already
usable, route to `/eval-diagnose` for failure RCA or `/eval-cost` for
tokenomics work instead of sending the user back to `/eval-engineer`.