Claude Cursor Skill

mujoco

Build and debug lightweight robot manipulation simulations with MuJoCo.

LLM Mart · 0 points · 2 views 0 listing impressions 0 install-command copies
Download robium-ai-robium-skills_mujoco-b4e9f75.zip · 4 KB

Install

skills CLI npx skills add https://github.com/robium-ai/robium/tree/main/skills/mujoco
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install robium-ai-robium@llmmart
Git git clone https://github.com/robium-ai/robium.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole robium-ai/robium collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

MuJoCo

A plausible render proves little by itself. Follow the physical chain from model through kinematics, actuation, contact, and observation.

Start from the model

  • For a first interactive tryout, new app, or first policy demo, read architect before creating a scene, controller, or viewer or downloading a model collection. Reuse its compatible reference-app selection if already made. Existing-model edits, physics debugging, and explanations stay here.
  • Read the MJCF and the pinned asset revision before adding control code. Check joint ranges, actuator limits, collision geometry, sites, masses, and the intended work surface.
  • Prefer a maintained model from MuJoCo Menagerie, but verify it against the real robot and task envelope.
  • Confirm gripper polarity, fingertip gap, and contact geometry empirically. Names and documentation can disagree with the model that actually runs.
  • Use the current MuJoCo documentation for MJCF and Python APIs rather than carrying signatures forward from memory.

Follow the physical chain

  • Kinematics: solve only for reachable targets and check the residual; damped least-squares can return a poor local solution without raising.
  • Actuation: compare commanded position or torque with joint state, actuator force, range limits, and saturation.
  • Contact: inspect which geoms belong to the gripper and object. Unnamed mesh geoms make name-only contact filters unsafe.
  • Grasp: calibrate the grasp point, approach path, wrist orientation, and lift together. The end-effector site is not automatically the physical pinch point.
  • Observation: make cameras and renderer lifecycle deterministic before using frames as training or regression data.
  • Controls: distinguish model state, actuator limits, and rounded UI ranges. Clamp reset values to the actual widget bounds before binding them; a physically valid state can still be rejected by a narrower control.

Go deeper only when needed

  • For reachability, collision, grasp, saturation, and rendering symptoms, read FAILURES.md.
  • For the measured SO-arm and macOS evidence from Robium's manipulation trial, read SO-ARM-MACOS.md. Preserve its numbers only with the stated model, scene, hardware, and renderer conditions.
  • Use LeRobot guidance when the boundary reaches datasets, policies, or evaluation; use simulator-selection guidance when MuJoCo itself has not yet been chosen.

Done

  • The intended workspace is reachable, commands produce the expected joint and contact state, grasps survive a lift across representative poses, and seeded resets produce acceptably stable observations.
Files (robium)
  • FAILURES.md 2.8 KB
    Loading…
  • SKILL.md 2.9 KB
    ---
    name: mujoco
    description: Build and debug MuJoCo robot simulations. First interactive robot tryouts start with architect's reference-app selection.
    ---
    
    # MuJoCo
    
    A plausible render proves little by itself. Follow the physical chain from
    model through kinematics, actuation, contact, and observation.
    
    ## Start from the model
    
    - For a first interactive tryout, new app, or first policy demo, read
      [architect](../architect/SKILL.md) before creating a scene, controller, or
      viewer or downloading a model collection. Reuse its compatible reference-app
      selection if already made. Existing-model edits, physics debugging, and
      explanations stay here.
    - Read the MJCF and the pinned asset revision before adding control code. Check
      joint ranges, actuator limits, collision geometry, sites, masses, and the
      intended work surface.
    - Prefer a maintained model from
      [MuJoCo Menagerie](https://github.com/google-deepmind/mujoco_menagerie), but
      verify it against the real robot and task envelope.
    - Confirm gripper polarity, fingertip gap, and contact geometry empirically.
      Names and documentation can disagree with the model that actually runs.
    - Use the current [MuJoCo documentation](https://mujoco.readthedocs.io/) for
      MJCF and Python APIs rather than carrying signatures forward from memory.
    
    ## Follow the physical chain
    
    - **Kinematics:** solve only for reachable targets and check the residual;
      damped least-squares can return a poor local solution without raising.
    - **Actuation:** compare commanded position or torque with joint state,
      actuator force, range limits, and saturation.
    - **Contact:** inspect which geoms belong to the gripper and object. Unnamed
      mesh geoms make name-only contact filters unsafe.
    - **Grasp:** calibrate the grasp point, approach path, wrist orientation, and
      lift together. The end-effector site is not automatically the physical pinch
      point.
    - **Observation:** make cameras and renderer lifecycle deterministic before
      using frames as training or regression data.
    - **Controls:** distinguish model state, actuator limits, and rounded UI
      ranges. Clamp reset values to the actual widget bounds before binding them;
      a physically valid state can still be rejected by a narrower control.
    
    ## Go deeper only when needed
    
    - For reachability, collision, grasp, saturation, and rendering symptoms, read
      [FAILURES.md](FAILURES.md).
    - For the measured SO-arm and macOS evidence from Robium's manipulation trial,
      read [SO-ARM-MACOS.md](SO-ARM-MACOS.md). Preserve its numbers only with the
      stated model, scene, hardware, and renderer conditions.
    - Use LeRobot guidance when the boundary reaches datasets, policies, or
      evaluation; use simulator-selection guidance when MuJoCo itself has not yet
      been chosen.
    
    ## Done
    
    - The intended workspace is reachable, commands produce the expected joint and
      contact state, grasps survive a lift across representative poses, and seeded
      resets produce acceptably stable observations.
    
  • SO-ARM-MACOS.md 3.2 KB
    Loading…

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.