Run dynamics validation and smoke tests on robosuite robot XMLs.
npx skills add https://github.com/axel-kaliff/dotfiles --skill validate-robot
Please help me install this Agent Skill. Skill: validate-robot Source: https://github.com/axel-kaliff/dotfiles/tree/main/claude/.claude/skills/validate-robot Command: npx skills add https://github.com/axel-kaliff/dotfiles --skill validate-robot
Detects dynamics and simulation issues in robosuite robot XMLs that cause unstable solvers, placeholder inertias, gravity-driven divergence, stuck actuators, or NaN/Inf during simulation, reducing time spent debugging low-level physics and controller problems.
Run validate-robot with the robot name and optional XML path to perform dynamics validation and smoke tests and return a PASS/FAIL summary with remediation suggestions.
High-intent search queries and answers about installing and using this skill.
Dynamics validation runs deterministic checks on robosuite robot XMLs to detect solver instability, placeholder inertias, gravity-driven divergence, actuator failures, and NaN/Inf issues. It extracts joint names and initial qpos from registration files to provide accurate inputs.
Simulation divergence and NaN/Inf issues often stem from placeholder inertias, solver instability, or gravity-driven divergence. Running a dynamics validation smoke test surfaces these specific physics failures and provides targeted remediation tips for each failed check.
Running dynamics validation and smoke tests after XML or physics changes catches regressions before integration testing. The workflow locates the correct cached robot XML, extracts joint lists from registration files, and reports PASS/FAIL results with actionable suggestions.
Yes, smoke tests run alongside dynamics validation to surface solver stability, mass sanity, gravity stability, and actuator response issues. The test operates on cached robot XMLs or source files and reports each check as PASS or FAIL.
Yes, the validation workflow requires locating the correct XML and registration file to extract joint names and initial qpos. These extracted values provide accurate inputs to the project's validation and smoke-test commands.
Impratio conflicts and insufficient ctrlrange are common actuator and solver failure modes detected during dynamics validation. The validation workflow reports these as FAIL and provides targeted remediation tips to resolve the physics configuration issues.
Ranch-Hand-RoboticsCreate, structure and validate URDF robot description files.
dmae97Map multi-agent runtime failures to a feedback control loop diagnosis.
phuetzAutomate Ableton Live control via OSC, MIDI scripting, and Max for Live.
ZurybrTune MuJoCo MJCF simulation parameters to balance speed and physics accuracy.
