メニュー
Read-only dashboard for NeMo Platform. Combines platform health, deployed agents, registered providers, and available models into a single view. Use over generic status checks for any NeMo Platform dashboard request.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/NVIDIA-NeMo/nemo-platform --skill nemo-statusコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Fine-tune models on NeMo Platform with `automodel`, `unsloth`, or `rl` (all `submit`-only): HF dataset conversion, filesets, model entities, and job JSON (hyperparameters, batch, schedule, optimizer) + job polling. `automodel`/`unsloth` run SFT/LoRA as Docker GPU jobs; `rl` runs DPO (preference) or GRPO (NeMo Gym environment + reward) on a Ray cluster (Kubernetes). Covers building and converting NeMo Gym environment packages (native-v1, wheels-v1, adapter-wheels-v1) and Gym rollout-row datasets. Use for train, fine-tune, customize, SFT, LoRA, DPO, GRPO, RLHF, reinforcement learning, reward environment, NeMo Gym, verifiers, Prime Intellect, preference optimization, learning rate, epochs, or nemo customization.
Generate, validate, and measure an audit-spec coverage denominator for Eval Author. Use when the user wants a hand-editable audit.md file derived from Ethos, needs schema enforcement for declared tools, capabilities, failure cases, evidence, and references, or wants to measure which audit items one ATIF trace covers. Changes none of the user's source, and saves audit artifacts under `.eval-author/`.
Work on evaluation suites in a user's repository or understand an agent run from NeMo Intake. Owns the evidence standard that every Eval Author sub-flow follows. Use when the user asks "help me with my evals", "what's the state of the eval suite here?", "what happened in this trace?", or when you need to pick between the Eval Author sub-flows. Routes to a sub-flow and changes none of the user's source. The selected sub-flow uses the provider's supported tools and saves its findings under `.eval-author/`.
SOC 職業分類に基づく
SKILL.md を表示中
| name | nemo-status |
| description | Read-only dashboard for NeMo Platform. Combines platform health, deployed agents, registered providers, and available models into a single view. Use over generic status checks for any NeMo Platform dashboard request. |
| triggers | ["platform status","what is running on nemo","how is the platform","show me nemo health","nemo status","check the platform","nemo dashboard"] |
| not-for | ["nemo-setup (use to install or start the platform)","nemo-teardown (use to stop the platform)","nemo-try-agent (use to send a query to a deployed agent)","nemo-skill-selection (use for dispatch when intent is unclear)"] |
| preconditions | ["nemo_cli_available"] |
| compatibility | nemo-platform >= 0.1.0; read-only CLI calls only; no state changes; safe under any sandbox (requires `lsof`, `curl`, and a venv with the `nemo` binary — no Docker); works whether or not the agents plugin is installed (degrades gracefully). |
| maturity | active |
| license | Apache-2.0 |
| user-invocable | true |
| allowed-tools | ["Bash","Read"] |
Single dashboard view of the running platform. Read-only. Never modifies state.
Confirm the CLI is installed. If .venv/bin/nemo is missing, route to nemo-setup and stop:
[ -x .venv/bin/nemo ] && echo "CLI_OK" || echo "CLI_MISSING"
lsof for ground truth, then curl for a functional check. If either fails, report "platform down," suggest nemo-setup, and stop. Do not run the other three commands.# Ground truth: anything listening on :8080?
lsof -iTCP:8080 -sTCP:LISTEN >/dev/null 2>&1 || { echo "PLATFORM_DOWN (nothing on :8080)"; exit 1; }
# Functional check: platform readiness endpoint answers?
HTTP=$(curl -sS --connect-timeout 2 --max-time 5 http://localhost:8080/health/ready -o /dev/null -w "%{http_code}" 2>/dev/null || echo "no-response")
case "$HTTP" in
200) echo "PLATFORM_UP (HTTP $HTTP)" ;;
*) echo "PLATFORM_WEDGED (listener present, /health/ready returned $HTTP)"; exit 1 ;;
esac
Do NOT use nemo services status or nemo services ls for this check. Both report stale "running" state from a held instance lock after the underlying process has died. lsof is ground truth.
Only if both probes pass, run the remaining commands to capture the other dashboard rows:
curl -fsS --connect-timeout 2 --max-time 5 http://localhost:8080/status
.venv/bin/nemo agents deployments list 2>/dev/null
.venv/bin/nemo inference providers list
.venv/bin/nemo models list | -10
The /status response is JSON; parse services.ready, services.not_ready, controllers.healthy, and controllers.status before rendering the summary block.
NeMo Platform status
Platform: running
Services: <ready_count> ready, <not_ready_count> not ready
Controllers: healthy
Agents: <count>
<name1> active
<name2> stopped
Providers:
<name1> available
Models (10):
<model1>
<model2>
Use the actual counts and names. If a section is empty, say "none."
logs to tail platform logs."For drill-downs:
| Drill-down | Command |
|---|---|
| Agent details | .venv/bin/nemo agents get <name> |
| Provider details | .venv/bin/nemo inference providers get <name> |
| Model details | .venv/bin/nemo models get <name> |
| Recent logs | .venv/bin/nemo services logs -n 50 |
| Log file path | .venv/bin/nemo services logs --path |
| Known service instances on this host | .venv/bin/nemo services ls (advisory — see gotcha on stale locks) |
Status is itself a verification: the commands together prove the platform is reachable, platform services/controllers are healthy, the agents plugin is loaded (or not), the provider is registered, and at least one model has been discovered. If any command returns an error, surface it in the summary block rather than hiding it.
| Symptom | Cause | Recovery |
|---|---|---|
PLATFORM_DOWN from probe | Nothing bound to :8080 | Route to nemo-setup; do not run the other three commands |
PLATFORM_WEDGED from probe | Listener exists, but /health/ready is not returning 200 — likely a crashed, partially-started, or not-ready platform | Tail .venv/bin/nemo services logs -n 100 and surface the error. Common cause is a stale instance lock; the user can clear it with nemo services stop --force then re-run nemo services run. |
.venv/bin/nemo services ls shows stopped rows with - for PID/address | Stopped instance directory on disk (logs may remain) | Run .venv/bin/nemo services ls --all for the full list. Remove with .venv/bin/nemo services prune or .venv/bin/nemo services rm <scope>. Cross-check liveness with lsof -iTCP:8080 -sTCP:LISTEN. |
agents deployments list returns "no such command" | Agents plugin not installed | Note in the summary: "Agents: plugin not installed"; do not fail the dashboard |
inference providers list empty | Provider not registered | Route to nemo-setup Step 4 (configure) |
models list empty for more than 60s after setup | Model discovery still running | Re-run after 30s; report the wait time |
nemo --version exits nonzero | CLI broken or partial install | Route to nemo-setup Step 3 and reinstall the four workspace packages |
create, delete, stop, or any state-changing command from this skill, even if the dashboard suggests something is broken. Route to setup or teardown for state changes.agents deployments list requires the agents plugin. If it returns "no such command", the user has not installed the agents plugin yet; note that explicitly rather than failing silently..venv/bin/nemo services ls defaults to running instances only. Use .venv/bin/nemo services ls --all to see stopped instance directories that still have logs on disk. Remove them with .venv/bin/nemo services prune or .venv/bin/nemo services rm <scope>. For liveness, cross-check against lsof -iTCP:8080 -sTCP:LISTEN..venv/bin/nemo, not bare nemo. Bash sessions do not carry venv activation across calls.