Shared foundation for Real-Time Digital Twins (RTDT) work. An agent skill from NVIDIA-Omniverse-blueprints/digital-twins-for-fluid-simulation.

Custom licenceAuto-check: notesDevOps & Cloud

Install Rtdt Core

skills CLI
$ npx skills add NVIDIA-Omniverse-blueprints/digital-twins-for-fluid-simulation --skill rtdt-core -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install NVIDIA-Omniverse-blueprints/digital-twins-for-fluid-simulation rtdt-core --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/NVIDIA-Omniverse-blueprints/digital-twins-for-fluid-simulation.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/core/rtdt-core .claude/skills/rtdt-core && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
rtdt-core
GitHub stars
140
Token cost
~1.7k tokens
SKILL.md length
841 words
Files
3 (incl. scripts, references)
Skills in repo
3
Repo updated
First seen
Licence
Custom licence

At a glance

Shared foundation for Real-Time Digital Twins (RTDT) work. An agent skill from NVIDIA-Omniverse-blueprints/digital-twins-for-fluid-simulation.

  • Works in 3 steps: Read docker compose logs kit-lite (or… → Keep the browser open through… → Change velocity and visualization mode;…
  • Health-checking the standard
  • SKILL.md covers Choose the execution mode, Start, stop, and check the…, Execution rules and Current contracts, plus 1 more section
  • Runs Shell scripts from its folder; calls docker; needs NGC_API_KEY

What it does

Rtdt Core is an agent skill from NVIDIA-Omniverse-blueprints/digital-twins-for-fluid-simulation. Shared foundation for Real-Time Digital Twins (RTDT) work. Use when starting or health-checking the standard or lite streaming stack, deciding whether a task needs a built Kit application, or reasoning about the current control and inference contracts. Read this before using rtdt-customize or rtdt-aero.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts and reference files (for example `references/contracts.md` and `scripts/check_readiness.sh`).

It sits in DevOps & Cloud. It works with Docker. The repository describes itself as: Reference implementation of real-time AI Physics in an interactive visualization and analysis workflow, applied to CFD and aerodynamics.

When your agent uses it

  • Health-checking the standard
  • Lite streaming stack
  • Deciding whether a task needs a built Kit application
  • Reasoning about the current control and inference contracts

Example prompts

  • “/rtdt-core”

Requirements

  • Python 3
  • A Bash shell
  • Docker
  • A credential in NGC_API_KEY

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Read docker compose logs kit-lite (or kit for standard). app ready can precede
  2. Keep the browser open through initialization. Confirm the scene appears and the loading message
  3. Change velocity and visualization mode; verify the rendered result changes, not just the selected

What it can do on your machine

Read from SKILL.md and the folder at commit 6261054. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • docker

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use docker, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • NGC_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Rtdt Core loads about 1.7k tokens when it runs, and up to ~3.4k if it reads all its reference files. Until then it costs about 79 tokens; SKILL.md has 841 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~79
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:29
    to `.env`, and select exactly one profile; `standard` and `lite` cannot run together because they
  • NoteMentions a .env fileSKILL.md:34
    Treat `.env` as secret-bearing. Do not print the fully resolved Compose model with
  • NoteMentions a .env fileSKILL.md:65
    The preflight does not parse `.env`. When `.env` changes the published web or proxy port, pass the

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 841 words (~1,735 tokens).

“Use this skill as the operational and contract foundation for RTDT work. The repository combines a workflow/controller layer, a specialization, USD stages, a browser UI, Kit-CAE 3.0 visualization, and either live Triton inference (standard) or an offline result cache (lite)…”

— opening of SKILL.md by NVIDIA-Omniverse-blueprints, Custom licence
name
rtdt-core

Read the full SKILL.md on GitHub

Files

SKILL.md and 2 other files (scripts, references) in skills/core/rtdt-core of NVIDIA-Omniverse-blueprints/digital-twins-for-fluid-simulation.

  • SKILL.md
  • references/contracts.md
  • scripts/check_readiness.sh

Open the folder on GitHubat commit 6261054

Compare with similar skills

Rtdt Core next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Rtdt Core compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Rtdt Core this skillNVIDIA-Omniverse-blueprints/digital-twins-for-fluid-simulation140—~1.7kAutomated safety check: NotesCustom licence
Iron Proxy Gateway for NanoClawnanocoai/nanoclaw31k—~4.6kAutomated safety check: NotesMIT
GreptimeDB Dev Docker ImageGreptimeTeam/greptimedb6.7k—~4kAutomated safety check: NotesApache-2.0
Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit2606 repos~1.1kAutomated safety check: NotesCustom licence
LangBot Deployment Guidelangbot-app/LangBot18k—~1.5kAutomated safety check: NotesApache-2.0
Build Openshell Mxc WindowsNVIDIA/OpenShell16k—~4.9kAutomated safety check: PassApache-2.0

Similar skills

  • Installs or refreshes Iron Proxy and its Iron Control web console for NanoClaw, with a local Docker setup, database, credentials and a human approval bridge.

    31k GitHub stars~4.6k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes
  • GreptimeDB Dev Docker Image

    GreptimeTeam/greptimedb

    Packages a locally built GreptimeDB debug binary into a development-only Docker image for local-cluster testing, with an optional push to a dev registry.

    6.7k GitHub stars~4k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes
  • Senior DevOps Toolkit

    maslennikov-ig/claude-code-orchestrator-kit

    Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…

    260 GitHub starsUsed in 6 repos~1.1k tokens
    DevOps & CloudAuto-check: notes
  • LangBot Deployment Guide

    langbot-app/LangBot

    Deploys and configures a LangBot instance with Docker Compose or Kubernetes, covering config.yaml, the Box sandbox runtime, the plugin runtime and the global API key.

    18k GitHub stars~1.5k tokensUpdated today
    DevOps & CloudAuto-check: notes
  • Official

    Maintain and validate OpenShell's build-only Windows MSVC lane for x64 and ARM64.

    16k GitHub stars~4.9k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Megatron-LM Base Image Bump

    NVIDIA/Megatron-LM

    Official

    Moves Megatron-LM CI to a newer NVIDIA PyTorch base image, updating both the GitHub and GitLab pins together and handling the CI follow-up.

    18k GitHub stars~2.8k tokensUpdated today
    DevOps & CloudAuto-check passed

More from NVIDIA-Omniverse-blueprints/digital-twins-for-fluid-simulation

  • Rtdt Aero

    NVIDIA-Omniverse-blueprints/digital-twins-for-fluid-simulation

    Apply RTDT customization specifically to the shipped auto-aero virtual wind tunnel.

    140 GitHub stars~1.9k tokensUpdated 21 days ago
    Auto-check passed
  • Rtdt Customize

    NVIDIA-Omniverse-blueprints/digital-twins-for-fluid-simulation

    Customize an RTDT workflow, AppState schema, USD stage, frontend control, or Kit-CAE 3.0 geometry/result wiring.

    140 GitHub stars~1.2k tokensUpdated 21 days ago
    Auto-check passed

Works with

Categories

Questions about Rtdt Core

What does Rtdt Core do?

Shared foundation for Real-Time Digital Twins (RTDT) work. An agent skill from NVIDIA-Omniverse-blueprints/digital-twins-for-fluid-simulation. Rtdt Core is an agent skill from NVIDIA-Omniverse-blueprints/digital-twins-for-fluid-simulation. Shared foundation for Real-Time Digital Twins (RTDT) work.

When should I use Rtdt Core?

Rtdt Core fits situations like: health-checking the standard; lite streaming stack; deciding whether a task needs a built Kit application; reasoning about the current control and inference contracts.

How do I install Rtdt Core in Claude Code?

Run `npx skills add NVIDIA-Omniverse-blueprints/digital-twins-for-fluid-simulation --skill rtdt-core -a claude-code`. Or copy the skill folder (skills/core/rtdt-core in NVIDIA-Omniverse-blueprints/digital-twins-for-fluid-simulation) into .claude/skills/rtdt-core in your project. Claude Code loads it when a task matches its description.

How do I install Rtdt Core in Codex?

Run `npx skills add NVIDIA-Omniverse-blueprints/digital-twins-for-fluid-simulation --skill rtdt-core -a codex`. Or copy the skill folder (skills/core/rtdt-core in NVIDIA-Omniverse-blueprints/digital-twins-for-fluid-simulation) into .agents/skills/rtdt-core in your project. Codex loads it when a task matches its description.

Can I use Rtdt Core in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NVIDIA-Omniverse-blueprints/digital-twins-for-fluid-simulation --skill rtdt-core -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/rtdt-core, .gemini/skills/rtdt-core, .github/skills/rtdt-core and .opencode/skills/rtdt-core in your project.

What does Rtdt Core need to run?

Going by SKILL.md and its folder, Rtdt Core needs a shell for the scripts in its folder, the command-line tools its instructions call (docker) and credentials named NGC_API_KEY. Our summary lists: Python 3; A Bash shell; Docker; A credential in NGC_API_KEY.

Does Rtdt Core access the network?

SKILL.md contains no URLs. Its commands use docker, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Rtdt Core safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Rtdt Core use?

Rtdt Core has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Rtdt Core use?

About 1.7k tokens (SKILL.md is roughly 6.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.7k tokens, read only when the agent opens those files.

What are the alternatives to Rtdt Core?

Skills that share tags, products or a category with Rtdt Core: Iron Proxy Gateway for NanoClaw (nanocoai/nanoclaw, 31k stars), GreptimeDB Dev Docker Image (GreptimeTeam/greptimedb, 6.7k stars), Senior DevOps Toolkit (maslennikov-ig/claude-code-orchestrator-kit, 260 stars) and LangBot Deployment Guide (langbot-app/LangBot, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Rtdt Core?

NVIDIA-Omniverse-blueprints (a GitHub organization) maintains it in NVIDIA-Omniverse-blueprints/digital-twins-for-fluid-simulation, which has 140 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on September 19, 2026.

Source: NVIDIA-Omniverse-blueprints/digital-twins-for-fluid-simulation on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.