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.

Informações da origem

Repositório
NVIDIA/OSMO
Última atividade na origem
8 de outubro de 2026 às 15:09
Idioma detectado do SKILL.md
inglês
Estrelas
284
Forks
63

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

Explorador de arquivos
66 arquivos

Exibindo SKILL.md

SKILL.md
Instruções da origem · Visualização somente leitura
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.