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
controllersSelect, validate, and extend robosuite controllers, controller configs, action splits, and custom robot composition.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill for controller selection, controller-config validation, action-split inspection, custom robot composition, and third-party composite controller routing.
references/controller-configs-and-actions.mdreferences/robots-grippers-and-bases.mdreferences/third-party-controllers.mdreferences/troubleshooting.mdscripts/print_action_info.py — print JSON action splits for an env / robot / controller configscripts/validate_controller_config.py — validate composite controller JSON shape and common omissionsload_composite_controller_config(robot="Panda")load_composite_controller_config(controller="BASIC")load_composite_controller_config(controller="/path/to/controller.json")load_part_controller_config(default_controller="OSC_POSE")robot.create_action_vector({"right": np.zeros(6), "right_gripper": np.array([0.0])})create_composite_robot("CustomPanda", robot="Panda", base="RethinkMount", grippers="PandaGripper")Included:
load_composite_controller_configload_part_controller_configBASIC, HYBRID_MOBILE_BASE, WHOLE_BODY_IKaction_split_indexesrobot.create_action_vectorcreate_composite_robotExcluded:
../environments for suite.make(...) examples../teleoperation for device-to-action conversion../modeling for custom robot XML checksWHOLE_BODY_MINK_IK is optional and reference-only; current verification did not include mink.robosuite_models adds extra robots, grippers, and bases when installed, but it is optional.