Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nexu-io/od-new-generation
Default reference pipeline for the new-generation taskKind — discovery → plan → generate → critique with a critique-theater devloop.
Passed 19 of 23 test cases with the skill, and 6 of 23 without it.
and 18 more in the full report
14 fixed5 passed either way3 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.
Which atom is assigned to the critique stage in the default fallback pipeline?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies atom critique-theater | Missed | Passed |
The instructions your model reads when the skill loads.
Spec §10.1 / §23.3.3: when a plugin omits od.pipeline, the daemon
falls back to this scenario plugin's pipeline. Replacing the
default for an enterprise / vertical edition is now a content edit
rather than a code change.
{
"stages": [
{ "id": "discovery", "atoms": ["discovery-question-form"] },
{ "id": "plan", "atoms": ["direction-picker", "todo-write"] },
{ "id": "generate", "atoms": ["file-write", "live-artifact"] },
{
"id": "critique", "atoms": ["critique-theater"],
"repeat": true,
"until": "critique.score>=4 || iterations>=3"
}
]
}
The discovery stage gives the agent a clean surface for clarifying questions; the plan stage commits to a TodoWrite-backed plan; the generate stage produces the artifact; the critique stage devloops until the score converges or the iteration ceiling is hit.
A plugin can override or extend by declaring its own od.pipeline.
The default applies only when the plugin's pipeline is absent.
test cases passed, vs 6 / 23 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.