nvidia-osmo-to-npa-workflow skillA
nvidia-osmo-to-npa-workflow is agent-read markdown (skill) from nebius/nebius-physical-ai: Use when semantically translating a pinned NVIDIA OSMO workflow definition, or a related Airflow DAG, into a reviewable npa.workflow/v0.0.1 graph without claiming control-plane equivalence..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# NVIDIA OSMO to NPA Workflow ## Scope Use this skill to translate the intent and execution contract of an authoritative, pinned NVIDIA OSMO workflow into `npa.workflow/v0.0.1`. It also covers an Airflow-on-Kubernetes definition when that is the authoritative NVIDIA source. This is a review procedure, not an automated converter. The result is a semantic translation: it must preserve real components, data dependencies, failure behavior, and evidence expectations while explicitly recording control-plane differences. Passing YAML parsing alone does not prove equivalence. Do not claim that SkyPilot executes OSMO or Airflow, and do not claim one-to-one equivalence for features NPA does not implement. Read these companion skills before changing a workflow: - `skills/workflows/author-npa-workflow/SKILL.md` - `skills/atomic/real-components/SKILL.md` - `skills/atomic/solution-licensing/SKILL.md` - `skills/atomic/gpu-selection/SKILL.md` - `skills/atomic/health-preflight/SKILL.md` - `skills/atomic/submit-workflow/SKILL.md` - `skills/workflows/emit-reviewable-rrd/SKILL.md` when Rerun evidence is required …
Read the whole file at its exact version.
How to install
mdr add nebius/nebius-physical-ai/nvidia-osmo-to-npa-workflow@git:20260920.e4d7a2amdr add nebius/nebius-physical-ai/nvidia-osmo-to-npa-workflow@sha256:ad0068880bb77980Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_34v7tqf3tlqnwzgz)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (13367 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
nebius/nebius-physical-ai · 32 stars · license Apache-2.0 · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_34v7tqf3tlqnwzgz GET https://markdownregistry.com/api/v1/resolve?ref=nebius/nebius-physical-ai/nvidia-osmo-to-npa-workflow GET https://markdownregistry.com/api/v1/blob/ad0068880bb77980f0743bf02559179d55b0d15fa5d74b86068efd73467d20c3
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.