Skip to main content
skill CX Codex

held-object-geometry — Claude Code skill: what it does and install

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.

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 held-object-geometry -a claude-code
Open on GitHub

What held-object-geometry does

The skill plans around the held object's actual pose. It identifies the lowest edge for clearance, an entering end and axis for engagement, or a working surface for tool contact. The feature is distinct from the hand center or the middle of an object mask.

After a turn, the hand-to-feature relationship must be transformed; after a slip or regrasp, refresh it before precise contact. Planning accounts for the full load and fingers, as well as the receiver opening. Relocalize that opening if it has moved.

The skill refers to general/gripper/grasp-geometry/SKILL.md, general/gripper/contact-effect/SKILL.md, and general/gripper/placement-and-engagement/SKILL.md. A feature hidden by fingers can look lower or smaller even when the object has not seated.

What it helps with

  • check clearance beneath the lowest corner of a held object
  • align an object's entering end with a receiver opening
  • plan approach and withdrawal around the load and fingers
  • refresh the object pose after a slip or regrasp

Example prompts for the agent

  • Check whether the held part's lowest corner clears the rim.
  • Align the tool's working end with the opening and account for finger clearance.
  • The object slipped in the grip; recalculate the working surface position.

How to install held-object-geometry

1Skills CLI (Vercel)

npx skills add Open-RUA/uni-robot-agent --skill held-object-geometry -a claude-code

2Manually: put the files in place

~/.claude/skills/held-object-geometry/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/held-object-geometry/

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

Questions about held-object-geometry

How do I install held-object-geometry in Claude Code?

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

What does held-object-geometry do?

It locates the part of a held object that matters for the next operation relative to the hand. That supports clearance checks, alignment, and tool contact planning.

What should be refreshed after an object slips?

Recalculate the relationship between the hand and the feature needed for the next precise contact.

Source text

SKILL.md · MIT
---
name: held-object-geometry
description: Locate the bottom, entering end or working feature of a held object relative to the hand. Use when clearance, placement or tool contact depends on the load's actual pose.
---

# Plan with the held object's actual features

Identify the feature needed for the next operation: the lowest edge for clearance,
an entering end and axis for engagement, or a working surface for tool contact.
Estimate its relation to the measured hand from a compatible observation. The
finger center, mask median and object center are not interchangeable features.
Use `general/gripper/grasp-geometry/SKILL.md` to keep the needed feature accessible.

## Preserve only geometry that remains valid

A held object can hang tilted or offset even when the hand reaches its requested
pose. Inspect its actual bottom, rim, long extent or working end rather than
assuming the initial grasp centered it. After reorientation, transform the
feature relationship with the new orientation and check that the grip did not
shift; a world-axis offset cannot simply be reused after rotation.

Slip, regrasp or support transfer invalidates the old hand-to-object relationship.
Refresh the affected feature before precise contact. Reuse a confirmed relation
through undisturbed motion; do not repeatedly measure the entire object.

## Check both the moving shape and the receiver

Plan approach and withdrawal for the whole load and fingers, including edges
below or beside the grasp. A hand above a rim does not establish clearance for
the lowest corner. Localize the receiving opening or support again if it moved;
an accurate held-object offset cannot compensate for a stale destination.

Separate hand tracking, retention and effective contact. A working end following
the hand establishes control of the tool, not its effect on the target. Use
`general/gripper/contact-effect/SKILL.md` for that effect and
`general/gripper/placement-and-engagement/SKILL.md` for the resulting relation.
When fingers obscure the deciding feature, choose a useful view or a supported
release and withdrawal if the operation permits it; an occluded mask can appear
smaller or lower without the object having seated.

## Case: the object is already aligned, but the hand looks rotated

The object's identifiable face and directed features already satisfy the required
world orientation, although the grasp-site yaw is nonzero. Preserve that useful object
orientation during transport when the route permits it. Zero grasp-site yaw is not an
object-alignment objective; an unnecessary loaded turn can shift the grip and
make the remaining route harder. Confirm alignment from distinguishing features,
not bbox aspect ratio alone. If rotation is required, choose it from the measured
hand-to-object relationship and available clearance, not an assumed centered grip.
After slip, regrasp or an unexpected turn, refresh the affected relationship before
using the old placement offset. When retention and geometry remain valid, reuse
them and inspect the released result without repeating localization at each move.

Before precise engagement, compare the actual working feature and its axis
with the receiver, then account for the fingers' approach and withdrawal space.
Do not translate a receiver coordinate directly into a gripper-center target
without the supported hand-to-feature relationship. A tighter motion tolerance
cannot repair an incorrect feature offset or stale held orientation.

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

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set41

The whole set →
deformable-material The deformable-material Claude Code skill moves selected regions of flexible material and checks their shape after release. It applies when deformation makes rigid-object poses or earlier contact coordinates unreliable. CX Codex +1 ★ 488repo stars contents-transfer contents-transfer — a skill for Claude Code that transfers loose contents from a held vessel into a receiver. It tracks outlet alignment, flow, and what remains. CX Codex +1 ★ 488repo stars 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 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 handover 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. 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

Project sponsors

Companies that keep this analytics open