Skip to main content
skill CX Codex

robodojo-motion-control — Claude Code skill: IK and setup

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.

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 robodojo-motion-control -a claude-code
Open on GitHub

What robodojo-motion-control does

The skill explains RoboDojo waypoint planning and how to read recovery results after an IK rejection. It distinguishes the requested target_pose from a temporary execution endpoint, reported as execution_target_position and execution_target_quaternion.

Each waypoint still uses strict IK tolerances of 1 mm and 0.02 rad. After a rejected plan, RoboDojo may search once for a temporary goal within 80% of the original final position and orientation tolerances. The measured pose must still meet the original goal; there is no automatic return to its center.

It also covers ik_statistics, recovery.stats, rejection reasons, and execution feedback. A successful tool call does not prove that the robot arrived or grasped an object; check measured state and images. Endpoint checks do not guarantee collision-free motion along the full path.

What it helps with

  • interpret IK rejection counters after a failed move
  • tell a temporary recovery endpoint from the requested pose
  • check whether measured feedback confirms arrival
  • assess whether a grasp action proves object attachment

Example prompts for the agent

  • Explain the ik_statistics and recovery.stats after this move was rejected.
  • Compare target_pose with execution_target_position and describe the arm's endpoint.
  • Use feedback.pose_reached and the measured pose to assess whether the robot arrived.

How to install robodojo-motion-control

1Skills CLI (Vercel)

npx skills add Open-RUA/uni-robot-agent --skill robodojo-motion-control -a claude-code

2Manually: put the files in place

~/.claude/skills/motion-control/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/motion-control/

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

Questions about robodojo-motion-control

How do I install robodojo-motion-control in Claude Code?

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

What does robodojo-motion-control do?

It explains RoboDojo's native IK, temporary recovery goals, motion guards, and diagnostic counters. It also describes how to compare execution feedback with the robot's measured state.

What IK and recovery limits does the skill describe?

Waypoint IK uses tolerances of 1 mm and 0.02 rad. Following a rejection, RoboDojo may search once for a temporary endpoint within 80% of the original final tolerances, while measured arrival must still satisfy the requested goal.

Source text

SKILL.md · MIT
---
name: robodojo-motion-control
description: Interpret RoboDojo native IK, temporary recovery goals, motion guards and diagnostic counters.
---

# Interpret RoboDojo motion and recovery

Use `general/gripper/pose-targeting/SKILL.md` to construct pose targets and
`general/gripper/motion-recovery/SKILL.md` to choose a changed recovery from
observed evidence. The details below describe this backend, not other robots.

## Waypoint planning and temporary goals

Profiles set waypoint limits and final arrival tolerances; they add no approach
height. RoboDojo keeps strict native waypoint IK (1 mm / 0.02 rad). After a
planning rejection, one recovery search per move may choose a temporary execution
goal within 80% of the original final position and orientation tolerances.
The requested target remains unchanged for measured arrival checks. Read
`goal_recovery` and per-arm `execution_target_position`/`execution_target_quaternion`
to distinguish the route's temporary endpoint from the original `target_pose`.
There is no automatic return to the exact goal center or coarse-to-fine phase.
Choose tolerances that the intended operation permits before submitting move.

## Recovery diagnostics

Per-arm `recovery.rejected` records stages for finally rejected candidates.
`native_not_converged` and `native_constraint_rejected` are distinct; a candidate
can have both. `collision_or_native_constraint` means a sampled joint connection
failed a native constraint check, not necessarily that endpoint IK failed.

`goal_recovery` records the optional once-per-move final-region search. A found
candidate is only a temporary execution goal: subsequent waypoints still need
IK and measured arrival must satisfy the original goal's tolerances. There is
no automatic tightening phase. Inspect actual feedback before dependent actions.

## Execution feedback and limits

A successful tool call does not prove physical arrival or task success. Inspect
`feedback.pose_reached`, actual position/orientation, executed steps and stop
reason. `grasp` or `release` does not prove object attachment or detachment.
Use measured state and images to verify the intended effect.

The current native IK includes modelled self/table constraints. Other action
routes do not necessarily have identical checks. Endpoint checks and joint
jump guards do not establish collision-free swept motion; task objects, the
other arm and carried objects are not automatically represented by the public
robot geometry. Plan short observable approaches and check clearances.

This interface does not add a timed-trajectory guarantee. Control steps consume
native episode budget; model thinking and network delay are separate wall time.
On a partial or uncertain action, inspect returned state/status instead of
replaying the same physical request.

## IK recovery goals and counts

RoboDojo keeps each native waypoint solve at 1 mm / 0.02 rad. After a rejected
waypoint, move may search once for a temporary endpoint inside 80% of the original
final position/orientation tolerances. `target_pose` remains the requested goal;
`execution_target_position` and `execution_target_quaternion` identify the
possibly adjusted endpoint. `goal_recovery` reports that search, not physical
arrival. Actual pose must still satisfy the original tolerances; there is no
automatic return to the center or coarse-to-fine phase.

Primitive per-arm `recovery.stats` and move's aggregate `ik_statistics` count:

- `ik_requests`: one arm's strict waypoint planning request, including held arms
  when actually solved; arms skipped after an earlier rejection are not counted.
- `ik_request_failures`: requests still rejected after candidate recovery.
- `solver_calls` / `seeds_attempted`: 32 then 128 means two calls and 160 seeds.
- `candidates_returned`: distinct seed results, with the true top1/topN alias removed.
- `candidates_checked` / `candidates_rejected`: candidates examined / finally rejected.
  Raw and legal whole-turn representations are branches of one candidate.

`seed_budget` retains its existing meaning: the largest single solve's seed
budget, not the sum. Different seeds with equal joint vectors remain distinct.
`rejected` counts each finally rejected candidate at most once per stage; stages
can overlap, so their sum is not a count of failures. Raw top1 convergence, native
feasibility and pose errors are reported separately from its combined success.
`ik_candidate_rejected` covers validation/connection failures and mixed stages;
none of these finite searches proves the requested pose mathematically impossible.

The waypoint IK rejection rate is `ik_request_failures / ik_requests` when the
denominator is nonzero. Region-search calls are separately recorded under
`goal_recovery.diagnostics` and are excluded from that fraction. Do not sum move
aggregates and their primitive receipts together. Across logs, identify each
primitive request and arm once. `ik_statistics=null` means this backend provided
no such counters, not that zero IK requests failed.

## Recovery and episode stopping

IK failure and joint-jump rejection are recoverable planning feedback, not task
failure or an environment failure preventing interaction. While the task remains
incomplete, interaction is available and budget remains, continue recovery.
Neither one rejection nor repeated rejections justify finish, ending the turn,
or declaring the task impossible. Abandon an ineffective route, not the goal.

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

Similar skills

SKILL.md skills catalog →

From the same set41

The whole set →
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 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 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 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

Project sponsors

Companies that keep this analytics open