Skip to main content
skill CX Codex

pose-targeting — Claude Code skill for robot motion targets

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.

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 pose-targeting -a claude-code
Open on GitHub

What pose-targeting does

The skill explains how to set an absolute robot target using the registered grasp site's world position and fixed XYZ Euler angles. It covers converting the quaternion in control_pose, changing position or orientation independently, and computing rotations around world or tool-local axes. The target describes Cartesian motion, not individual wrist joints.

It separates motion into stages when clearance must come first: move while keeping orientation, inspect feedback, then send the turn. A single move interpolates position and orientation together. The skill also covers aligning a held part by its working feature and resuming an unfinished move without applying the relative angle again.

The current environment's robot description and published manual are needed for units, frames, and capability limits. A numerically valid target does not establish that the robot can reach it with adequate clearance.

What it helps with

  • set a robot target in world coordinates
  • convert a quaternion into Euler angles
  • stage translation before reorientation
  • align a held part's working feature with an opening

Example prompts for the agent

  • Set an absolute motion target and keep the current orientation.
  • Convert control_pose into a target for move.
  • Align the end of the held part with the opening.

How to install pose-targeting

1Skills CLI (Vercel)

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

2Manually: put the files in place

~/.claude/skills/pose-targeting/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/pose-targeting/

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

Questions about pose-targeting

How do I install pose-targeting in Claude Code?

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

What does pose-targeting do?

It explains how to define robot motion targets, convert quaternion orientation, and stage movement and rotation. It also covers aligning a held object's working feature.

What does pose-targeting need to work?

The current environment's robot description and published manual provide the units, coordinate frames, and capability limits. SciPy appears in a quaternion-conversion example, but is not presented as a required dependency.

Source text

SKILL.md · MIT
---
name: pose-targeting
description: Construct Direct pose targets with the correct position frame and rotation semantics. Use when switching motion tools, changing orientation, or aligning a held object's feature.
---

# Specify the point and orientation that must reach the goal

Choose the physical intent first: the approach direction, finger closing axis
and object feature needed for the next operation. A numerically valid pose
does not certify reachability, clearance or contact.

## Construct an absolute six-dimensional target

`move.targets[].pose = [x,y,z,roll,pitch,yaw]` describes the registered grasp
site in world metres and fixed/extrinsic XYZ Euler radians:
`R = Rz(yaw) @ Ry(pitch) @ Rx(roll)`. All six numbers are required.
Read `control_frame` and `grasp_site_description`; do not add a controller offset.
The site is not automatically the tip or working end of a held object.

State `control_pose` still contains position and a wxyz quaternion. Convert that
quaternion to fixed XYZ Euler angles before copying a measured pose into `move`.
For example, with SciPy in a code tool:

```python
from scipy.spatial.transform import Rotation
w, x, y, z = control_pose["quaternion"]
rpy = Rotation.from_quat([x, y, z, w]).as_euler("xyz").tolist()
pose = [*control_pose["position"], *rpy]
```

To translate without reorienting, retain measured RPY and change XYZ. To rotate
in place, retain measured XYZ and change RPY. To move and reorient together,
change both. These specify a Cartesian target, not particular wrist joints.
The wrist, fingers and held features may sweep arcs around the grasp site.

Profiles set waypoint limits and final arrival tolerances; they add no approach
height. Use the current tool contract for supported recovery behavior. If feedback
distinguishes a requested goal from an adjusted execution endpoint, inspect both
and verify measured arrival against the requested goal. Choose tolerances that
the intended operation permits before submitting move.
Select a pre-grasp offset from observed geometry. Preserve the distinction between
arrival tolerance, object localization uncertainty and contact margin; tightening
arrival cannot fix the wrong target.

## Preserve task constraints and stage order

Prefer an orientation this arm has reached when it suits the current contact,
finger closing direction and route. Do not copy orientations between arms merely
because positions appear symmetric. If IK rejects a target, the agent may choose
a different absolute orientation only when the task and held object allow it;
the tool does not search for or silently substitute one.

One `move` interpolates position and orientation together. It does not mean
"translate, then rotate". When clearance must be established first, move to the
clearance pose while preserving orientation, inspect the completed feedback and
images, then send the reorientation target. Likewise, verify pre-grasp arrival
before a dependent approach or close, and withdraw from an insertion before a
large turn. Combine translation and rotation only when their combined sweep is
appropriate. A two-arm target list coordinates steps; list order is not time order.

## Compute relative intent outside the tool

For a relative change, compute a new absolute orientation: a world-axis rotation
uses `R_goal = R_delta @ R_current`; a tool-local rotation uses
`R_goal = R_current @ R_delta`. Convert the result to fixed XYZ Euler radians.
Adding an angle to an arbitrary Euler component is not a general local-axis turn.
A held object's tip is a different pivot and may require a changed XYZ target.

If a call runs out of steps while making progress, continue toward the same
`feedback.arms[arm].target_pose` when the route is still valid. Do not add the
relative angle again. Euler wraparound and gimbal-lock representations can change
numbers without changing physical orientation; compare rotations, not component
subtraction. Quaternions q and -q are also equivalent. Read
`general/gripper/motion-recovery/SKILL.md` for rejection or lost progress.

## Example: the hand aligns but the object's tip misses

A long held part must enter an opening. Aligning the finger center with that
opening does not align an offset tip. Observe the tip and axis relative to the
hand, then choose the hand pose that places the entering feature appropriately.
After reorientation, update that relationship and check retention. A previous
world-axis offset cannot simply be reused after the object rotates.
Use `general/gripper/held-object-geometry/SKILL.md` for the feature relationship
and `general/gripper/placement-and-engagement/SKILL.md` for actual entry evidence.
If the tip is occluded, obtain useful evidence rather than assuming the hand
target proves alignment. Do not silently tighten tolerance to compensate for
targeting the wrong point.


## Schema example

This illustrates the request shape, not a recommended scene coordinate. Replace
the six pose values with the desired registered site pose from current evidence.

```json
{"profile":"precision","targets":[{"arm":"left","pose":[0.2,-0.1,0.9,0,0,0]}],"max_steps":12}
```

When metric opening calibration is exposed, move targets use `gripper_opening_m`.
Otherwise follow the declared opening parameter and units. Omit opening to preserve
the drive target. Native reviewer prefixes retain their declared convention; do
not convert them to metres unless their schema requires it.
Read the current environment's robot description and published manual for
units, frames and capability limits.

A supplied metric opening changes during the pose motion. Inspect targets_reached
and per-arm opening_reached as well as pose_reached; the pose can arrive first.
Omitting opening retains the complete drive intent and preserves closing preload.
It does not copy the measured gap. Use separate stages when full opening must
precede entry into a constrained region; keep independent work concurrent.

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

Similar skills

All skills for Science and research →
robotics-engineer rohitg00 robotics-engineer — a subagent that builds autonomous robots with ROS2: sensor drivers, perception, SLAM localization, motion planning, and real-time control loops. CX Codex ★ 2,858repo stars controlnet-pose prime-skills controlnet-pose — a skill for controlling pose and motion in video and image generation via RunComfy. Transfer movement from a source video to a target character, animate by pose, or generate images with depth or skeleton control. CX Codex +1 388,200installs tao-train-pose-classification NVIDIA Corporation tao-train-pose-classification is a Claude Code skill for training, evaluating, exporting, and running inference with a TAO ST-GCN classifier on pose-keypoint sequences. CX Codex +1 1,600installs configs-targeting launchdarkly configs-targeting — a skill for Claude Code and Codex that sets up LaunchDarkly AI config targeting rules. Controls percentage rollouts, user segments, and attribute conditions across environments. CX Codex +1 1,900installs fine-tuning-serving-openpi Orchestra Research fine-tuning-serving-openpi is a Claude Code skill with workflows for fine-tuning and serving OpenPI models pi0, pi0-fast, and pi0.5. It guides setup, norm stats calculation, and policy inference server deployment. CX Codex +1 1,000installs fine-tuning-openvla-oft Orchestra Research fine-tuning-openvla-oft guides fine-tuning and evaluation of OpenVLA-OFT robot action policies. Use it for LIBERO or ALOHA workflows with continuous action heads. CX Codex +1 1,000installs

From the same set41

The whole set →
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 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 contact-effect The contact-effect Claude Code skill checks contact by observing how the target responds and guides adjustments. It activates for new or uncertain contact, or after a change to grip, tool geometry, or support. CX Codex +1 ★ 488repo stars placement-and-engagement The placement-and-engagement Claude Code skill plans and checks object placement, support, containment, and mechanical engagement from visible features. It applies when receiver stability or relative geometry shapes the requested result. CX Codex +1 ★ 488repo stars state-verification The state-verification Claude Code skill checks object states and relationships using distinguishing evidence. It activates when a next step depends on whether an object is held, placed, or correctly oriented. CX Codex +1 ★ 488repo stars grasp-geometry This Claude Code skill selects grasp geometry based on exposed material, finger access, and the object's next use. It covers thin, hollow, crowded, or partly blocked objects. CX Codex +1 ★ 488repo stars

Project sponsors

Companies that keep this analytics open