[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-nvidia-osmo-admin":3,"mdc--gn60ok-key":31,"related-repo-nvidia-osmo-admin":619,"related-org-nvidia-osmo-admin":666},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":20,"repoUrl":21,"updatedAt":22,"license":23,"forks":24,"topics":25,"repo":26,"sourceUrl":29,"mdContent":30},"osmo-admin","manage OSMO service configuration","Use only for offline\u002Flocal OSMO service-config admin requests involving explicit config roots or values files, or to ask for one when a file-specific config request omits it. Do not inspect the workspace to infer a root. Do not use for live workflow support, resource capacity, pod\u002Fnode diagnostics, or cluster operations, except live service-config paths that must be refused.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},"nvidia","NVIDIA","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fnvidia.png",[12,16,19],{"name":13,"slug":14,"type":15},"Operations","operations","tag",{"name":17,"slug":18,"type":15},"Configuration","configuration",{"name":9,"slug":8,"type":15},192,"https:\u002F\u002Fgithub.com\u002FNVIDIA\u002FOSMO","2026-07-14T05:33:26.717488",null,40,[],{"repoUrl":21,"stars":20,"forks":24,"topics":27,"description":28},[],"The developer-first platform for scaling complex Physical AI workloads across heterogeneous compute—unifying training GPUs, simulation clusters, and edge devices in a simple YAML","https:\u002F\u002Fgithub.com\u002FNVIDIA\u002FOSMO\u002Ftree\u002FHEAD\u002Fskills\u002Fosmo-admin","---\nname: osmo-admin\nversion: \"1.0.0\"\nauthor: NVIDIA\ntags: [osmo, admin, service-config]\ntools: [filesystem, shell]\ndescription: >\n  Use only for offline\u002Flocal OSMO service-config admin requests involving\n  explicit config roots or values files, or to ask for one when a file-specific\n  config request omits it. Do not inspect the workspace to infer a root. Do not\n  use for live workflow support, resource capacity, pod\u002Fnode diagnostics, or\n  cluster operations, except live service-config paths that must be refused.\n---\n\n# osmo-admin\n\nUse this skill for OSMO configuration administration in a user-provided config\nroot. Keep this file as a router: load only the reference files needed for the\ncurrent request.\n\n## First Action Gate\n\nBefore listing, searching, or reading the workspace:\n\n- If the request is live workflow support, resource availability, pod\u002Fnode\n  diagnostics, events, logs, status, or scheduler troubleshooting, do not use\n  this skill. Say it needs live workflow or cluster tooling, such as the\n  namespace, kube context, or exported diagnostics. If that tooling is missing,\n  ask for the missing access details or exported diagnostics and stop. Do not\n  attempt local kubeconfig or workspace discovery as a fallback.\n- If the request needs file-specific config data but omits an explicit config\n  root or values file path, ask for that path and stop. An environment,\n  deployment, pool, backend, template, or role name alone is not a config root.\n  Do not name a source file, current value, backend, or target YAML key path\n  before reading the provided root. Do not read references or list files first;\n  after this router confirms the missing root, the next response is the path\n  request.\n- If the request includes an explicit config root or values file path, continue\n  under that exact root string. Use it for discovery, reads, and citations\n  unless a tool requires an internal filesystem remap.\n\n## Purpose\n\nRoute OSMO config-admin questions to verified service values or local file\ndiffs. This skill is config-root agnostic: it does not assume a repo layout,\nenvironment name, identity provider, storage backend, approval process, or\ndeployment mechanism.\n\n## Requirements\n\n- A user-provided config root or values file path containing OSMO service\n  config values or docs.\n- Permission to read files under the provided config root.\n- Permission to edit local files only when the user asks for an admin change.\n- Generic example-only requests do not require a config root, but the answer\n  must use placeholder names and label the structure as illustrative.\n\n## Activation\n\nFor file-specific config questions, first check whether the user provided an\nexplicit config root or values file. If not, activate only to ask for that path;\ndo not list, search, or read the working directory.\n\nBefore activating, confirm the request is about OSMO service-config desired\nstate or local service-values files. Do not activate for live workflow support\nrequests, including submitted or running workloads, stuck or pending workflows,\nworkflow events\u002Flogs\u002Fstatus, workflow exec\u002Fport-forward\u002Frsync, live resource or\ncapacity availability, node\u002Fpod\u002Fscheduler diagnostics, raw Kubernetes\ntroubleshooting, live cluster operations for workloads or resources, or\nincident response. Route those to live workflow or cluster support instead.\nActivate for live OSMO service-config requests such as `osmo config`, direct\nconfig API calls, or service ConfigMap reads\u002Fwrites only to refuse that live\npath and ask for an explicit config root or values file for local config work.\nIf live workflow terms appear, including workflow IDs, stuck, pending, events,\nlogs, status, pod\u002Fnode\u002Fscheduler diagnostics, resource availability, or GPU\ncapacity, stop before reading references or local configs and ask for live\nworkflow or cluster tooling.\n\nUse this skill for OSMO admin questions about:\n\n- pool, backend, platform, quota, maintenance, topology, template, or storage\n  desired state\n- service config, workflow config, backend, role, resource\n  validation, pod template, group template, or backend test definitions\n- read-only answers such as which pools are in maintenance, which roles grant\n  access, which tests attach to a backend, or which mounts a pool resolves to\n- local service-values diffs for requested admin changes\n- config history or rollback only when history is available in the provided\n  config workspace\n\nIf the user asks to read or mutate OSMO admin config through a live path such as\n`osmo config`, a direct OSMO API config call, or a Kubernetes ConfigMap, use\nthis skill only to refuse the live path and ask for an explicit config root or\nvalues file for local config work.\n\nDo not use this skill for user workflow submission\u002Fdebugging, OSMO\ninstallation\u002Fdeployment, or generic Kubernetes help.\n\n## Core Rules\n\n1. Require an explicit config root or values file path before making\n   file-specific claims or edits. Ask for it when missing. Generic example\n   requests may be answered without a config root when clearly labeled as\n   illustrative.\n   A deployment, environment, pool, backend, template, or role name alone is not\n   an explicit config root or values file. Generic target descriptions such as\n   `the GPU pool`, `the production backend`, or `the default template` are not\n   exact target names. Do not search the working directory to infer missing\n   roots or targets.\n   If the request needs file-specific config data and the user did not provide\n   a config root or values file, stop and ask for that path before listing,\n   searching, reading, editing local files, or suggesting source files, current\n   values, backends, or target YAML key paths.\n2. Preserve the user's config root string exactly. Construct paths under that\n   root and cite files using that root or paths relative to it. Never replace it\n   with the current working directory or another discovered checkout. If local\n   tooling maps the supplied root to another filesystem location, use that\n   location only for actual reads; keep that mapping internal and cite the\n   supplied root string or a path relative to it in the answer.\n3. Read `references\u002Fservice-configs.md` for `services.configs` questions before\n   answering or editing.\n4. Clarify ambiguous config root, values file, deployment, pool, backend,\n   template, role, or local-diff intent before editing. For edits, the config\n   root or values file, target deployment or values file, and exact target name\n   must all be unambiguous before any file is changed.\n5. Answer read-only questions from verified config files and cite the source\n   file path plus YAML key path.\n6. For requested changes, prepare the smallest local file diff, inspect it, and\n   report the before\u002Fafter value or diff summary plus local validation output\n   when run, or the exact statement that no local validation command was found.\n7. Do not invent deployment names, file paths, review steps, or config\n   relationships. Infer only from provided config files, or use obvious\n   placeholder names in clearly labeled examples.\n8. Do not treat the working directory as the config root unless the user\n   explicitly identifies it as the config root.\n9. Never run `osmo config` commands or direct OSMO API config calls, including\n   read-only `show`, `list`, `get`, `history`, or `rollback` commands. Answer\n   from an explicit config root or values file, or ask for one.\n10. Never run live mutation commands, including cluster mutation, deployment\n   sync, or rollout commands.\n11. Never run destructive shell cleanup or repo-destructive commands, including\n   `rm`, `rm -f`, `rm -rf`, `git clean`, `git reset --hard`, or\n   `git checkout --`. For preview diffs, use read-only extraction and diff\n   construction that does not require deleting temporary files.\n12. Never print secret payloads. Refer only to secret names, key names, and\n   reference paths.\n\n## Service Config Procedure\n\nFor `services.configs` read-only answers, previews, edits, history, and rollback\ndiffs, follow only the relevant section of `references\u002Fservice-configs.md`.\nAvoid dumping the whole reference when a bounded section is enough. `rg`,\n`grep`, `find`, `ls`, and other listings are locator-only; claims require\ndirect reads or YAML extraction that include the exact source path, key\npath, and value or small subtree. After the required exact evidence is collected,\nstop gathering and answer.\n\n## Reference Routing\n\n### `references\u002Fservice-configs.md`\n\nRead for service-values work itself: discovering config files under the provided\nroot, `services.configs` key mapping, read-only answers, local edits, history\nwhen available, rollback diffs, safe removals, and admin-flow specifics for\npool\u002Fbackend\u002Fstorage\u002Frole\u002Ftemplate\u002Fvalidation\u002Fworkflow\u002Fbackend-test\nvalues.\n\n## Limitations\n\n- This skill prepares local config file changes. It does not deploy, sync,\n  patch, drain, cancel workflows, or verify live service state.\n- If the target config root does not visibly use `services.configs`, say so\n  from file evidence instead of substituting another deployment.\n- If required deployment-specific details are missing, ask one targeted\n  question and stop before editing.\n\n## Troubleshooting\n\n| Problem | Response |\n|---|---|\n| Config root is missing | Ask for the exact config root or values file unless the user only wants a generic example. |\n| Target deployment or pool is ambiguous | Ask for the config root or values file plus the exact deployment and target name. |\n| User asks for `osmo config` | Refuse the live config path and ask for the config root or values file. |\n| User asks for live mutation | Refuse the live path and offer a local config diff. |\n| Secret payload is requested | Refuse payload output; cite only secret names and keys. |\n",{"data":32,"body":41},{"name":4,"version":33,"author":9,"tags":34,"tools":38,"description":6},"1.0.0",[35,36,37],"osmo","admin","service-config",[39,40],"filesystem","shell",{"type":42,"children":43},"root",[44,51,57,64,69,89,95,100,106,129,135,140,154,159,187,199,204,210,401,407,456,462,472,484,490,515,521],{"type":45,"tag":46,"props":47,"children":48},"element","h1",{"id":4},[49],{"type":50,"value":4},"text",{"type":45,"tag":52,"props":53,"children":54},"p",{},[55],{"type":50,"value":56},"Use this skill for OSMO configuration administration in a user-provided config\nroot. Keep this file as a router: load only the reference files needed for the\ncurrent request.",{"type":45,"tag":58,"props":59,"children":61},"h2",{"id":60},"first-action-gate",[62],{"type":50,"value":63},"First Action Gate",{"type":45,"tag":52,"props":65,"children":66},{},[67],{"type":50,"value":68},"Before listing, searching, or reading the workspace:",{"type":45,"tag":70,"props":71,"children":72},"ul",{},[73,79,84],{"type":45,"tag":74,"props":75,"children":76},"li",{},[77],{"type":50,"value":78},"If the request is live workflow support, resource availability, pod\u002Fnode\ndiagnostics, events, logs, status, or scheduler troubleshooting, do not use\nthis skill. Say it needs live workflow or cluster tooling, such as the\nnamespace, kube context, or exported diagnostics. If that tooling is missing,\nask for the missing access details or exported diagnostics and stop. Do not\nattempt local kubeconfig or workspace discovery as a fallback.",{"type":45,"tag":74,"props":80,"children":81},{},[82],{"type":50,"value":83},"If the request needs file-specific config data but omits an explicit config\nroot or values file path, ask for that path and stop. An environment,\ndeployment, pool, backend, template, or role name alone is not a config root.\nDo not name a source file, current value, backend, or target YAML key path\nbefore reading the provided root. Do not read references or list files first;\nafter this router confirms the missing root, the next response is the path\nrequest.",{"type":45,"tag":74,"props":85,"children":86},{},[87],{"type":50,"value":88},"If the request includes an explicit config root or values file path, continue\nunder that exact root string. Use it for discovery, reads, and citations\nunless a tool requires an internal filesystem remap.",{"type":45,"tag":58,"props":90,"children":92},{"id":91},"purpose",[93],{"type":50,"value":94},"Purpose",{"type":45,"tag":52,"props":96,"children":97},{},[98],{"type":50,"value":99},"Route OSMO config-admin questions to verified service values or local file\ndiffs. This skill is config-root agnostic: it does not assume a repo layout,\nenvironment name, identity provider, storage backend, approval process, or\ndeployment mechanism.",{"type":45,"tag":58,"props":101,"children":103},{"id":102},"requirements",[104],{"type":50,"value":105},"Requirements",{"type":45,"tag":70,"props":107,"children":108},{},[109,114,119,124],{"type":45,"tag":74,"props":110,"children":111},{},[112],{"type":50,"value":113},"A user-provided config root or values file path containing OSMO service\nconfig values or docs.",{"type":45,"tag":74,"props":115,"children":116},{},[117],{"type":50,"value":118},"Permission to read files under the provided config root.",{"type":45,"tag":74,"props":120,"children":121},{},[122],{"type":50,"value":123},"Permission to edit local files only when the user asks for an admin change.",{"type":45,"tag":74,"props":125,"children":126},{},[127],{"type":50,"value":128},"Generic example-only requests do not require a config root, but the answer\nmust use placeholder names and label the structure as illustrative.",{"type":45,"tag":58,"props":130,"children":132},{"id":131},"activation",[133],{"type":50,"value":134},"Activation",{"type":45,"tag":52,"props":136,"children":137},{},[138],{"type":50,"value":139},"For file-specific config questions, first check whether the user provided an\nexplicit config root or values file. If not, activate only to ask for that path;\ndo not list, search, or read the working directory.",{"type":45,"tag":52,"props":141,"children":142},{},[143,145,152],{"type":50,"value":144},"Before activating, confirm the request is about OSMO service-config desired\nstate or local service-values files. Do not activate for live workflow support\nrequests, including submitted or running workloads, stuck or pending workflows,\nworkflow events\u002Flogs\u002Fstatus, workflow exec\u002Fport-forward\u002Frsync, live resource or\ncapacity availability, node\u002Fpod\u002Fscheduler diagnostics, raw Kubernetes\ntroubleshooting, live cluster operations for workloads or resources, or\nincident response. Route those to live workflow or cluster support instead.\nActivate for live OSMO service-config requests such as ",{"type":45,"tag":146,"props":147,"children":149},"code",{"className":148},[],[150],{"type":50,"value":151},"osmo config",{"type":50,"value":153},", direct\nconfig API calls, or service ConfigMap reads\u002Fwrites only to refuse that live\npath and ask for an explicit config root or values file for local config work.\nIf live workflow terms appear, including workflow IDs, stuck, pending, events,\nlogs, status, pod\u002Fnode\u002Fscheduler diagnostics, resource availability, or GPU\ncapacity, stop before reading references or local configs and ask for live\nworkflow or cluster tooling.",{"type":45,"tag":52,"props":155,"children":156},{},[157],{"type":50,"value":158},"Use this skill for OSMO admin questions about:",{"type":45,"tag":70,"props":160,"children":161},{},[162,167,172,177,182],{"type":45,"tag":74,"props":163,"children":164},{},[165],{"type":50,"value":166},"pool, backend, platform, quota, maintenance, topology, template, or storage\ndesired state",{"type":45,"tag":74,"props":168,"children":169},{},[170],{"type":50,"value":171},"service config, workflow config, backend, role, resource\nvalidation, pod template, group template, or backend test definitions",{"type":45,"tag":74,"props":173,"children":174},{},[175],{"type":50,"value":176},"read-only answers such as which pools are in maintenance, which roles grant\naccess, which tests attach to a backend, or which mounts a pool resolves to",{"type":45,"tag":74,"props":178,"children":179},{},[180],{"type":50,"value":181},"local service-values diffs for requested admin changes",{"type":45,"tag":74,"props":183,"children":184},{},[185],{"type":50,"value":186},"config history or rollback only when history is available in the provided\nconfig workspace",{"type":45,"tag":52,"props":188,"children":189},{},[190,192,197],{"type":50,"value":191},"If the user asks to read or mutate OSMO admin config through a live path such as\n",{"type":45,"tag":146,"props":193,"children":195},{"className":194},[],[196],{"type":50,"value":151},{"type":50,"value":198},", a direct OSMO API config call, or a Kubernetes ConfigMap, use\nthis skill only to refuse the live path and ask for an explicit config root or\nvalues file for local config work.",{"type":45,"tag":52,"props":200,"children":201},{},[202],{"type":50,"value":203},"Do not use this skill for user workflow submission\u002Fdebugging, OSMO\ninstallation\u002Fdeployment, or generic Kubernetes help.",{"type":45,"tag":58,"props":205,"children":207},{"id":206},"core-rules",[208],{"type":50,"value":209},"Core Rules",{"type":45,"tag":211,"props":212,"children":213},"ol",{},[214,243,248,269,274,279,284,289,294,342,347,396],{"type":45,"tag":74,"props":215,"children":216},{},[217,219,225,227,233,235,241],{"type":50,"value":218},"Require an explicit config root or values file path before making\nfile-specific claims or edits. Ask for it when missing. Generic example\nrequests may be answered without a config root when clearly labeled as\nillustrative.\nA deployment, environment, pool, backend, template, or role name alone is not\nan explicit config root or values file. Generic target descriptions such as\n",{"type":45,"tag":146,"props":220,"children":222},{"className":221},[],[223],{"type":50,"value":224},"the GPU pool",{"type":50,"value":226},", ",{"type":45,"tag":146,"props":228,"children":230},{"className":229},[],[231],{"type":50,"value":232},"the production backend",{"type":50,"value":234},", or ",{"type":45,"tag":146,"props":236,"children":238},{"className":237},[],[239],{"type":50,"value":240},"the default template",{"type":50,"value":242}," are not\nexact target names. Do not search the working directory to infer missing\nroots or targets.\nIf the request needs file-specific config data and the user did not provide\na config root or values file, stop and ask for that path before listing,\nsearching, reading, editing local files, or suggesting source files, current\nvalues, backends, or target YAML key paths.",{"type":45,"tag":74,"props":244,"children":245},{},[246],{"type":50,"value":247},"Preserve the user's config root string exactly. Construct paths under that\nroot and cite files using that root or paths relative to it. Never replace it\nwith the current working directory or another discovered checkout. If local\ntooling maps the supplied root to another filesystem location, use that\nlocation only for actual reads; keep that mapping internal and cite the\nsupplied root string or a path relative to it in the answer.",{"type":45,"tag":74,"props":249,"children":250},{},[251,253,259,261,267],{"type":50,"value":252},"Read ",{"type":45,"tag":146,"props":254,"children":256},{"className":255},[],[257],{"type":50,"value":258},"references\u002Fservice-configs.md",{"type":50,"value":260}," for ",{"type":45,"tag":146,"props":262,"children":264},{"className":263},[],[265],{"type":50,"value":266},"services.configs",{"type":50,"value":268}," questions before\nanswering or editing.",{"type":45,"tag":74,"props":270,"children":271},{},[272],{"type":50,"value":273},"Clarify ambiguous config root, values file, deployment, pool, backend,\ntemplate, role, or local-diff intent before editing. For edits, the config\nroot or values file, target deployment or values file, and exact target name\nmust all be unambiguous before any file is changed.",{"type":45,"tag":74,"props":275,"children":276},{},[277],{"type":50,"value":278},"Answer read-only questions from verified config files and cite the source\nfile path plus YAML key path.",{"type":45,"tag":74,"props":280,"children":281},{},[282],{"type":50,"value":283},"For requested changes, prepare the smallest local file diff, inspect it, and\nreport the before\u002Fafter value or diff summary plus local validation output\nwhen run, or the exact statement that no local validation command was found.",{"type":45,"tag":74,"props":285,"children":286},{},[287],{"type":50,"value":288},"Do not invent deployment names, file paths, review steps, or config\nrelationships. Infer only from provided config files, or use obvious\nplaceholder names in clearly labeled examples.",{"type":45,"tag":74,"props":290,"children":291},{},[292],{"type":50,"value":293},"Do not treat the working directory as the config root unless the user\nexplicitly identifies it as the config root.",{"type":45,"tag":74,"props":295,"children":296},{},[297,299,304,306,312,313,319,320,326,327,333,334,340],{"type":50,"value":298},"Never run ",{"type":45,"tag":146,"props":300,"children":302},{"className":301},[],[303],{"type":50,"value":151},{"type":50,"value":305}," commands or direct OSMO API config calls, including\nread-only ",{"type":45,"tag":146,"props":307,"children":309},{"className":308},[],[310],{"type":50,"value":311},"show",{"type":50,"value":226},{"type":45,"tag":146,"props":314,"children":316},{"className":315},[],[317],{"type":50,"value":318},"list",{"type":50,"value":226},{"type":45,"tag":146,"props":321,"children":323},{"className":322},[],[324],{"type":50,"value":325},"get",{"type":50,"value":226},{"type":45,"tag":146,"props":328,"children":330},{"className":329},[],[331],{"type":50,"value":332},"history",{"type":50,"value":234},{"type":45,"tag":146,"props":335,"children":337},{"className":336},[],[338],{"type":50,"value":339},"rollback",{"type":50,"value":341}," commands. Answer\nfrom an explicit config root or values file, or ask for one.",{"type":45,"tag":74,"props":343,"children":344},{},[345],{"type":50,"value":346},"Never run live mutation commands, including cluster mutation, deployment\nsync, or rollout commands.",{"type":45,"tag":74,"props":348,"children":349},{},[350,352,358,359,365,366,372,373,379,380,386,388,394],{"type":50,"value":351},"Never run destructive shell cleanup or repo-destructive commands, including\n",{"type":45,"tag":146,"props":353,"children":355},{"className":354},[],[356],{"type":50,"value":357},"rm",{"type":50,"value":226},{"type":45,"tag":146,"props":360,"children":362},{"className":361},[],[363],{"type":50,"value":364},"rm -f",{"type":50,"value":226},{"type":45,"tag":146,"props":367,"children":369},{"className":368},[],[370],{"type":50,"value":371},"rm -rf",{"type":50,"value":226},{"type":45,"tag":146,"props":374,"children":376},{"className":375},[],[377],{"type":50,"value":378},"git clean",{"type":50,"value":226},{"type":45,"tag":146,"props":381,"children":383},{"className":382},[],[384],{"type":50,"value":385},"git reset --hard",{"type":50,"value":387},", or\n",{"type":45,"tag":146,"props":389,"children":391},{"className":390},[],[392],{"type":50,"value":393},"git checkout --",{"type":50,"value":395},". For preview diffs, use read-only extraction and diff\nconstruction that does not require deleting temporary files.",{"type":45,"tag":74,"props":397,"children":398},{},[399],{"type":50,"value":400},"Never print secret payloads. Refer only to secret names, key names, and\nreference paths.",{"type":45,"tag":58,"props":402,"children":404},{"id":403},"service-config-procedure",[405],{"type":50,"value":406},"Service Config Procedure",{"type":45,"tag":52,"props":408,"children":409},{},[410,412,417,419,424,426,432,434,440,441,447,448,454],{"type":50,"value":411},"For ",{"type":45,"tag":146,"props":413,"children":415},{"className":414},[],[416],{"type":50,"value":266},{"type":50,"value":418}," read-only answers, previews, edits, history, and rollback\ndiffs, follow only the relevant section of ",{"type":45,"tag":146,"props":420,"children":422},{"className":421},[],[423],{"type":50,"value":258},{"type":50,"value":425},".\nAvoid dumping the whole reference when a bounded section is enough. ",{"type":45,"tag":146,"props":427,"children":429},{"className":428},[],[430],{"type":50,"value":431},"rg",{"type":50,"value":433},",\n",{"type":45,"tag":146,"props":435,"children":437},{"className":436},[],[438],{"type":50,"value":439},"grep",{"type":50,"value":226},{"type":45,"tag":146,"props":442,"children":444},{"className":443},[],[445],{"type":50,"value":446},"find",{"type":50,"value":226},{"type":45,"tag":146,"props":449,"children":451},{"className":450},[],[452],{"type":50,"value":453},"ls",{"type":50,"value":455},", and other listings are locator-only; claims require\ndirect reads or YAML extraction that include the exact source path, key\npath, and value or small subtree. After the required exact evidence is collected,\nstop gathering and answer.",{"type":45,"tag":58,"props":457,"children":459},{"id":458},"reference-routing",[460],{"type":50,"value":461},"Reference Routing",{"type":45,"tag":463,"props":464,"children":466},"h3",{"id":465},"referencesservice-configsmd",[467],{"type":45,"tag":146,"props":468,"children":470},{"className":469},[],[471],{"type":50,"value":258},{"type":45,"tag":52,"props":473,"children":474},{},[475,477,482],{"type":50,"value":476},"Read for service-values work itself: discovering config files under the provided\nroot, ",{"type":45,"tag":146,"props":478,"children":480},{"className":479},[],[481],{"type":50,"value":266},{"type":50,"value":483}," key mapping, read-only answers, local edits, history\nwhen available, rollback diffs, safe removals, and admin-flow specifics for\npool\u002Fbackend\u002Fstorage\u002Frole\u002Ftemplate\u002Fvalidation\u002Fworkflow\u002Fbackend-test\nvalues.",{"type":45,"tag":58,"props":485,"children":487},{"id":486},"limitations",[488],{"type":50,"value":489},"Limitations",{"type":45,"tag":70,"props":491,"children":492},{},[493,498,510],{"type":45,"tag":74,"props":494,"children":495},{},[496],{"type":50,"value":497},"This skill prepares local config file changes. It does not deploy, sync,\npatch, drain, cancel workflows, or verify live service state.",{"type":45,"tag":74,"props":499,"children":500},{},[501,503,508],{"type":50,"value":502},"If the target config root does not visibly use ",{"type":45,"tag":146,"props":504,"children":506},{"className":505},[],[507],{"type":50,"value":266},{"type":50,"value":509},", say so\nfrom file evidence instead of substituting another deployment.",{"type":45,"tag":74,"props":511,"children":512},{},[513],{"type":50,"value":514},"If required deployment-specific details are missing, ask one targeted\nquestion and stop before editing.",{"type":45,"tag":58,"props":516,"children":518},{"id":517},"troubleshooting",[519],{"type":50,"value":520},"Troubleshooting",{"type":45,"tag":522,"props":523,"children":524},"table",{},[525,544],{"type":45,"tag":526,"props":527,"children":528},"thead",{},[529],{"type":45,"tag":530,"props":531,"children":532},"tr",{},[533,539],{"type":45,"tag":534,"props":535,"children":536},"th",{},[537],{"type":50,"value":538},"Problem",{"type":45,"tag":534,"props":540,"children":541},{},[542],{"type":50,"value":543},"Response",{"type":45,"tag":545,"props":546,"children":547},"tbody",{},[548,562,575,593,606],{"type":45,"tag":530,"props":549,"children":550},{},[551,557],{"type":45,"tag":552,"props":553,"children":554},"td",{},[555],{"type":50,"value":556},"Config root is missing",{"type":45,"tag":552,"props":558,"children":559},{},[560],{"type":50,"value":561},"Ask for the exact config root or values file unless the user only wants a generic example.",{"type":45,"tag":530,"props":563,"children":564},{},[565,570],{"type":45,"tag":552,"props":566,"children":567},{},[568],{"type":50,"value":569},"Target deployment or pool is ambiguous",{"type":45,"tag":552,"props":571,"children":572},{},[573],{"type":50,"value":574},"Ask for the config root or values file plus the exact deployment and target name.",{"type":45,"tag":530,"props":576,"children":577},{},[578,588],{"type":45,"tag":552,"props":579,"children":580},{},[581,583],{"type":50,"value":582},"User asks for ",{"type":45,"tag":146,"props":584,"children":586},{"className":585},[],[587],{"type":50,"value":151},{"type":45,"tag":552,"props":589,"children":590},{},[591],{"type":50,"value":592},"Refuse the live config path and ask for the config root or values file.",{"type":45,"tag":530,"props":594,"children":595},{},[596,601],{"type":45,"tag":552,"props":597,"children":598},{},[599],{"type":50,"value":600},"User asks for live mutation",{"type":45,"tag":552,"props":602,"children":603},{},[604],{"type":50,"value":605},"Refuse the live path and offer a local config diff.",{"type":45,"tag":530,"props":607,"children":608},{},[609,614],{"type":45,"tag":552,"props":610,"children":611},{},[612],{"type":50,"value":613},"Secret payload is requested",{"type":45,"tag":552,"props":615,"children":616},{},[617],{"type":50,"value":618},"Refuse payload output; cite only secret names and keys.",{"items":620,"total":665},[621,627,647],{"slug":4,"name":4,"fn":5,"description":6,"org":622,"tags":623,"stars":20,"repoUrl":21,"updatedAt":22},{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[624,625,626],{"name":17,"slug":18,"type":15},{"name":9,"slug":8,"type":15},{"name":13,"slug":14,"type":15},{"slug":628,"name":628,"fn":629,"description":630,"org":631,"tags":632,"stars":20,"repoUrl":21,"updatedAt":646},"osmo-deploy","deploy OSMO to Kubernetes clusters","How to deploy OSMO to a Kubernetes cluster on Azure (AKS), AWS (EKS), MicroK8s (single-node), or any kubectl-reachable cluster (BYO). Use this skill whenever the user asks to install, deploy, set up, or stand up OSMO; whenever they ask to provision an OSMO cluster; whenever they mention deploy-osmo-minimal.sh, deploy-k8s.sh, or \"OSMO helm install\"; whenever they ask to wire up workflow storage (MinIO \u002F Azure Blob \u002F S3); or whenever they ask to add a GPU pool to an OSMO cluster, install KAI scheduler, install the NVIDIA GPU Operator, or run the post-install smoke tests. Targets OSMO 6.3 (ConfigMap mode).\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[633,636,639,642,645],{"name":634,"slug":635,"type":15},"AWS","aws",{"name":637,"slug":638,"type":15},"Azure","azure",{"name":640,"slug":641,"type":15},"Deployment","deployment",{"name":643,"slug":644,"type":15},"Kubernetes","kubernetes",{"name":9,"slug":8,"type":15},"2026-07-14T05:33:24.181591",{"slug":648,"name":648,"fn":649,"description":650,"org":651,"tags":652,"stars":20,"repoUrl":21,"updatedAt":664},"osmo-user","manage cloud robotics workflows with OSMO","Drive the OSMO CLI for cloud-robotics compute on behalf of an end user: check resources, submit\u002Fmonitor\u002Fdebug\u002Fexplain workflows, fetch logs and Grafana\u002FKubernetes 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:\u002F\u002F...`, even when they describe a workflow, cluster resource, or storage URI without saying \"OSMO\". Do not use for Kubernetes admin, server-side `osmo config` changes, OSMO install\u002Fdeploy, non-OSMO compute, or general NVIDIA hardware questions.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[653,656,659,660,663],{"name":654,"slug":655,"type":15},"CLI","cli",{"name":657,"slug":658,"type":15},"Grafana","grafana",{"name":643,"slug":644,"type":15},{"name":661,"slug":662,"type":15},"Monitoring","monitoring",{"name":9,"slug":8,"type":15},"2026-07-14T05:33:25.461692",3,{"items":667,"total":824},[668,686,702,713,725,739,752,766,779,790,804,813],{"slug":669,"name":669,"fn":670,"description":671,"org":672,"tags":673,"stars":683,"repoUrl":684,"updatedAt":685},"nemoclaw-user-guide","retrieve NemoClaw documentation and configuration","Guides human users' AI agents to the NemoClaw docs MCP server and canonical Fern documentation in Markdown form. Use when users ask how to install, configure, operate, troubleshoot, secure, or learn NemoClaw with an AI coding assistant. Trigger keywords - nemoclaw docs, use nemoclaw with ai agent, nemoclaw mcp docs, nemoclaw install help, nemoclaw quickstart, nemoclaw markdown docs, llms.txt, agent skills.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[674,677,680],{"name":675,"slug":676,"type":15},"Documentation","documentation",{"name":678,"slug":679,"type":15},"MCP","mcp",{"name":681,"slug":682,"type":15},"Search","search",21777,"https:\u002F\u002Fgithub.com\u002FNVIDIA\u002FNemoClaw","2026-07-20T06:00:01.461044",{"slug":687,"name":687,"fn":688,"description":689,"org":690,"tags":691,"stars":699,"repoUrl":700,"updatedAt":701},"mcore-build-and-dependency","manage Megatron-LM development environments","Container-based dev environment setup and dependency management for Megatron-LM. Covers acquiring and launching the CI container, uv package management, and updating uv.lock.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[692,695,696],{"name":693,"slug":694,"type":15},"Containers","containers",{"name":640,"slug":641,"type":15},{"name":697,"slug":698,"type":15},"Python","python",17049,"https:\u002F\u002Fgithub.com\u002FNVIDIA\u002FMegatron-LM","2026-07-27T06:06:11.249662",{"slug":703,"name":703,"fn":704,"description":705,"org":706,"tags":707,"stars":699,"repoUrl":700,"updatedAt":712},"mcore-bump-base-image","update NVIDIA PyTorch base images","Bump the NVIDIA PyTorch base image (`nvcr.io\u002Fnvidia\u002Fpytorch:YY.MM-py3`) used by Megatron-LM CI. Covers the two pin sites (GitHub CI in `docker\u002F.ngc_version.dev` and GitLab CI in `.gitlab\u002Fstages\u002F01.build.yml`), the post-bump CI loop (re-run functional tests, refresh golden values, mark broken tests), and the gotchas that bit PRs",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[708,711],{"name":709,"slug":710,"type":15},"CI\u002FCD","ci-cd",{"name":640,"slug":641,"type":15},"2026-07-14T05:25:59.97109",{"slug":714,"name":714,"fn":715,"description":716,"org":717,"tags":718,"stars":699,"repoUrl":700,"updatedAt":724},"mcore-cicd","manage CI\u002FCD pipelines for Megatron-LM","CI\u002FCD reference for Megatron-LM. Covers CI pipeline structure, PR scope labels, triggering internal GitLab CI (which force-pushes the current branch to a pull-request\u002FBRANCH ref — always dry-run and verify the destination first; never run against shared or protected branches), and CI failure investigation.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[719,720,721],{"name":709,"slug":710,"type":15},{"name":640,"slug":641,"type":15},{"name":722,"slug":723,"type":15},"GitHub","github","2026-07-27T06:06:12.278222",{"slug":726,"name":726,"fn":727,"description":728,"org":729,"tags":730,"stars":699,"repoUrl":700,"updatedAt":738},"mcore-create-issue","investigate CI failures and create issues","Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[731,734,735],{"name":732,"slug":733,"type":15},"Debugging","debugging",{"name":722,"slug":723,"type":15},{"name":736,"slug":737,"type":15},"Triage","triage","2026-07-14T05:25:57.442089",{"slug":740,"name":740,"fn":741,"description":742,"org":743,"tags":744,"stars":699,"repoUrl":700,"updatedAt":751},"mcore-linting-and-formatting","lint and format Megatron-LM code","Linting and formatting for Megatron-LM. Covers running autoformat.sh, tools (ruff, black, isort, pylint, mypy), and code style rules.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[745,748],{"name":746,"slug":747,"type":15},"Best Practices","best-practices",{"name":749,"slug":750,"type":15},"Code Analysis","code-analysis","2026-07-14T05:25:56.18433",{"slug":753,"name":753,"fn":754,"description":755,"org":756,"tags":757,"stars":699,"repoUrl":700,"updatedAt":765},"mcore-migrate-gpt-to-hybrid","migrate Megatron-LM models to HybridModel","Migration guide for moving Megatron Core GPTModel checkpoints, model providers, training commands, and layer mappings to HybridModel.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[758,761,764],{"name":759,"slug":760,"type":15},"Machine Learning","machine-learning",{"name":762,"slug":763,"type":15},"Migration","migration",{"name":9,"slug":8,"type":15},"2026-07-17T06:07:11.777011",{"slug":767,"name":767,"fn":768,"description":769,"org":770,"tags":771,"stars":699,"repoUrl":700,"updatedAt":778},"mcore-onboard-gb200-1node-tests","onboard functional tests for GB200","Onboard 1-node GitHub MR functional tests for GB200 from existing mr-scoped 2-node tests.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[772,775],{"name":773,"slug":774,"type":15},"QA","qa",{"name":776,"slug":777,"type":15},"Testing","testing","2026-07-14T05:25:53.673039",{"slug":780,"name":780,"fn":781,"description":782,"org":783,"tags":784,"stars":699,"repoUrl":700,"updatedAt":789},"mcore-run-on-slurm","launch distributed training jobs on SLURM","How to launch distributed Megatron-LM training jobs on a SLURM cluster. Covers a minimal sbatch skeleton, environment-variable setup for torch.distributed.run, CUDA_DEVICE_MAX_CONNECTIONS rules across hardware and parallelism modes, container conventions, monitoring, and per-rank failure diagnosis.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[785,786],{"name":640,"slug":641,"type":15},{"name":787,"slug":788,"type":15},"Infrastructure","infrastructure","2026-07-14T05:25:49.362534",{"slug":791,"name":791,"fn":792,"description":793,"org":794,"tags":795,"stars":699,"repoUrl":700,"updatedAt":803},"mcore-split-pr","split pull requests to reduce review load","Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[796,799,800],{"name":797,"slug":798,"type":15},"Code Review","code-review",{"name":722,"slug":723,"type":15},{"name":801,"slug":802,"type":15},"Pull Requests","pull-requests","2026-07-14T05:26:01.226578",{"slug":805,"name":805,"fn":806,"description":807,"org":808,"tags":809,"stars":699,"repoUrl":700,"updatedAt":812},"mcore-testing","run and manage Megatron-LM tests","Test system for Megatron-LM. Covers test layout, recipe YAML structure, adding and running unit and functional tests, golden values, marker filters, and CI parity.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[810,811],{"name":773,"slug":774,"type":15},{"name":776,"slug":777,"type":15},"2026-07-14T05:25:54.928983",{"slug":814,"name":814,"fn":815,"description":816,"org":817,"tags":818,"stars":699,"repoUrl":700,"updatedAt":823},"nightly-sync","manage nightly main-to-dev sync workflows","Domain knowledge for the nightly main-to-dev sync workflow. Covers merge strategy, CI architecture, failure investigation, and known issues.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[819,822],{"name":820,"slug":821,"type":15},"Automation","automation",{"name":709,"slug":710,"type":15},"2026-07-30T05:29:03.275638",496]