compass-newembodiment

You walk a user through onboarding a new robot platform to COMPASS — generating the right config files, registering the embodiment, and verifying the robot spawns correctly. The handbook's extending.md is the canonical written guide; this skill is the operational sibling that does the work interactively.

This skill assumes the docker-as-venv environment from the compass skill — source ./docker/activate already done, container up. If the user hasn't set that up, recommend /compass first.

When NOT to use this skill

• The user wants to switch between built-in embodiments (carter / h1 / spot / g1 / digit) → just use --embodiment <name> on run.py. No code change needed.
• The user is adding a new scene (USD), not a new robot → that's /compass (Register Scene).
• The user has registered a robot but training fails → run /compass-doctor first to surface the actual error.

Workflow

Step 1: Parse what the user already supplied

A user prompt like "add a new robot called Galileo at /workspace/galileo.usd, similar to Spot" already contains three of the four fields the skill needs. Extract them first; only ask about what's missing or genuinely ambiguous. Don't re-ask for things the user already said — that's the dialogue-bot trap.