Community

Contribute

The Imitator Game is an open-source community for robot imitation from human video. Everyone is welcome to contribute tasks, models, embodiments, assets, demonstrations, or evaluation ideas through the shared design templates and reproducible protocols.

How to grow the benchmark

Anyone interested in imitative ability (goal-directed imitation, video-conditioned policies, cross-embodiment skill transfer, intent inference, affordance adaptation, ...) is welcome to participate. The project grows through four connected contribution paths, all gated by the same design templates and evaluation contracts. Contributions should include enough information for maintainers to reproduce and evaluate them:

Tasks

Contribute new Imitator tasks (L0–L3) designed with the task template under mani_skill/envs/tasks/_template/, together with their motion-planning solutions. Accepted tasks can then be added to the benchmark task set, task mapping, and collection pipeline.

Models

Contribute new imitation-learning models built on the baseline template under examples/baselines/_template/, together with the evaluation interface and training/evaluation recipe needed for reproducibility.

Embodiments / assets

Contribute new robots using the robot template under mani_skill/agents/robots/_template/ and diverse scene assets. New assets should follow the documented asset pipeline and licensing requirements.

Real-world evaluation

Submit a reproducible model package and simulation environment through the shared protocol. After the simulation package is reviewed, contributors may request deployment on our real-robot platform under the agreed evaluation conditions.

Pairing service

Human demonstration data is only useful for imitation when it is paired with robot trajectories. For accepted community-contributed tasks, we may collect human and robot pairing demonstrations and merge the paired data into IG-10K-format datasets under the shared LeRobot format.

Request pairing

Community members can request pairing for accepted tasks. Pairing is coordinated after the task protocol, reset conditions, and evaluation standard are agreed with maintainers.

Real-device paired data collection

For an accepted task, contributors can provide the human demonstration and task protocol while the project team determines whether matching robot demonstrations can be collected. When available, paired episodes can be released alongside simulated data under the IG-10K / LeRobot contract.

See the data collection guide for preparation details and the Task Gallery for published human, simulated, and real-robot rollouts.

Submit a model or simulation environment

We accept more than standalone checkpoints. To request a real-world evaluation, submit a reproducible bundle through a pull request. Include the model checkpoint or source, inference API, environment dependencies, license, task protocol, reset conditions, task-specific evaluation standard, and commands needed to reproduce inference. We first reproduce the simulation result before scheduling hardware time.

Use the contribution protocol

Open a pull request with the model or environment package, a short README, the relevant task IDs and L0–L3 levels, checkpoint or asset locations, licensing information, dependencies, and simulator-side evaluation results. Maintainers confirm that the bundle is reproducible before considering real-robot evaluation. The repository does not currently provide an automatic policy-upload endpoint.

Real-world deployment and evaluation

After the simulation package is reproducible and passes review, contributors can request deployment on the real-robot platform. The team runs the agreed evaluation protocol and records rollout videos and evaluation conditions.

Hardware runs are scheduled only after the package is reproducible. Approved real-world rollouts can be added to the Imitator Arena for blind A/B comparison against the same human reference.

Publish results to Imitator Arena

Once a real-world evaluation is complete, we can add the approved rollouts to Imitator Arena. The Arena presents a human reference and anonymous model rollouts for blind A/B human evaluation, turning a private hardware run into a public, community-readable comparison.

From submission to public comparison

The complete path is: submit a reproducible package, reproduce the task in simulation, request real-robot deployment, run the agreed evaluation, and publish approved rollouts to the Imitator Arena. The Gallery keeps the underlying videos discoverable.

Contribution workflow

  1. Follow the design templates: examples/baselines/_template/ for models, mani_skill/envs/tasks/_template/ for L0–L3 tasks, and mani_skill/agents/robots/_template/ for robots.
  2. Open a pull request with your task, model, robot, embodiment, or asset contribution.
  3. Maintainers review the contribution against the templates (data contract, environment contract, L0–L3 semantics, motion-planning solution).
  4. Once accepted, the contribution is merged, registered, and, where applicable, considered for human/robot pairing and release.
  5. For real-world evaluation, provide the reproducible model or source, API, dependencies, license, task protocol, reset conditions, evaluation standard, and simulator results.
  6. After review, request deployment on the real platform; hardware runs are scheduled only after the package is reproducible.
  7. Approved real-world rollouts are published in Imitator Arena for blind A/B community evaluation and linked from the Task Gallery.

Active ManiSkill sync

We keep the simulation framework actively updated with the upstream ManiSkill repository so the community can use the latest simulation features. To keep the ecosystem coherent, all contributions must follow the shared ManiSkill design templates — the robot agent template, the environment interface, and the motion-planning interface are the same ones the upstream project documents. If you build on a new ManiSkill feature, please keep the common interfaces intact.

Join the community

Questions about the benchmark, data, or a potential contribution are welcome. Use whichever community channel is most convenient:

Discord

Join the project community for announcements, technical discussion, and collaboration.

Join on Discord

WeChat community

For Chinese-language discussion, scan the QR code to join the project group.

QR code for The Imitator Game WeChat group
Scan to join the WeChat group

For direct technical inquiries, contact Xunzhe Zhou.

Citation

bibtex
@unpublished{imitatorgame2026,
  title={The Imitator Game: Benchmarking Robot Imitative Ability Beyond Action Prediction},
  author={Zhou, Xunzhe and Cai, Yiyang and Wang, Fengyi and Ju, Ran and Ren, Hanxiang and Liu, Ruizhe and Zhang, Yu and Luo, Qian and Chen, Feng and Zhou, Pei and Ma, Yi and Yang, Yanchao},
  url={https://github.com/imitator-game/The-Imitator-Game},
  year={2026}
}
Start here

New to the codebase? Follow the installation and quickstart guides, then build your first task with creating a new task.