Skip to main content

osmo-user

Drive OSMO through its CLI or a connected MCP for cloud-robotics compute on behalf of an end user: check resources, submit/monitor/debug/explain workflows, fetch logs and Grafana/Kubernetes links, inspect direct data storage, manage workflow apps, and set workflow credentials. Use whenever the user asks about OSMO pools, quota, GPUs, or nodes, or about submitting, listing, querying, monitoring, or troubleshooting workflows — including failed, PENDING, queued, stuck, or image-pull-blocked workflows, or when they ask to inspect or transfer direct storage URIs such as `s3://...`. Use when the request explicitly mentions OSMO or the `osmo` CLI, or otherwise provides unambiguous OSMO context such as an OSMO pool, quota, workflow ID, or storage URI. Do not trigger solely from the word "workflow," which is ambiguous across host environments. Do not use for Kubernetes admin, server-side `osmo config` changes, OSMO install/deploy, non-OSMO compute, or general NVIDIA hardware questions.

Datos de origen

Repositorio
NVIDIA/OSMO
Última actividad en el origen
8 de octubre de 2026 a las 15:09
Idioma detectado de SKILL.md
inglés
Estrellas
284
Forks
63

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Explorador de archivos
66 archivos

Mostrando SKILL.md

SKILL.md
Instrucciones de origen · Vista previa de solo lectura
nameosmo-user
descriptionDrive OSMO through its CLI or a connected MCP for cloud-robotics compute on behalf of an end user: check resources, submit/monitor/debug/explain workflows, fetch logs and Grafana/Kubernetes links, inspect direct data storage, manage workflow apps, and set workflow credentials. Use whenever the user asks about OSMO pools, quota, GPUs, or nodes, or about submitting, listing, querying, monitoring, or troubleshooting workflows — including failed, PENDING, queued, stuck, or image-pull-blocked workflows, or when they ask to inspect or transfer direct storage URIs such as `s3://...`. Use when the request explicitly mentions OSMO or the `osmo` CLI, or otherwise provides unambiguous OSMO context such as an OSMO pool, quota, workflow ID, or storage URI. Do not trigger solely from the word "workflow," which is ambiguous across host environments. Do not use for Kubernetes admin, server-side `osmo config` changes, OSMO install/deploy, non-OSMO compute, or general NVIDIA hardware questions.