# ManiSkill panda PushCube-v1 motion planner: robotics skill example

Push a cube to a goal region with the official Panda motion planner.

## Task and environment

maniskill | 3.0.0b22 | panda | pd_joint_pos | linux | 3.10

## Example input

```json
{
  "task": "PushCube-v1",
  "seed": 0,
  "robot": "panda",
  "controller": "pd_joint_pos",
  "obs_mode": "state",
  "sim_backend": "cpu",
  "render_backend": "none",
  "reward_mode": "sparse",
  "max_episode_steps": 1000
}
```

## Retrieve and prepare

Read https://hub.superfastrobotics.com/skills/maniskill-panda-push-cube/skill.json or https://api.superfastrobotics.com/v1/skills/maniskill-panda-push-cube?hub_commit=ede75c00118e9808e5099da43c26f4619cc3bc37&record_version=1.1.0&include=experience without installing a client. Inspect the license, exact environment and evidence before preparation. Preparation and execution remain separate.

Source: https://github.com/haosulab/ManiSkill at 33967b9e3ead1f841eec57cc9f31d0d8b8cf0907. Record version: 1.1.0.

## Success condition

PushCube-v1 env info.success is true after the upstream solver finishes, truncated is false, and 0 < elapsed_steps < max_episode_steps=1000; only then status is task_complete and exit is 0. The 1000-step motion-planning horizon is a Hub recipe condition, not the upstream default benchmark horizon.

## Recorded evidence

task_complete: PushCube-v1 seed 0 completed in the explicit Hub 1000-step motion-planning episode: success=true, terminated=true, truncated=false, elapsed_steps=71, exit=0 and no 180-second process timeout (4.575 seconds task process time). The same maintainer agent explicitly selected the panda-transport named batch; each task ran once. This verifies only the recorded CPU/state configuration and seed, not the upstream default benchmark, multiple-seed reliability, fresh blind discovery, public adoption, hardware or camera modes.

This page is a data-only example and performs no execution.