Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →evo-hq/ship
Land the winning experiment from an evo run as a clean, mergeable change -- open a PR when the repo has a remote, otherwise merge into the working branch. Distills the best-scoring experiment down to the minimal diff that reproduces its behaviour, shaped for the qualities a maintainer merges on (scope discipline, test integrity, style adherence), then attaches an advisory mergeability report.
Passed 16 of 21 test cases with the skill, and 11 of 21 without it.
and 2 more in the full report
5 fixed12 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
When starting Stage 2 distillation, where should the distillation work take place?
| Checked | Without skill | With skill |
|---|---|---|
| creates a fresh branch off the user's current HEAD | Missed | Passed |
The instructions your model reads when the skill loads.
Turn a finished evo run into a change a maintainer would merge.
The optimize loop leaves a tree of committed experiments. The winning worktree diff is not mergeable as-is: it carries debug prints, search-process churn, over-broad edits, and sometimes a test that was relaxed to clear a gate. Shipping is the step that re-derives the minimal clean change reproducing the winning behaviour, lands it the way the repo expects (PR or merge), and reports how mergeable it is.
Correctness is the floor, not the goal. The score says the behaviour works; this skill decides whether the diff is fit to merge.
/evo:ship # ship the auto-selected winner
/evo:ship exp_0042 # ship a specific experiment instead
Pick the experiment to ship, then confirm it with the user before touching their tree.
evo status # current best valid score + counts
evo report # top valid experiments table + score chart
evo frontier is for choosing where to branch next; it can
exclude an exhausted branch whose score is still the right thing to ship. An
explicit exp_id argument overrides auto-selection.committed, or pruned with
prune_kind=exhausted, with a commit and score, no gate_result === false,
and no invalid-pruned ancestor. Never select discarded, failed, active,
evaluated, legacy-pruned nodes with no prune_kind, prune_kind=invalid, or
descendants of invalid-pruned nodes. If no valid candidate exists, stop andtest cases passed, vs 11 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.