osmo-user
About 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.
Install
Copy the command and run it in a terminal.
npx skills add https:/ / nvidia/ osmo --skill osmo-userAfter installing, type/osmo-userin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
evals/.gitignoreconfig.ymlevals.jsonevals/files/fixtures/app_ok/app_create_response.txtevals/files/fixtures/default/app_info_response.txtapp_list_response.txtapp_show_response.txtapp_spec_response.yamlapp_submit_response.txtcredential_list_response.txtcredential_set_response.txtdata_check_response.txtdata_download_response.txtpool_list.jsonprofile_list.jsonresource_list.jsonworkflow_events_badimage.txtworkflow_events_oom.txtworkflow_events_pending.txtworkflow_events_private_image.txtworkflow_list.jsonworkflow_logs_badimage.txtworkflow_logs_private_image.txtworkflow_logs_single_task.txtworkflow_logs_tool.txtworkflow_query_app_run.jsonworkflow_query_badimage.jsonworkflow_query_oom.jsonworkflow_query_pending.jsonworkflow_query_private_image.json