Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

mjlab

Sterne15

Forks8

Aktualisiert24. Juli 2026 um 02:55

Use when working on MJLab locomotion evaluation, SONIC checkpoint scoring, SkyPilot MJLab YAMLs, or Workbench MJLab CLI behavior.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

nebius

nebius/nebius-physical-ai

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	mjlab
description	Use when working on MJLab locomotion evaluation, SONIC checkpoint scoring, SkyPilot MJLab YAMLs, or Workbench MJLab CLI behavior.

MJLab

MJLab is the locomotion evaluation stage for SONIC Workbench workflows.

Interfaces

CLI:

npa workbench mjlab eval
npa workbench mjlab workflow
npa workbench mjlab status
npa workbench mjlab list

SkyPilot YAML:

npa/src/npa/workflows/skypilot/mjlab-eval.yaml
npa/src/npa/workflows/skypilot/sonic-locomotion-finetuning.yaml

Routing And Data Flow

Route MJLab evaluation to H100 for the checked-in workflow templates.

Inputs and outputs use S3 paths:

--input-path: retargeted motion or rollout artifacts.
--checkpoint: SONIC checkpoint artifact.
--output-path: MJLab evaluation output prefix.

The result artifact is mjlab_eval.json.

Workflow Constraint

Keep orchestration logic in SkyPilot YAML. Do not add a Python runner script for the SONIC locomotion fine-tuning path.

Mehr aus diesem Repository

gleiches Repository

dataset

nebius/nebius-physical-ai

Use when ingesting, validating, curating, or querying production sensor data as a versioned dataset-of-record, or wiring the dataset-ingest-curate workflow.

2026-07-2415

scenario-gen

nebius/nebius-physical-ai

Use when generating adversarial scenarios via RL, ranking mined failures of a policy-under-test, or wiring the adversarial-scenario-hardening workflow.

2026-07-2415

cosmos3-codebase-nav

nebius/nebius-physical-ai

Use when navigating the Cosmos3 integration in NPA or locating upstream Cosmos3 framework files, defaults, scripts, configs, recipes, and docs.

2026-07-2415

cosmos3-env-troubleshoot

nebius/nebius-physical-ai

Use when Cosmos3 setup, fetch, inference, CUDA, uv, Docker, Hugging Face, GitHub, NGC, or checkpoint staging fails in NPA or in an upstream Cosmos framework checkout.

2026-07-2415

cosmos3-setup

nebius/nebius-physical-ai

Use when setting up Cosmos3 access through NPA, checking source or Hugging Face reachability, staging the public Cosmos3 framework and checkpoint cache, or deciding which NPA workflow to use before inference.

2026-07-2415

physical-ai-context

nebius/nebius-physical-ai

Use for Claude Code reviews that need robotics, simulation, GPU-routing, sim-to-real, or BDD100K pipeline domain context.

2026-07-2415

name	mjlab
description	Use when working on MJLab locomotion evaluation, SONIC checkpoint scoring, SkyPilot MJLab YAMLs, or Workbench MJLab CLI behavior.

MJLab

MJLab is the locomotion evaluation stage for SONIC Workbench workflows.

Interfaces

CLI:

npa workbench mjlab eval
npa workbench mjlab workflow
npa workbench mjlab status
npa workbench mjlab list

SkyPilot YAML:

npa/src/npa/workflows/skypilot/mjlab-eval.yaml
npa/src/npa/workflows/skypilot/sonic-locomotion-finetuning.yaml

Routing And Data Flow

Route MJLab evaluation to H100 for the checked-in workflow templates.

Inputs and outputs use S3 paths:

--input-path: retargeted motion or rollout artifacts.
--checkpoint: SONIC checkpoint artifact.
--output-path: MJLab evaluation output prefix.

The result artifact is mjlab_eval.json.

Workflow Constraint

Keep orchestration logic in SkyPilot YAML. Do not add a Python runner script for the SONIC locomotion fine-tuning path.