coordinate-nemoclaw-blender

Redirect legacy Blender and Omniverse simulation prompts to the coach-nemoclaw-hermes system.

86|42|Updated May 6, 2026
One-click install
npx skills add https://github.com/NVIDIA/nemoclaw-community --skill coordinate-nemoclaw-blender
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coordinate-nemoclaw-blender
Source: https://github.com/NVIDIA/nemoclaw-community/tree/main/examples/demos/field/blender-omniverse-dgx-station/codex-skills/coordinate-nemoclaw-blender
Command: npx skills add https://github.com/NVIDIA/nemoclaw-community --skill coordinate-nemoclaw-blender

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a compatibility layer for legacy prompts that specifically request the coordinate-nemoclaw-blender workflow, ensuring continuity for older agent interactions.

Core Features & Use Cases

  • Legacy Compatibility: Maintains support for existing prompts while directing users toward modern, robust coaching workflows.
  • Workflow Alignment: Ensures that Blender, Omniverse, and simulation tasks are routed through the appropriate, validated coaching systems.
  • Use Case: When an existing automation script or user prompt calls for the legacy coordinate-nemoclaw-blender skill, this unit safely redirects the request to the current coach-nemoclaw-hermes system to maintain operational integrity.

Quick Start

Use the coordinate-nemoclaw-blender skill to initiate the transition to the current Hermes coaching workflow for your active Blender or Omniverse project.

Frequently Asked Questions about coordinate-nemoclaw-blender

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

FAQPage Schema
How do I transition legacy Blender and Omniverse simulation workflows to a modern coaching system?

To transition legacy Blender and Omniverse simulation workflows, this skill redirects older task requests to the current coach-nemoclaw-hermes system for improved safety and validation.

What is a compatibility alias for older Omniverse and Blender agent prompts?

A compatibility alias for older Omniverse and Blender agent prompts maintains support for existing automation scripts while routing tasks through validated coaching workflows.

Do I need to update my automation scripts if they call the coordinate-nemoclaw-blender workflow?

You do not need to immediately update automation scripts calling the coordinate-nemoclaw-blender workflow, as this skill safely intercepts and redirects them to the current Hermes system.

Does this legacy bridge ensure rendering and simulation tasks meet modern serialization requirements?

Yes, the legacy bridge ensures rendering and simulation tasks meet modern serialization and sandbox-transfer requirements by routing them through the updated coach-nemoclaw-hermes system.

When should I use this legacy compatibility layer for Blender and Omniverse tasks?

Use this legacy compatibility layer when an existing automation script or user prompt calls for the coordinate-nemoclaw-blender skill to maintain operational integrity during active projects.