handoff
Lets your agent send the finished work to other places. It marks where the work was sent for tracking.
What it does
This tool sends your finished work to another place where you can keep using it. It records where the work was sent.
When to use it
- ✓When you want to send your code to your computer.
- ✓When you want to publish your work on a website.
- ✓When you want to pass the work to another code program.
Example of what to ask your AI
“Send this code to my computer.”
Want more? Open the sections below.
How to use
The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.
Skill link
Ready-to-paste message
How it works
The tool takes your accepted work and sends it to the location you chose. It also notes where it was sent in your work's history.
Installation
Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.
In the terminal (Claude Code, Codex, Cursor), in your project folder:
npx skills add nexu-io/open-design --skill handoffOr download just the file:
curl -L https://raw.githubusercontent.com/nexu-io/open-design/main/plugins/_official/atoms/handoff/SKILL.md -o SKILL.mdTechnical content (original SKILL.md)
Original text by the author, straight from GitHub.
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-reviewresolved withdecision: 'accept' | 'partial'). - The export target (one of the
surfaceenum values fromArtifactManifest.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
figmaas a no-op when the user's source was a Figma file — round-trip is the whole point of the figma-migration scenario.
Status
Implemented by the daemon runner in
apps/daemon/src/plugins/atoms/handoff.ts. It records provenance,
handoffKind, and export targets, then persists the updated artifact
manifest.
FAQ
What is an 'artifact'?
Think of 'artifact' as the final result of your work, like ready code or a design.
What does 'export target' mean?
'Export target' is the place where you want to send your work, such as your computer, a website, or another program.
Why is the history important?
The history shows all the places your work has been sent, ensuring you know the origin and destination of each version.
Details
Original description by the author
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.
repo: nexu-io/open-design
Popularity
- GitHub stars
- 101k
- Ranking position
- #526
- License
- Apache-2.0
- Updated
- 10/16/2026
Comments
- …
More skills from this repository
sample-plugin
Makes your agent create a metadata file for tests. It helps ensure code works correctly in different situations.
nexu-io/open-design
aster-atelier
Helps your agent create an artistic website with a classic look. It uses elegant imagery, blue skies, and serif fonts for a cinematic feel.
nexu-io/open-design
audio-jingle
Makes your agent generate audio like jingles and sound effects. It can create music and voices, saving the result as an audio file.
nexu-io/open-design
blog-post
Helps your agent write long articles or blog posts. It includes space for images, quotes, and author information.
nexu-io/open-design
Similar skills
bun-runtime
Has your agent use Bun to run, organize, and test code. It helps choose Bun over other tools and migrate existing projects.
affaan-m/ECC
database-migrations
Helps your agent make safe changes to databases. It ensures changes can be undone and minimizes downtime.
affaan-m/ECC
deployment-patterns
Sets up deployment and CI/CD workflows, containerization, and rollback strategies to ensure safe releases.
affaan-m/ECC