Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nexu-io/handoff
Push the run's accepted artifact to a downstream collaboration surface (cli, other code agents, cloud, desktop) and stamp the artifact manifest with the export target.
Passed 18 of 22 test cases with the skill, and 6 of 22 without it.
and 14 more in the full report
14 fixed4 passed either way2 still failing2 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.
The changes passed diff review. We want to open a pull request by publishing to the catalog via od plugin publish --to catalog. Update the manifest target list.
| Checked | Without skill | With skill |
|---|---|---|
| The export target entry uses the surface value github. | Missed | Passed |
| The entry is appended to ArtifactManifest.exportTargets[]. | Missed | Passed |
The instructions your model reads when the skill loads.
Spec §11.5.1 / §21.5: an OD run isn't done when the artifact
exists — it's done when the artifact reaches the surface the user
will keep iterating on. This atom is the "push it somewhere"
stage. It's the natural counterpart to diff-review.
diff-review resolved with
decision: 'accept' | 'partial').surface enum values from
ArtifactManifest.exportTargets[].surface).| surface | typical follow-on |
|---|---|
cli | the user runs od files read against the project; no extra push |
desktop | open the project in the OD desktop app |
web | publish to the public marketplace via spec §13's od:// deep link |
docker | wrap the artifact into a self-contained container (calls the §15.4 image) |
github | open a PR via od plugin publish --to <catalog> |
figma | round-trip back into the figma-migration source file |
code-agent | hand off to Cursor / Claude Code / Codex sitting on top of the project cwd |
Updates ArtifactManifest.exportTargets[] with a row per push,
appending — never replacing — so the artifact's distribution
history stays append-only.
The atom completes when at least one exportTargets[] entry
matches the user's intent or the user explicitly skipped via the
confirmation GenUI surface.
test cases passed, vs 6 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.