Agent Skills
› NVIDIA/dgx-spark-playbooks
› dgx-station-diagnose
dgx-station-diagnose
GitHub用于 NVIDIA DGX Station GB300 的只读诊断工具,自动运行检测、关联官方手册并生成支持包。仅在获得明确授权后执行单一修复操作,严禁修改配置或中断服务,确保硬件与软件故障的安全排查。
触发场景
用户报告 GPU 健康、CUDA 或推理服务故障
需要导出 DGX Station 诊断支持包
请求应用经过批准的允许列表修复
安装
npx skills add NVIDIA/dgx-spark-playbooks --skill dgx-station-diagnose -g -y
SKILL.md
Frontmatter
{
"name": "dgx-station-diagnose",
"description": "Run and interpret the complete read-only dgx-assist diagnostic suite for NVIDIA DGX Station GB300, correlate findings with pinned NVIDIA playbooks, export a redacted support bundle, and apply one separately approved allowlisted fix. Use when the user reports a Station, CUDA, GPU health, coherency, vsloshd, Docker, CDI, MIG, cache, port, or owned inference-service failure."
}
DGX Station diagnostics
Diagnose first. Do not mutate as part of diagnosis.
Workflow
- Run
scripts/dgx-assist diagnose run --json. - Report the detected compatibility profile, then findings in severity order with their stable IDs and evidence. Preserve
unknownstates. On Software 1.0, do not reinterpret intentionally skipped Software 2.0 service checks as faults. - Search the pinned playbooks for each high or critical finding; cite the relevant URL, heading, lines, and commit.
- If no passage overlaps, say so and avoid inventing a platform fix.
- Offer
diagnose bundle --report-id "<id>"when escalation is appropriate. - Offer at most one automatic fix at a time, and only when
fix_idis present. - Preview with
diagnose fix --report-id "<id>" --finding "<id>" --dry-run. - Explain exact actions, impact, privilege, and reboot state. Obtain explicit approval.
- Repeat with
--yesonly after approval and report the action receipt.
Safety requirements
- Keep
diagnose runread-only. - Never install packages, rewrite Docker configuration, change power caps or driver parameters, kill workloads, or modify MIG through a diagnostic fix.
- Never stop a service without current
dgx-assistownership evidence. - Never use Fabric Manager as a routine Station check or remediation.
- Re-run diagnostics when finding evidence is stale.
- Never reveal secrets or unredacted home paths in a bundle.
- Do not execute an unregistered remediation.
- Treat
--yesonly as approval already obtained.
Read references/findings.md before proposing a fix or support bundle. Read references/bringup.md when the problem concerns physical deployment, BMC or firmware verification, driver bring-up, power braking, or support escalation.
版本历史
- 1fb66f0 当前 2026-08-20 12:20


