report
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.
npx skills add evo-hq/evo --skill report --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 va
- What it shows
- How to invoke
- When not to use
- Overnight / Improvement Reports
evo report
What does the report skill do?
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.
How do I install it?
Run `npx skills add evo-hq/evo --skill report --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From evo-hq/evo, a repository with 1,359 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.