Skip to content
Back to skills

Handoff

ASecurity

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.

  • 98,936 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added June 6, 2026
ai-agentsdockergit

Works with

  • claude code
  • cursor
  • cli

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned June 6, 2026

npx -y skills add nexu-io/open-design --skill handoff --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Handoff?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Handoff
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/nexu-io-handoff/badge)](https://www.skillsdirectory.com/skills/nexu-io-handoff)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: handoff
description: 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.
od:
  scenario: tune-collab
  mode: handoff
---

# Handoff

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`.

## Inputs

- The accepted artifact set (after `diff-review` resolved with
  `decision: 'accept' | 'partial'`).
- The export target (one of the `surface` enum values from
  `ArtifactManifest.exportTargets[].surface`).

## Surfaces

| 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 |

## Output

Updates `ArtifactManifest.exportTargets[]` with a row per push,
appending — never replacing — so the artifact's distribution
history stays append-only.

## Convergence

The atom completes when at least one `exportTargets[]` entry
matches the user's intent or the user explicitly skipped via the
`confirmation` GenUI surface.

## Anti-patterns the prompt fragment forbids

- Pushing the artifact to a surface that wasn't on the user's
  intent list.
- Mutating `sourcePluginSnapshotId` (it's immutable; the export
  trail is additive).
- Treating `figma` as a no-op when the user's source was a Figma
  file — round-trip is the whole point of the figma-migration
  scenario.

## Status

Reserved id, prompt-only fragment in v1.

Files in this skill

  • SKILL.md2 KB
  • open-design.json889 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.