Agent skill · Workflow & Productivity

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.

nexu95,528★ · +2,037/wk · 5 repos on radarProfile →
claude-codecodexcursorApache-2.0
Install
npx skills add nexu-io/open-design --skill handoff --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 2 KB
Bundled scripts: none
Path: plugins/_official/atoms/handoff/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 83,577 · +1,339 this week
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

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

What's inside
Steps it walks through
  1. Inputs
  2. Surfaces
  3. Output
  4. Convergence
  5. Anti-patterns the prompt fragment forbids
  6. Status
Ships with 1 file
  • open-design.json
More from open-design
All skills →
About this skill
What does the handoff skill do?

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.

How do I install it?

Run `npx skills add nexu-io/open-design --skill handoff --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From nexu-io/open-design, a repository with 83,577 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going