Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nexu-io/od-tune-collab
Default reference pipeline for the tune-collab taskKind — pick a direction, patch-edit the existing artifact, critique, hand off.
Passed 19 of 21 test cases with the skill, and 6 of 21 without it.
and 18 more in the full report
15 fixed6 passed either way1 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
Write out the complete JSON until property string for the critique stage repeat logic when iterating on the checkout workflow artifact. Should it be 'critique.score==5 || iterations>=5' or the standard condition?
| Checked | Without skill | With skill |
|---|---|---|
| The until expression string is critique.score>=4 || iterations>=3. | Missed | Passed |
The instructions your model reads when the skill loads.
Spec §1 / §10.1 / §21.5 / §23.3.3: the canonical "iterate on an
existing artifact" flow. Inherits parentArtifactId from the
project metadata so the produced artifact's
ArtifactManifest.parentArtifactId is set automatically — the
artifact lineage chain stays intact across multi-turn tune cycles.
{
"stages": [
{ "id": "direction", "atoms": ["direction-picker"] },
{ "id": "patch", "atoms": ["patch-edit"] },
{
"id": "critique",
"atoms": ["critique-theater"],
"repeat": true,
"until": "critique.score>=4 || iterations>=3"
},
{ "id": "handoff", "atoms": ["handoff"] }
]
}
The handoff stage records handoffKind: 'patch' (or
'deployable-app' when the user opted in via
od plugin run --target deployable-app AND build-test ran
successfully somewhere upstream in the project's history).
test cases passed, vs 6 / 21 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.