AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified Apache-2.0 Self-run

Handoff

skill-nexu-io-open-design-handoff · by nexu-io

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.

↗ Website ↗ Repository
— No reviews yet
0 installs
15 views
0.0% view→install

Install

$ agentstack add skill-nexu-io-open-design-handoff

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Handoff? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Content & Media