# Report

Read-only evo run reporting.

- Repository: https://github.com/evo-hq/evo (1491 stars)
- Category: Engineering
- License: Apache-2.0
- Last updated: 2026-10-05
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add evo-hq/evo --skill report -g -a claude-code -y`
Codex: `npx skills add evo-hq/evo --skill report -g -a codex -y`
Cursor: `npx skills add evo-hq/evo --skill report -g -a cursor -y`
Gemini CLI: `npx skills add evo-hq/evo --skill report -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add evo-hq/evo`

## Description

Read-only evo run reporting. Use when the user invokes /evo:report, asks what happened overnight, asks what improved recently, asks for the best/frontier candidates, asks for a quick score chart without opening the dashboard, or wants the scatter plot in chat output. Never run benchmarks, gates, Slurm commands, evo run, or ad-hoc verification scripts for report requests.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Report

Report the current evo workspace from recorded state only. A report request is
read-only, even if the user phrases it casually as "what happened?", "what got
better?", "what should I pay attention to?", or "I just woke up".

Do not spend compute while reporting:

- Do not run `evo run`, `evo gate check`, benchmark commands, or project eval
  scripts.
- Do not run `python bench.py`, `python slurm_eval.py`, `sbatch`, `srun`,
  `squeue`, `sacct`, or `scancel` to verify a result.
- Do not create launcher, monitor, parsing, or analysis scripts.
- Do not edit files.

Use stored evo state instead: `evo report`, `evo status`, `evo tree`,
`evo frontier`, `evo show <id>`, `evo diff <id>`, and immutable artifacts under
`.evo/run_*/experiments/<exp>/attempts/<NNN>/`.

For chart requests, render the dashboard's scatter plot as a colored terminal
block, one chart per run, sized to the current terminal.

## What it shows

Mirrors the web dashboard's score scatter (left rail of `evo dashboard`):

- X = experiment creation order, Y = score
- Dot color by status: green = committed valid result, red = failed, purple = active, grey = pending / evaluated / discarded / pruned
- ★ marks the current best valid committed-result experiment. `pruned` with `prune_kind=exhausted` can still be best; `prune_kind=invalid` and its descendants cannot.
- Yellow ring on dots that sit on the best-path spine (root → best)
- Yellow stair line traces cumulative-best across valid committed-result experiments
- ○ at the baseline for experiments that have no score yet (active / pending)

Every run in the workspace is rendered, stacked top-to-bottom, with a header line showing `run_id · target · metric`.

## How to invoke

Run:

```bash
evo report
```

That is it. Print the output verbatim in your reply so the user sees the chart. Do not summarize the chart in prose, the visual is the point.

Flags:

The rest: https://github.com/evo-hq/evo/blob/HEAD/plugins/evo/npm/skills/report/SKILL.md