Skip to main content
skill CX Codex

handover · open-rua — Claude Code skill for transferring objects between hands

The handover Claude Code skill transfers an object held by one robot hand to another. It is triggered for hand-to-hand transfers, not ordinary placement with a single arm.

MIT ★ 488 updated 2026-11-15

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add Open-RUA/uni-robot-agent --skill handover -a claude-code
Open on GitHub

What handover does

The skill lays out a staged transfer: the receiving hand grips exposed material while the donor continues to hold the object. The receiver’s fingers must visibly enclose the object before the donor releases it. Then the agent checks that the receiver alone retains the object and carries it briefly to confirm it has not slipped.

The procedure uses view_env_state for inspection and relies on the common attachment checks in general/SKILL.md. Current arm geometry guides each approach; coordinates from an earlier episode are not reused. The donor stays closed during the transfer until the receiver passes its grip check.

For VLA, the agent handles one phase at a time and inspects the result after each actor_act call, since it cannot inspect between internal chunks. If the receiver misses, it keeps the donor supporting the object, adjusts the approach, and tries again.

What it helps with

  • transfer an object held by one robot hand to another
  • confirm that the receiving hand retains an object without donor support
  • retry a missed grasp while keeping the donor closed
  • find an alternate approach when the donor arm blocks the receiver

Example prompts for the agent

  • Transfer the object from the right robot hand to the left, then verify that the left hand holds it alone.
  • Hand the object over while keeping the donor grip until the receiver passes its retention check.
  • Retry the transfer: the receiving fingers closed beside the object instead of around it.

How to install handover

1Skills CLI (Vercel)

npx skills add Open-RUA/uni-robot-agent --skill handover -a claude-code

2Manually: put the files in place

~/.claude/skills/handover/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/handover/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about handover

How do I install handover in Claude Code?

Run npx skills add Open-RUA/uni-robot-agent --skill handover -a claude-code. The skill file is placed at ~/.claude/skills/handover/SKILL.md.

What does handover do?

It guides a robot through transferring an object between two hands. The receiver’s grip is checked before the donor releases, then the receiver’s independent hold is verified.

What checks does handover require?

It starts with the attachment checks in general/SKILL.md. After the receiver closes, its fingers must visibly enclose the object; after the donor releases, the receiver must retain it alone.

Source text

SKILL.md · MIT
---
name: handover
description: Transfer a held object between two available robot hands while preserving support and verifying independent receiver retention. Use for hand-to-hand transfer, not ordinary single-arm placement.
---

# Transfer support between hands

Use after the common attachment checks in `general/SKILL.md`.
Name the donor, receiver and intended object. Choose the receiving grasp for
the next operation, leaving an insertion tip or required placement face free.
Use current geometry; do not replay coordinates from another episode.

## Present an accessible grasp

- Confirm the donor actually holds the intended object. A wrist image centered
  on an object still at its source is not attachment evidence.
- Select a presentation pose both arms can reach with clearance for the whole
  object, fingers and forearms. Check that the receiver can approach the
  exposed material without occupying the donor's grasp region.
- Keep the donor closed while moving to that pose. Separate large changes in
  orientation from the receiver's final approach and inspect for slip after each.
- Hold the donor approximately stationary during receiver alignment. Approach
  with the receiver open; use view_env_state at alignment and contact checkpoints
  to inspect useful wrist and head views. If the donor obstructs the grasp, change the presentation
  while preserving its support rather than driving the receiver through it.

## Close, transfer support, then verify

1. Align receiver fingers around exposed object material, not around the donor
   fingers. Close the receiver while the donor continues supporting the object.
2. After receiver closure completes, inspect its attached wrist image (or VLA's
   final images); use view_env_state if another view is needed. Require visible
   enclosure of the intended object by the
   receiving fingers; closure or a valid tool return alone is insufficient.
   Two hands touching the object do not yet prove independent receiver retention.
3. Keep the receiver closed and approximately stationary while releasing the
   donor. Separate the open donor a short distance along a clear route, then
   call view_env_state to inspect whether the receiver alone retains the object.
   In parallel, do not queue donor release before the enclosure check or a long
   receiver carry before this independent-retention check.
4. Make a short receiver carry and verify the object follows without visible
   slip. Only then mark handover complete and continue toward the destination.

For Direct calls, preserve the holding hand's closed command during each
phase. For VLA, describe one phase at a time near closure and release; inspect
the result after each whole actor_act call. Use separate calls when an enclosure
or retention check must precede the next phase; the main agent does not inspect
between internal chunks. `constraints.gripper_openings_m` (or normalized `constraints.gripper_targets`,
when declared by the schema) fixes a hand's opening throughout the
whole call, so do not fix a hand that must close or release during that call.

## Recover without losing the remaining support

- If the receiver closes beside the object or the intended material remains
  outside its fingers, keep the donor closed and stationary. Reopen the receiver,
  correct its position relative to the visible material, and close again. Do not
  translate closed receiver fingers through the donor's grip to fix a miss.
- If a top-down receiver path is blocked by the donor or its forearm, retract
  the open receiver and inspect a side-entry route to exposed material. Change
  the donor's presentation only while its grip remains secure; inspect retention
  and the new corridor before another receiver approach. Do not rotate both
  hands around an unverified shared grip.
- For thin coins, slices or a broom handle, distinguish graspable object material
  from the donor fingers. If a mask selects the robot, clear the occlusion and
  remeasure. Repeated receiver misses call for a different exposed region or
  presentation, not another closure at the same relationship.
- If the object slips during support transfer, inspect its actual location
  before another move. When it still has donor support, recover receiver alignment;
  when it has fallen, reopen the acquisition subgoal at its new location and
  invalidate the old transfer poses. Do not move both closed hands apart and pull
  against the object.
- When intermediate placement is allowed, a stable support reachable by both
  hands can divide an otherwise unreachable route. Check the resting orientation
  and regrasp region before release; laying a thin object flat can remove its
  useful edge. This is a new placement and acquisition, not a substitute for an
  explicitly required hand-to-hand transfer.

© Open-RUA · MIT · Open-RUA/uni-robot-agent

Similar skills

SKILL.md skills catalog →

handover by other authors comes first.

handover adobe Generates handover documentation for an AEM Edge Delivery Services project: separate guides for content authors, developers and site administrators. CX Codex +1 1,600installs handover Paweł Huryn This Claude Code skill writes a handover for the next agent session. It checks the project against the files on disk and records verified facts, unfinished work, and a concrete next step. CX Codex +1 ★ 741repo stars handover-developer adobe handover-developer generates technical handover guides for AEM Edge Delivery Services codebases. Useful when onboarding engineers or documenting block architecture. CX Codex +1 773installs handover-admin adobe handover-admin is a Claude Code skill that creates admin documentation for AEM Edge Delivery Services projects. It runs for an admin handoff, a new site administrator’s onboarding, or procedure writing. CX Codex +1 770installs account-handover PostHog account-handover drafts structured handover briefings when transferring PostHog accounts between TAMs or CSMs. CX Codex +1 193installs seat-continuity-and-handover mvschwarz The seat-continuity-and-handover skill for Claude Code covers replacing an agent while keeping its seat identity stable. It separates creating a successor from binding it to the seat and recording the transition. CX Codex +1 ★ 8,928repo stars find-skills vercel-labs find-skills is a Claude Code skill that locates agent skills for a task and helps assess the results. It activates when someone asks for a capability that may already be installable. CX Codex +1 4,400,000installs frontend-design official anthropics The frontend-design skill guides intentional visual design for new interfaces and redesigns. Use it when a generic generated UI is not enough. CX Codex +1 1,025,790installs agent-browser vercel-labs This Claude Code skill automates browser interaction for tasks like navigating sites, filling forms, and testing web apps. It also supports exploratory QA and Electron app automation. CX Codex +1 1,600,000installs design-taste-frontend Leonxlnx The design-taste-frontend Claude Code skill sets design rules and checks for websites. It activates for new pages, redesigns, and requests to fix a generic-looking site. CX Codex +1 802,600installs

From the same set41

The whole set →
moving-target-control The moving-target-control Claude Code skill plans contact with moving physical objects and checks whether a grasp holds. It activates when a target or receiver may move during approach or transfer. CX Codex +1 ★ 488repo stars return-to-start return-to-start — a skill for Claude Code and Codex guides robotic arms back to their measured starting poses. Verifies position and orientation tolerances before ending the movement. CX Codex +1 ★ 488repo stars held-object-geometry The held-object-geometry Claude Code skill locates a held object's relevant feature relative to the hand. It applies to clearance checks, placement, and tool contact during robot motion. CX Codex +1 ★ 488repo stars reachability-and-recovery The reachability-and-recovery Claude Code skill selects an arm, approach, and permitted relay for a complete gripper route. It activates when the destination is hard to reach or an existing route needs reassignment. CX Codex +1 ★ 488repo stars scene-memory The scene-memory Claude Code skill tracks object identities, reference states, and event order. It activates when an agent’s next action depends on an earlier observation, a demonstration, or another actor’s move. CX Codex +1 ★ 488repo stars robodojo-motion-control The robodojo-motion-control Claude Code skill explains RoboDojo motion planning, IK recovery, and diagnostic counters. It helps interpret why a robot did not reach its requested pose. CX Codex +1 ★ 488repo stars supported-contact The supported-contact Claude Code skill plans object contact and the assisting hand’s motion. It activates when a held load needs a receiver adjusted or restrained at the same time. CX Codex +1 ★ 488repo stars pose-targeting The pose-targeting Claude Code skill builds robot motion targets from a position and orientation. It activates for tool changes, reorientation, and aligning a feature on a held object. CX Codex +1 ★ 488repo stars

Project sponsors

Companies that keep this analytics open