eval-setuplisted

# 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. ## 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 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