mjlab

Orchestrate locomotion evaluation and SONIC workbench workflows on Nebius GPU clusters.

17|8|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/nebius/nebius-physical-ai --skill mjlab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mjlab
Source: https://github.com/nebius/nebius-physical-ai/tree/main/skills/tools/mjlab
Command: npx skills add https://github.com/nebius/nebius-physical-ai --skill mjlab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the evaluation of locomotion models and SONIC workbench workflows, removing the complexity of manual orchestration and artifact management.

Core Features & Use Cases

  • Locomotion Evaluation: Execute standardized evaluation stages for SONIC Workbench workflows.
  • Workflow Integration: Manage SkyPilot YAML configurations for locomotion fine-tuning and evaluation.
  • Use Case: A researcher needs to validate a new locomotion policy against retargeted motion data; this skill handles the routing to H100 clusters and generates the required mjlab_eval.json artifact.

Quick Start

Use the mjlab skill to run the evaluation workflow for the specified input path and SONIC checkpoint.

Frequently Asked Questions about mjlab

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

FAQPage Schema
How do I evaluate a physical-AI locomotion model on Nebius GPU clusters?

Evaluating a physical-AI locomotion model on Nebius GPU clusters requires orchestrating evaluation tasks via SkyPilot YAML templates and S3-based data paths. This workflow routes tasks to H100 clusters, monitoring status and generating mjlab_eval.json artifacts.

What is the SONIC workbench workflow for locomotion fine-tuning?

The SONIC workbench workflow for locomotion fine-tuning is a standardized evaluation process that validates new locomotion policies against retargeted motion data. It handles routing to H100 clusters and manages input and output artifacts stored in S3.

How do I use SkyPilot YAML configurations to manage locomotion evaluation tasks?

SkyPilot YAML configurations manage locomotion evaluation tasks by defining the execution parameters for Nebius GPU clusters. They integrate with S3-based data paths to process input artifacts and generate the required mjlab_eval.json output.

Can I validate a locomotion policy against retargeted motion data using SONIC checkpoints?

Validating a locomotion policy against retargeted motion data using SONIC checkpoints is supported by specifying the input path and checkpoint. The workflow executes standardized evaluation stages and outputs the mjlab_eval.json artifact.

Does locomotion evaluation on Nebius require specific data paths for input and output artifacts?

Locomotion evaluation on Nebius requires S3-based data paths for both input and output artifacts. This integration facilitates the execution of evaluation tasks and the generation of the mjlab_eval.json artifact.

Why use SkyPilot for physical-AI locomotion evaluation instead of manual orchestration?

Using SkyPilot for physical-AI locomotion evaluation removes the complexity of manual orchestration and artifact management. It streamlines workflow execution, status monitoring, and task routing to H100 clusters for SONIC models.