Use an SSH machine

ssh-keygen -t ed25519
cat ~/.ssh/id_ed25519.pub

ssh-keygen -t ed25519
Get-Content $env:USERPROFILE\.ssh\id_ed25519.pub

him login
him machine launch --key ~/.ssh/id_ed25519.pub --profile gpu --hours 6
# The command waits for Ready and prints the exact ssh command.

# Later, always stop it explicitly:
him machine stop <machine-id>

cd /workspace
python3 --version
nvidia-smi  # GPU machines only
git clone YOUR_REPOSITORY_URL
cd YOUR_REPOSITORY
# Install this repository's declared dependencies.

Help me prepare and upload this robotics project to HIM Arena.

First ask me only for details you cannot discover here: whether this is a policy, simulator, both, or a creative project; the robot; the simulator (MuJoCo, Isaac Lab, Brax, custom, or not applicable); the project name; and the command that produces the result. Then:

1. Read the repository instructions, README, git status, dependency files, tests, and existing run or render commands. Keep the project's current simulator, trainer, model formats, and layout.
2. Run the shortest meaningful test or simulation. Use its real output; do not invent scores, training claims, or hardware readiness.
3. Produce or locate one playable result.mp4 and inspect it. It must contain a real video track and be 50 MB or less. If the project cannot produce video, explain the smallest missing step instead of substituting fake footage.
4. Prepare one ZIP containing only the source and small assets needed to reproduce the result. Exclude .git, secrets, .env files, datasets, intermediate checkpoints, unused weights, logs, caches, and virtual environments. Include a final inference checkpoint only when the verified run requires it and it fits the upload limit. The ZIP plus MP4 must be 100 MB or less.
5. Show me the exact run command, test results, ZIP inventory, file sizes, and the proposed public name and caption. Ask before uploading.
6. If the HIM CLI is missing, install it with: curl -fsSL https://arena.himrobotics.com/install.sh | sh
7. Check authentication with him whoami --json. If login is needed, tell me to run him login and enter my developer token only in its hidden prompt. Never ask me to paste a token into chat.
8. After I approve, upload with:
   him upload ./PROJECT.zip --video ./result.mp4 --kind [policy|simulator|both|creative-project] --robot [microduck|unitree-g1|agibot-x2|unitree-h1|unitree-go2|booster-k1|booster-t1|yam|so-101|franka-panda|other] --simulator [mujoco|isaac-lab|brax|custom|not-applicable] --name "[name]" --caption "[what the video shows]" --run-command "[verified command]" --yes --json
9. Return the project URL, upload ID, exact files uploaded, test evidence, and limitations. The video, metadata, and ZIP are public; the ZIP stays quarantined and is labeled as unreviewed code.

Optional data: after signing in, use him data download table-tennis to get HIM's account-gated data. To upload a private dataset, create and validate a Dataset Manifest, then use him dataset push with one --file URI=PATH mapping per artifact. Ask before large downloads or data uploads.

Do not create a .him directory unless I explicitly ask for an immutable package, CI validation, controlled scoring, or another advanced package workflow. Do not launch paid compute unless I explicitly ask for it and approve the budget.