executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
mdp-componentsUse mjlab built-in actions, actuators, observations, rewards, terminations, events, commands, curricula, metrics, and task-specific MDP terms.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when a task asks which mjlab MDP term, action config, actuator config, command generator, reward, termination, curriculum, or built-in task-family component to use.
| Need | Typical mjlab surface |
|---|---|
| Drive joints from policy output | JointPositionActionCfg, JointVelocityActionCfg, JointEffortActionCfg, or RelativeJointPositionActionCfg |
| Reuse XML actuators | XmlActuatorCfg on EntityArticulationInfoCfg |
| Stable implicit PD in MuJoCo | BuiltinPositionActuatorCfg, BuiltinPdActuatorCfg, or BuiltinDcMotorActuatorCfg |
| Explicit torque/PD/DC dynamics | IdealPdActuatorCfg, DcMotorActuatorCfg, LearnedMlpActuatorCfg |
| Robot target lookup | SceneEntityCfg with joint/body/geom/site/actuator names |
| Standard observations | mjlab.envs.mdp.observations functions |
| Standard penalties/rewards | mjlab.envs.mdp.rewards plus task-family rewards |
| Episode stop logic | mjlab.envs.mdp.terminations and task-family terminations |
| Reset or perturb states | EventTermCfg with event functions |