Source profileQuality 60/100

nexu-io/open-design/plugins/_official/atoms/handoff/SKILL.md

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.

Source repository stars
82,073
Declared platforms
0
Static risk flags
0
Last source update
2026-07-28
Source checked
2026-07-28
DecisionCompatibilityInstallWorkflowPermissionsEvidenceSource

Decision brief

What it does—and where it fits

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.

Best for

    Not for

    • Pushing the artifact to a surface that wasn't on the user's
    • Mutating sourcePluginSnapshotId (it's immutable; the export

    Compatibility matrix

    Platform support, with evidence labels

    PlatformStatusEvidenceWhat to check
    CodexNot declaredNo explicit evidencePortability before use
    Claude CodeNot declaredNo explicit evidencePortability before use
    CursorNot declaredNo explicit evidencePortability before use
    Gemini CLINot declaredNo explicit evidencePortability before use
    Open the compatibility checker

    Installation

    Inspect first. Install second.

    The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

    Source-detected install commandSource
    npx skills add https://github.com/nexu-io/open-design --skill "plugins/_official/atoms/handoff"
    Safe inspection promptEditorial

    Inspect the Agent Skill "handoff" from https://github.com/nexu-io/open-design/blob/89d6d4ef21baf80f871595abdf6f7de6e941dd44/plugins/_official/atoms/handoff/SKILL.md at commit 89d6d4ef21baf80f871595abdf6f7de6e941dd44. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

    Workflow

    What the source asks the agent to do

    1. 01

      Inputs

      The accepted artifact set (after diff-review resolved with

      The accepted artifact set (after diff-review resolved withThe export target (one of the surface enum values from- 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).
    2. 02

      Surfaces

      Review the “Surfaces” section in the pinned source before continuing.

      Review and apply the “Surfaces” source section.
    3. 03

      Output

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

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

      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.

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

    Permission review

    Static risk signals and limitations

    No configured static risk pattern was detected

    This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

    Evidence record

    Why each signal appears

    EvidenceSourceComputedTestedEditorial
    SignalValueEvidence typeMeaning
    Quality score60/100ComputedDocumentation, specificity, maintenance, and trust rules
    Repository stars82,073SourceRepository attention, not individual Skill quality
    Compatibility0 platformsSourceDeclared in the catalog source record
    Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

    Pinned source

    Provenance and original SKILL.md

    Repository
    nexu-io/open-design
    Skill path
    plugins/_official/atoms/handoff/SKILL.md
    Commit
    89d6d4ef21baf80f871595abdf6f7de6e941dd44
    License
    Apache-2.0
    Collected
    2026-07-28
    Default branch
    main
    View the original 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

    surfacetypical follow-on
    clithe user runs od files read against the project; no extra push
    desktopopen the project in the OD desktop app
    webpublish to the public marketplace via spec §13's od:// deep link
    dockerwrap the artifact into a self-contained container (calls the §15.4 image)
    githubopen a PR via od plugin publish --to <catalog>
    figmaround-trip back into the figma-migration source file
    code-agenthand 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

    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.

    Alternatives

    Compare before choosing

    Computed 10042,015

    coreyhaines31/marketingskills

    ab-testing

    When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program

    2026-07-270 platforms
    Computed 1007

    event4u-app/agent-config

    design-intelligence

    Grounded design brief from the adopted corpus — style, WCAG-checked color tokens, typography, layout pattern, anti-patterns. Use on ui-design-brief or any which-style/palette/font/chart decision.

    2026-07-280 platforms
    Computed 1007

    event4u-app/agent-config

    existing-ui-audit

    Use BEFORE writing or editing any non-trivial UI — inventories components, design tokens, shadcn primitives, and reusable patterns into state.ui_audit. Hard gate for the ui directive set.

    2026-07-280 platforms
    Computed 1007

    event4u-app/agent-config

    testing-anti-patterns

    Use BEFORE writing/changing tests, adding mocks, or test-only methods on production classes — vs mocking-the-mock, production pollution, partial mocks, and overfit/tautological assertions

    2026-07-280 platforms