mjlab-skillkit

Migrate IsaacLab projects to mjlab-native code while preserving behavioral parity.

102|7|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/cmjang/mjlab-skillkit --skill mjlab-skillkit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mjlab-skillkit
Source: https://github.com/cmjang/mjlab-skillkit/tree/main
Command: npx skills add https://github.com/cmjang/mjlab-skillkit --skill mjlab-skillkit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill kit provides two integrated capabilities to AI coding assistants: an IsaacLab Migration Skill to translate IsaacLab projects into mjlab-native implementations while preserving behavior, and an mjlab Native Skill to author new mjlab-native tasks, configs, sensors, and mesh workflows directly from local or bundled mjlab docs and examples.

Core Features & Use Cases

  • IsaacLab Migration Skill: preserves task behavior during migration, maps IsaacLab concepts to mjlab APIs, and generates migration playbooks with API mappings, checklists, and complex-task strategies.
  • mjlab Native Skill: enables authoring of EnvCfgs, scene configs, managers, sensors, RL wiring, and mesh workflows, reusing local examples first and bundled references second.
  • Adapts workflows for multi-tool AI assistants by promoting a standalone, mjlab-native task package structure and a registry-based discovery flow.

Quick Start

Load the two core capabilities and begin by choosing migrate for IsaacLab projects, then switch to author for mjlab-native task creation.

Frequently Asked Questions about mjlab-skillkit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate IsaacLab projects to mjlab-native code?

To migrate IsaacLab projects to mjlab-native code, use the migration mode to map IsaacLab concepts to mjlab APIs while preserving behavioral parity. It generates migration playbooks with API mappings, checklists, and complex-task strategies.

What is the best way to author new mjlab-native tasks and scene configs?

Authoring new mjlab-native tasks and scene configs is best done using the native authoring mode. It guides layout and scope for EnvCfgs, managers, sensors, RL wiring, and mesh workflows, reusing local examples first and bundled references second.

Does mjlab-native authoring enforce official dict-based manager configurations?

Yes, mjlab-native authoring strictly enforces official dict-based manager configurations and mjlab API usage. It actively avoids compatibility shims to ensure your task registry and scene configs adhere to native standards.

Can I use local mjlab docs and examples for creating new environments?

Yes, you can use local mjlab docs and examples for creating new environments. The native authoring capability prioritizes reusing local examples first, falling back to bundled references second to define scene configs and sensors.

Why should I avoid compatibility shims during IsaacLab to mjlab migration?

Avoid compatibility shims during IsaacLab to mjlab migration to ensure true behavioral parity and clean native code. Relying on shims bypasses official dict-based manager configurations and prevents proper API mapping.

How does task-registry discovery work for standalone mjlab-native packages?

Task-registry discovery for standalone mjlab-native packages operates through a registry-based discovery flow. This promotes a standalone package structure, allowing multi-tool AI assistants to adapt workflows and locate tasks efficiently.