agentsclimarketplace

Nvidia ai operations day2

Skill Raishin/vanguard-frontier-agentic/skills/nvidia/nvidia-ai-operations-day2

Use this skill when reviewing day-2 operations of NVIDIA GPU fleets — DCGM exporter and DCGM-Diag posture, GPU telemetry into Prometheus/Grafana, MIG partitioning lifecycle, GPU health and Xid error response, fleet upgrade paths, and incident response for GPU-failure modes. Trigger when the user asks how a GPU fleet is monitored, whether DCGM is wired, whether Xid signatures map to runbooks, or whether the deployment meets NCP-AIO certification expectations.From its SKILL.md

Install
npx -y skills add Raishin/vanguard-frontier-agentic --skill nvidia-ai-operations-day2

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

2.3 KB, 383 tokens by cl100k_base, as published. Nobody here has run it

NVIDIA AI Operations (Day-2) Review

Purpose

Review operational posture of NVIDIA GPU fleets against the NCP-AIO body of knowledge: DCGM and DCGM-Exporter coverage, MIG partitioning lifecycle, Xid error classification and runbooks, fleet driver/firmware upgrade orchestration, and GPU-aware incident response.

Lean operating rules

  • Prefer live evidence (dcgmi diag, dcgmi health, nvidia-smi --query-gpu=..., Prometheus DCGM metrics) when the active client exposes it; otherwise fall back to NVIDIA DCGM documentation, sanitized dashboards, and Xid reference tables.
  • Separate confirmed facts from inference. If DCGM coverage, alerting rules, or Xid classification was not directly queried, say so.
  • Treat absence of DCGM exporter on production GPU nodes as a high finding — fleet is operationally blind.
  • Treat ungated driver/firmware rolling upgrade (no pre-drain, no canary, no rollback path) as a high finding.
  • Treat undocumented Xid signature → runbook mapping as a medium finding — incidents will be triaged from scratch.
  • Treat GPU-Operator / device-plugin running with default permissive securityContext on multi-tenant clusters as a high finding.
  • Treat MIG re-partitioning performed live without workload drain as a medium finding (running contexts are killed).
  • Treat alerting that does not cover ECC double-bit errors, NVLink errors, or row-remapping pending as a medium finding.

Response minimum

Return, at minimum:

  • the scoped target (cluster/fleet, exporter version) and evidence level,
  • DCGM exporter coverage and alert posture,
  • MIG partitioning lifecycle posture,
  • Xid → runbook coverage,
  • driver/firmware upgrade discipline,
  • safe next actions and assumptions or blockers.

What ships with it: 1 file

1.2 KB alongside SKILL.md

Keep looking

Skills are one crate of 613,531. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.