Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →evo-hq/report
Read-only evo run reporting.
Passed 16 of 18 test cases with the skill, and 7 of 18 without it.
and 10 more in the full report
12 fixed7 passed either way2 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
I only need a quick score check for experiment exp_402. I don't need a full terminal scatter plot rendered right now. Which command should I run for a fast lookup?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends evo status or evo show exp_402 for single node score lookups | Missed | Passed |
The instructions your model reads when the skill loads.
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:
evo run, evo gate check, benchmark commands, or project eval
scripts.python bench.py, python slurm_eval.py, sbatch, srun,
squeue, sacct, or scancel to verify a result.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.
Mirrors the web dashboard's score scatter (left rail of evo dashboard):
pruned with prune_kind=exhausted can still be best; prune_kind=invalid and its descendants cannot.Every run in the workspace is rendered, stacked top-to-bottom, with a header line showing run_id · target · metric.
Run:
test cases passed, vs 7 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.