eval-fetchlisted

# Eval Fetch Use this skill to turn messy Galileo console links and IDs into local evidence. The goal is a grounded debug packet, not a diagnosis. Do not print secret values. Report only credential variable names, whether expected variables are present, and the exact fetch blocker. ## First Parse The Input Use `skills/eval-engineer/scripts/parse_galileo_url.py` when the user provides a Galileo URL. Follow `skills/eval-engineer/references/galileo-url-intake.md` for artifact-specific behavior. Preserve source metadata in the packet: - `source.console_url` - `source.console_host` - `source.workspace_slug` - `source.project_id` - artifact IDs such as `log_stream_id`, `experiment_id`, `session_id`, or `trace_id` ## Ask Only For Missing Information - project URL: ask for log stream, experiment, session, trace, time window, or failure metric. - Experiments list URL: ask for latest experiment, specific experiment, failing experiment, or comparison pair. - Log stream URL: ask for latest N traces, failed traces, time window, or aggregate metrics if the user did not specify. - Log stream aggregate metrics: use `skills/eval-engineer/scripts/fetch_log_stream_packet.py` with `--url` or `--project-id` plus `--log-stream-id`. This fetches traces, spans, sessions, aggregates numeric scorer metrics into `.galileo/current/debug-packet.json`, and reports `metric_fetch_status`. - Trace/session URL: fetch that artifact and ask whether to compare against a baseline only if