Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nexu-io/od-code-migration
Default reference pipeline for the code-migration taskKind — code-import → design-extract → token-map → rewrite-plan → patch-edit ↔ build-test devloop → diff-review → handoff.
Passed 22 of 22 test cases with the skill, and 6 of 22 without it.
and 26 more in the full report
16 fixed6 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 16 test cases the skill fixed. Same model, same prompt, with and without the skill.
When declaring the plugin input requirements for an OpenDesign code migration project, what parameter holds the repository path, what is its data type, and where is its value automatically pulled from?
| Checked | Without skill | With skill |
|---|---|---|
| The repository path input is named repoPath | Missed | Passed |
| The repoPath parameter is a required string | Missed | Passed |
| The repoPath parameter source is od project import | Missed | Passed |
The instructions your model reads when the skill loads.
Spec §1 / §10.1 / §20.3 / §21.3.2 / §23.3.3: the canonical
code-migration flow. The pipeline cannot ship an accept decision
without a passing build — the patch-edit ↔ build-test devloop is
the convergence engine.
{
"stages": [
{ "id": "import", "atoms": ["code-import"] },
{ "id": "tokens", "atoms": ["design-extract", "token-map"] },
{ "id": "plan", "atoms": ["rewrite-plan"] },
{
"id": "verify",
"atoms": ["patch-edit", "build-test"],
"repeat": true,
"until": "(build.passing && tests.passing) || iterations>=8"
},
{ "id": "review", "atoms": ["diff-review"] },
{ "id": "handoff", "atoms": ["handoff"] }
]
}
The scenario uses build.passing && tests.passing as the
convergence signal — promoted into the spec §22.4 vocabulary by
the build-test atom.
A plugin built on this scenario typically declares od.inputs:
repoPath (string, required): pulled from od project import.targetStack (form): collected by rewrite-plan.testCommand / buildCommand (string, optional): overrides
the inferred package.json scripts in the build-test atom.test cases passed, vs 6 / 22 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.